Probable bug with maven-war-plugin-2.1-alpha-2
I recently upgraded Maven 2.0.10 and noticed that this version of Maven has changed the default version of the maven-war-plugin to 2.1-alpha-2. When using this version of the plugin I get the following error: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappS tructure.java:109) at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(Web appStructure.java:288) at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask. performPackaging(DependenciesAnalysisPackagingTask.java:46) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo. java:439) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(Abstract WarMojo.java:375) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) I have reverted back to alpha-1 of the plugin and everythings works fine. I checkedout the source and compared it with alpha 1 and it looks like there were a lot of changes to file WebappStructure.java:109, the file throwing the NullPointerException. My best guess is that the new version of the file does not correctly handling the situation where no dependencies are found. Has anyone else seen this? I have not see this issue raised on the Jira page yet. --- Todd Thiessen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Probable bug with maven-war-plugin-2.1-alpha-2
> I checkedout the source and compared it with alpha 1 and it looks like > there were a lot of changes to file WebappStructure.java:109, the file > throwing the NullPointerException. My best guess is that the new version > of the file does not correctly handling the situation where no > dependencies are found. > > Has anyone else seen this? I have not see this issue raised on the Jira > page yet. Sounds like a bug -- please file it, with a sample project if you have one to share. You're probably one of very few people using Maven 2.0.10 and working on a WAR project with zero dependencies. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Probable bug with maven-war-plugin-2.1-alpha-2
Reported and fixed in the next version. See http://jira.codehaus.org/browse/MWAR-170 Todd Thiessen wrote: > I recently upgraded Maven 2.0.10 and noticed that this version of Maven > has changed the default version of the maven-war-plugin to 2.1-alpha-2. > When using this version of the plugin I get the following error: > > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappS > tructure.java:109) > at > org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(Web > appStructure.java:288) > at > org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask. > performPackaging(DependenciesAnalysisPackagingTask.java:46) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo. > java:439) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(Abstract > WarMojo.java:375) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa > nager.java:453) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default > LifecycleExecutor.java:559) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec > ycle(DefaultLifecycleExecutor.java:500) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL > ifecycleExecutor.java:479) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle > Failures(DefaultLifecycleExecutor.java:331) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( > DefaultLifecycleExecutor.java:292) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:142) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > I have reverted back to alpha-1 of the plugin and everythings works > fine. > > I checkedout the source and compared it with alpha 1 and it looks like > there were a lot of changes to file WebappStructure.java:109, the file > throwing the NullPointerException. My best guess is that the new version > of the file does not correctly handling the situation where no > dependencies are found. > > Has anyone else seen this? I have not see this issue raised on the Jira > page yet. > > --- > Todd Thiessen > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Probable bug with maven-war-plugin-2.1-alpha-2
Thanks. Any word on when there will be a new release of the plugin? --- Todd Thiessen > -Original Message- > From: Dennis Lundberg [mailto:denn...@apache.org] > Sent: Tuesday, February 24, 2009 5:19 PM > To: Maven Users List > Subject: Re: Probable bug with maven-war-plugin-2.1-alpha-2 > > Reported and fixed in the next version. > See http://jira.codehaus.org/browse/MWAR-170 > > Todd Thiessen wrote: > > I recently upgraded Maven 2.0.10 and noticed that this version of > > Maven has changed the default version of the > maven-war-plugin to 2.1-alpha-2. > > When using this version of the plugin I get the following error: > > > > [INFO] > > > -- > > -- > > [ERROR] FATAL ERROR > > [INFO] > > > -- > > -- > > [INFO] null > > [INFO] > > > -- > > -- > > [INFO] Trace > > java.lang.NullPointerException > > at > > > org.apache.maven.plugin.war.util.WebappStructure.getDependencies(Webap > > pS > > tructure.java:109) > > at > > > org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(W > > eb > > appStructure.java:288) > > at > > > org.apache.maven.plugin.war.packaging.DependenciesAnalysisPack > agingTask. > > performPackaging(DependenciesAnalysisPackagingTask.java:46) > > at > > > org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(Abstra > ctWarMojo. > > java:439) > > at > > > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(Abstra > > ct > > WarMojo.java:375) > > at > > > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) > > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) > > at > > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin > > Ma > > nager.java:453) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau > > lt > > LifecycleExecutor.java:559) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif > > ec > > ycle(DefaultLifecycleExecutor.java:500) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul > > tL > > ifecycleExecutor.java:479) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand > > le > > Failures(DefaultLifecycleExecutor.java:331) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment > > s( > > DefaultLifecycleExecutor.java:292) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif > > ec > > ycleExecutor.java:142) > > at > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > > av > > a:39) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess > > or > > Impl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > > at > > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > > at > > > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > > > I have reverted back to alpha-1 of the plugin and everythings works > > fine. > > > > I checkedout the source and compared it with alpha 1 and it > looks like > > there were a lot of changes to file > WebappStructure.java:109, the file > > throwing the NullPointerException. My best guess is that the new > > version of the file does not correctly handling the > situation where no > > dependencies are found. > > > > Has anyone else seen this? I have not see this issue raised on the > > Jira page yet. > > > > --- > > Todd Thiessen > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Probable bug with maven-war-plugin-2.1-alpha-2
It's on my medium term todo list. I'll probably release it after I finish Site Plugin 2.0 et al. Todd Thiessen wrote: > Thanks. > > Any word on when there will be a new release of the plugin? > > --- > Todd Thiessen > > >> -Original Message- >> From: Dennis Lundberg [mailto:denn...@apache.org] >> Sent: Tuesday, February 24, 2009 5:19 PM >> To: Maven Users List >> Subject: Re: Probable bug with maven-war-plugin-2.1-alpha-2 >> >> Reported and fixed in the next version. >> See http://jira.codehaus.org/browse/MWAR-170 >> >> Todd Thiessen wrote: >>> I recently upgraded Maven 2.0.10 and noticed that this version of >>> Maven has changed the default version of the >> maven-war-plugin to 2.1-alpha-2. >>> When using this version of the plugin I get the following error: >>> >>> [INFO] >>> >> -- >>> -- >>> [ERROR] FATAL ERROR >>> [INFO] >>> >> -- >>> -- >>> [INFO] null >>> [INFO] >>> >> -- >>> -- >>> [INFO] Trace >>> java.lang.NullPointerException >>> at >>> >> org.apache.maven.plugin.war.util.WebappStructure.getDependencies(Webap >>> pS >>> tructure.java:109) >>> at >>> >> org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(W >>> eb >>> appStructure.java:288) >>> at >>> >> org.apache.maven.plugin.war.packaging.DependenciesAnalysisPack >> agingTask. >>> performPackaging(DependenciesAnalysisPackagingTask.java:46) >>> at >>> >> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(Abstra >> ctWarMojo. >>> java:439) >>> at >>> >> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(Abstra >>> ct >>> WarMojo.java:375) >>> at >>> >> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) >>> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) >>> at >>> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin >>> Ma >>> nager.java:453) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau >>> lt >>> LifecycleExecutor.java:559) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif >>> ec >>> ycle(DefaultLifecycleExecutor.java:500) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul >>> tL >>> ifecycleExecutor.java:479) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand >>> le >>> Failures(DefaultLifecycleExecutor.java:331) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment >>> s( >>> DefaultLifecycleExecutor.java:292) >>> at >>> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif >>> ec >>> ycleExecutor.java:142) >>> at >>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j >>> av >>> a:39) >>> at >>> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess >>> or >>> Impl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:585) >>> at >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>> at >>> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >>> >>> I have reverted back to alpha-1 of the plugin and everythings works >>> fine. >>> >>> I checkedout the source and compared it with alpha 1 and it >> looks like >>>
