'mvn -n' does not work after update to 1.393

[Oli]

Hi,

I updated to v1.393 yesterday. Now our parent project fails with the
following error message:

...
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/
workspace/../OpmCommon of /home/hudson/.hudson/jobs/opm_OpmLibWS/
workspace/pom.xml does not exist @
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/
workspace/../OpmChannelWs of /home/hudson/.hudson/jobs/opm_OpmLibWS/
workspace/pom.xml does not exist @
...

Maven is started with 'mvn -N clean install' so the other modules are
not needed. This works with the old version of Hudson (unfortunately I
don't know which version it was). Is there a workaround available?

[olive...@gmail.com]

Hello,

When this issue is ?

During the Pom Parsin phase or during the build ?

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

[oliver]

Hello,

it happens during POM parsing. Here the complete log:

Gestartet durch Benutzer hudson
[workspace] $ cvs -q -z3 update -PdC -D "Wednesday, January 12, 2011 8:46:00 AM UTC"
$ no changes detected
Found mavenVersion 3.0.1 from file jar:file:/usr/local/maven/lib/maven-core-3.0.1.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
Parsing POMs
ERROR: POMs konnten nicht geparst werden
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 60, column 15
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 69, column 15
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../OpmCommon of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../OpmChannelWs of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../OpmClientCommon of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../DialogManager of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../SpreadsheetBridge of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../OPMCalcListener of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[ERROR] Child module /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/../CalcBridge of /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml does not exist @ 
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-jxr-plugin is missing. @ line 304, column 15
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 316, column 15
[WARNING] 'reporting.plugins.plugin.version' for org.codehaus.mojo:findbugs-maven-plugin is missing. @ line 338, column 15

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1097)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:985)
	at hudson.FilePath.act(FilePath.java:756)
	at hudson.FilePath.act(FilePath.java:738)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:691)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:527)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1362)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:401)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)

and here the log from last successful build (before the update):

Build wurde durch eine SCM-Änderung ausgelöst.
[workspace] $ cvs -q -z3 update -PdC -D "Wednesday, December 15, 2010 3:25:13 PM UTC"
P pom.xml
$ computing changelog
Parsing POMs
[workspace] $ /usr/java/jdk1.6/bin/java -Xms512m -Xmx1024m -XX:MaxPermSize=256m -cp /home/hudson/.hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.374.jar:/usr/local/maven/boot/classworlds-1.1.jar hudson.maven.agent.Main /usr/local/maven /home/hudson/.hudson/war/WEB-INF/lib/remoting-1.374.jar /home/hudson/.hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.374.jar 52431 /home/hudson/.hudson/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar
<===[HUDSON REMOTING CAPACITY]===>���channel started
Executing Maven:  -B -f /home/hudson/.hudson/jobs/opm_OpmLibWS/workspace/pom.xml -N clean install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building OpmLibWS
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------

I have tested it also with Maven 2.2.1 so it depends not on the Maven version.

regards,

Oliver

[Richard Mortimer]

Hi,

I think that this is basically the same problem as
http://issues.hudson-ci.org/browse/HUDSON-8462
I reported that earlier this week and it was reported fixed within a few
hours. I haven't tested the fix but hopefully that should mean that the
next release fixes your problem.

Regards

Richard

On 12/01/2011 10:51, oliver wrote:
> Hello,
>
> it happens during POM parsing. Here the complete log:
>
> Gestartet durch Benutzer hudson
> [workspace] $ cvs -q -z3 update -PdC -D "Wednesday, January 12, 2011 8:46:00 AM UTC"
> $ no changes detected
> Found mavenVersion 3.0.1 from file jar:file:/usr/local/maven/lib/maven-core-3.0.1.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
> Parsing POMs
> ERROR: POMs konnten nicht geparst werden

> org.apache.maven.project.ProjectBuildingException <http://grepcode.com/search?query=org.apache.maven.project.ProjectBuildingException>: Some problems were encountered while processing the POMs:

> Am 12.01.2011 um 11:15 schrieb ol...@apache.org <mailto:ol...@apache.org>:
>
>> Hello,
>> When this issue is ?
>> During the Pom Parsin phase or during the build ?
>>
>>
>> --
>> Olivier Lamy
>> http://twitter.com/olamy

>> http://www.linkedin.com/in/olamy <http://www.linkedin.com/in/olamy>
>

[oliver]

Hi,

I don't think so. The problems are not the missing versions (they are only warnings), the problem is the missing POMs of the child modules (which are not needed for 'mvn -N ...').
When I start 'mvn -N clean install' in the workspace from the command line it works.

regards,
Oliver

[olive...@gmail.com]

Hello,

It's an issue. 

I have created an issue [1], I will try to fix that for the coming 1.394.

Watch the issue in order to know :-)

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

[1] http://issues.hudson-ci.org/browse/HUDSON-8484

[olive...@gmail.com]

So fixed and will be in the coming 1.394.

Junit added so normally such regression won't happen anymore :-)