dependency management not working
---------------------------------
Key: NPANDAY-327
URL: https://issues.apache.org/jira/browse/NPANDAY-327
Project: NPanday
Issue Type: Bug
Affects Versions: 1.2.1, 1.2
Environment: windows 7 32 bits. maven 2.0.9, java 6 sdk eng.
Reporter: sergio rupena
I have a parent pom that declares a config section like this:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>Logging</groupId>
<artifactId>log4net</artifactId>
<version>1.2.10.0</version>
<type>dotnet-library</type>
</dependency>
</dependencies>
</dependencyManagement>
When I refer to my parent pom and use the following section (without explicitly
denoting the version)
<dependency>
<groupId>Logging</groupId>
<artifactId>log4net</artifactId>
<type>dotnet-library</type>
</dependency>
I can successfully do a maven test. (mvn test)
However, when I do a maven install I get the following error:
[INFO] Trace
java.lang.NullPointerException
at npanday.dao.Project.hashCode(Project.java:329)
at java.util.HashMap.put(HashMap.java:372)
at java.util.HashSet.add(HashSet.java:200)
at npanday.dao.Project.addProjectDependency(Project.java:204)
at npanday.dao.ProjectFactory.createProjectFrom(ProjectFactory.java:148)
at
npanday.dao.impl.ProjectDaoImpl.storeModelAndResolveDependencies(ProjectDaoImpl.java:837)
at
npanday.artifact.impl.ArtifactInstallerImpl.installArtifactWithPom(ArtifactInstallerImpl.java:399)
at npanday.plugin.install.InstallerMojo.execute(InstallerMojo.java:177)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
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 think that dependency management is one of the great features from maven, but
it doesn't seem to be working in npanday.
/joe
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
