smartics / smartics-enforcer-rules

A collection of rules for the Maven enforcer plugin.
Other
1 stars 0 forks source link

NPE on release:prepare goal is executed #7

Closed nfalco79 closed 4 years ago

nfalco79 commented 4 years ago

We start to use these additional rules. In particula the NoSnapshotsInDependencyManagementRule for our business.

Our first releases run witn mvn release:prepare release:perform now fails with this NPE:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce (enforce-build) on project com.thedigitalstack.fileaccess.web: Execution enforce-build of goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce failed. NullPointerException -> [Help 1]
...
[INFO] Caused by: java.lang.NullPointerException
[INFO]     at de.smartics.maven.enforcer.rule.NoSnapshotsInDependencyManagementRule.execute (NoSnapshotsInDependencyManagementRule.java:98)
[INFO]     at org.apache.maven.plugins.enforcer.EnforceMojo.execute (EnforceMojo.java:205)
[INFO]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
[INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
[INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
[INFO]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
[INFO]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
[INFO]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
[INFO]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
[INFO]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)

This happens when the release plugin (3.0.0-M1) internally launch other maven reactor to prepare the pom.xml versions.

nfalco79 commented 4 years ago

I'm sorry was already fixed in 1.0.2