Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Maven jetty plugin classpath error with 7.5.3.v20111011

Yep, the impl of the plugin changed for 7.5.3 in the way in which it obtains the dependency jars of the project.  I think what has happened is that the new way (recommended by the maven developers) of obtaining the project dependencies is a maven 3.x-ism.

Note also that I want to change the names of some of the configuration parameters, so I used a maven mechanism called "aliasing" to maintain backward compatibility with the old names, however, I suspect that this mechanism is also a maven 3.x-ism as I've had a report of the old names not working when using maven 2.x.

I'll have to put something on the wiki about this.


On 20 October 2011 03:00, Mike Pilone <MPilone@xxxxxxx> wrote:

I upgraded from 7.4.5.v20110725 to 7.5.3.v20111011 today and found that any system using Maven 2.2.1 would throw a "javax.servlet.UnavailableException" when loading a servlet from my webapp. The same exact project works fine using Maven 3.0.3.


What I've seen with the exact same project and POM:

- Maven 2 with 7.4.5.v20110725 works

- Maven 2 with 7.5.3.v20111011 fails

- Maven 3 with 7.5.3.v20111011 works


With Maven 2 and 7.5.3.v20111011 debug output I see:

[2011-10-19 11:40:53,630] [DEBUG] [org.mortbay.jetty.plugin.MavenWebInfConfiguration           ] [main]: Classpath = [file:/C:/contentDepot/head/cd-project/ui/portalui/target/classes/]

[2011-10-19 11:40:53,630] [DEBUG] [org.mortbay.jetty.plugin.MavenWebInfConfiguration           ] [main]: Server classes: ...


With Maven 3 and 7.5.3.v20111011 debug output I see:

[2011-10-19 11:28:14,880] [DEBUG] [org.mortbay.jetty.plugin.MavenWebInfConfiguration           ] [main]: Classpath = [file:/C:/contentDepot/head/cd-project/ui/portalui/target/classes/, file:/C:/Users/mpilone/.m2/repository/org/prss/contentdepot/core/16.18.0-SNAPSHOT/core-16.18.0-SNAPSHOT.jar, file:/C:/Users/mpilone/.m2/repository/org/springframework/spring-core/3.0.5.RELEASE/spring-core-3.0.5.RELEASE.jar, file:/C:/Users/mpilone/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar, file:/C:/Users/mpilone/.m2/repository/org/springframework/spring-context/3.0.5.RELEASE/spring-context-3.0.5.RELEASE.jar, file:/C:/Users/mpilone/.m2/repository/org/springframework/spring-aop/3.0.5.RELEASE/spring-aop-3.0.5.RELEASE.jar, file:/C:/Users/mpilone/.m2/repository/org/springframework/spring-tx/3.0.5.RELEASE/spring-tx-3.0.5.RELEASE.jar, file:/C:/Users/mpilone/.m2/repository/org/hibernate/hibernate-validator/4.0.2.GA/hibernate-validator-4.0.2.GA.jar, file:/C:/Users/mpilone/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar,



So it looks like the plug-in is behaving differently under Maven 2 and 3. This difference only started to show up from 7.4 to 7.5. I could send along my plugin config from the POM if needed but they are both running with the same POM.


Any ideas?





* | Mike Pilone | Software Architect, Distribution | mpilone@xxxxxxx | o: 202-513-2679  m: 703-969-7493


jetty-users mailing list

Back to the top