Maven 2 & 3

null pointer exception in profile if pluginManagement section exists in pom

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.1
  • Fix Version/s: 2.0.5
  • Component/s: POM
  • Labels:
    None
  • Environment:
    windows xp, java 1.4
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

TO TEST simply run mvn projecthelp:effective-pom -Dbark=true with the attached pom

the attached pom appears to be legal, but complains of a null pointer exception:

if the plugin management section is removed then the null pointer goes away and the plugins are added as expected;

here is the trace:

C:\ditech\workspace\barks>mvn projecthelp:effective-pom -Dbark=true
[INFO] Scanning for projects...
[INFO] -------------------------------------------------------------------------

[ERROR] FATAL ERROR
[INFO] -------------------------------------------------------------------------

[INFO] null
[INFO] -------------------------------------------------------------------------

[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.project.injection.DefaultProfileInjector.injectPlugi
ns(DefaultProfileInjector.java:147)
at org.apache.maven.project.injection.DefaultProfileInjector.injectBuild
(DefaultProfileInjector.java:134)
at org.apache.maven.project.injection.DefaultProfileInjector.inject(Defa
ultProfileInjector.java:80)
at org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfi
les(DefaultMavenProjectBuilder.java:1037)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
efaultMavenProjectBuilder.java:838)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:594)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
le(DefaultMavenProjectBuilder.java:304)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
nProjectBuilder.java:274)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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)
[INFO] -------------------------------------------------------------------------

[INFO] Total time: < 1 second
[INFO] Finished at: Wed Jan 11 16:26:16 MST 2006
[INFO] Final Memory: 1M/2M
[INFO] -------------------------------------------------------------------------

Issue Links

Activity

Hide
Maria Odea Ching added a comment -

Already fixed in svn.
When I executed mvn in the attached sample pom using maven-2.0.2, the "null" exception showed up.
But when I executed it using maven-2.0.4 and maven-2.1-SNAPSHOT, the "null" exception has already been fixed.

Show
Maria Odea Ching added a comment - Already fixed in svn. When I executed mvn in the attached sample pom using maven-2.0.2, the "null" exception showed up. But when I executed it using maven-2.0.4 and maven-2.1-SNAPSHOT, the "null" exception has already been fixed.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
Not Specified
Original Estimate - Not Specified
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
7h
Time Spent - 7 hours