maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Commented: (MNG-2899) In cases where ${version} is used in depMan we get null versions in attached artifacts
Date Sun, 25 Mar 2007 18:15:34 GMT


Jason van Zyl commented on MNG-2899:

Dan, I'm sure this is being caused by the same thing that caused the last problem in yoko.
I'm sure we can track it down and fix it. For some reason artifact info is not making it though
when ${version} is being used.  From a brief look it seems that because depMan was never used
before consistently the null makes it through in the process and just propagates because we
don't check it and just assume it will be there. It resolves to an empty string which is no
longer null and makes it through the gate.

> In cases where ${version} is used in depMan we get null versions in attached artifacts
> --------------------------------------------------------------------------------------
>                 Key: MNG-2899
>                 URL:
>             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:
> java.lang.NullPointerException
>         at org.apache.maven.project.artifact.AttachedArtifact.getVersion(
>         at org.apache.maven.artifact.DefaultArtifact.validateIdentity(
>         at org.apache.maven.artifact.DefaultArtifact.<init>(
>         at org.apache.maven.project.artifact.AttachedArtifact.<init>(
>         at org.apache.maven.project.DefaultMavenProjectHelper.attachArtifact(
>         at org.apache.maven.plugin.jar.AbstractJarMojo.execute(
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>         at org.apache.maven.DefaultMaven.doExecute(
>         at org.apache.maven.DefaultMaven.execute(
>         at org.apache.maven.cli.MavenCli.main(
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at org.codehaus.classworlds.Launcher.launchEnhanced(
>         at org.codehaus.classworlds.Launcher.launch(
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
>         at org.codehaus.classworlds.Launcher.main(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message