[jira] Closed: (MNG-2899) In cases where ${version} is used in depMan we get null versions in attached artifacts

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-2899.
------------------------------

    Resolution: Fixed

When the range has gone null, I just create it again from the version. I've build CXF, QPid, Yoko, and Geronimo, Maven, Plexus, and the ITs and it's all working. I'll get Brian Fox to check with his build as well.

> In cases where ${version} is used in depMan we get null versions in attached artifacts
> --------------------------------------------------------------------------------------
>
>                 Key: MNG-2899
>                 URL: http://jira.codehaus.org/browse/MNG-2899
>             Project: Maven 2
>          Issue Type: Bug
>            Reporter: Jason van Zyl
>         Assigned To: Jason van Zyl
>             Fix For: 2.0.6
>
>
> This is from the Yoko build for the api module. The parent POM is here:
> http://svn.apache.org/repos/asf/incubator/yoko/trunk/pom.xml
> java.lang.NullPointerException
>         at org.apache.maven.project.artifact.AttachedArtifact.getVersion(AttachedArtifact.java:122)
>         at org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:147)
>         at org.apache.maven.artifact.DefaultArtifact.<init>(DefaultArtifact.java:122)
>         at org.apache.maven.project.artifact.AttachedArtifact.<init>(AttachedArtifact.java:42)
>         at org.apache.maven.project.DefaultMavenProjectHelper.attachArtifact(DefaultMavenProjectHelper.java:53)
>         at org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:179)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira