RE: Assembly problem: Error Not a v4.0.0 POM
Hi George, I created an issue for this in jira (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it would help? Regards, Christopher -Original Message- From: George Armhold [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 7:49 PM To: users@maven.apache.org Subject: RE: Assembly problem: Error Not a v4.0.0 POM Hi John, I'm also interested in this fix for the assembly plugin. Could you kindly commit it, or at least post it here so we can apply it locally? Thanks, George Chris Helck wrote: Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] - - -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa u lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi f ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau l tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan d le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen t s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi f ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces s or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(A b st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi n Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa u lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.a d dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.e x ec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyP h as e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.crea t eA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(A b st ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default M av
Re: Assembly problem: Error Not a v4.0.0 POM
You two should try the snapshot of the assembly plugin on the repository: http://people.apache.org/repo/m2-snapshot-repository While it's not great practice to load plugins from here, you can verify that this problem has been fixed already. It's just not quite ready for release, due to some other issues that need fixing still. -john On Jul 11, 2007, at 9:31 AM, Chris Helck wrote: Hi George, I created an issue for this in jira (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it would help? Regards, Christopher -Original Message- From: George Armhold [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 7:49 PM To: users@maven.apache.org Subject: RE: Assembly problem: Error Not a v4.0.0 POM Hi John, I'm also interested in this fix for the assembly plugin. Could you kindly commit it, or at least post it here so we can apply it locally? Thanks, George Chris Helck wrote: Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] - - -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa u lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL i f ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau l tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa n d le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme n t s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi f ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces s or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute( A b st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPlugi n Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa u lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. a d dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. e x ec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssembly P h as e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.cre a t eA rchive(DefaultAssemblyArchiver.java:98
RE: Assembly problem: Error Not a v4.0.0 POM
Thanks Chris, I have voted for it. George Chris Helck wrote: Hi George, I created an issue for this in jira (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it would help? Regards, Christopher -Original Message- From: George Armhold [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 7:49 PM To: users@maven.apache.org Subject: RE: Assembly problem: Error Not a v4.0.0 POM Hi John, I'm also interested in this fix for the assembly plugin. Could you kindly commit it, or at least post it here so we can apply it locally? Thanks, George Chris Helck wrote: Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] - - -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa u lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi f ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau l tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan d le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen t s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi f ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces s or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(A b st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi n Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa u lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.a d dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.e x ec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyP h as e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.crea t eA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(A b st ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM
Re: Assembly problem: Error Not a v4.0.0 POM
I just tried the 2.2-beta-2-SNAPSHOT from that repo, and unfortunately the problem still exists. George John Casey-5 wrote: You two should try the snapshot of the assembly plugin on the repository: http://people.apache.org/repo/m2-snapshot-repository While it's not great practice to load plugins from here, you can verify that this problem has been fixed already. It's just not quite ready for release, due to some other issues that need fixing still. -john On Jul 11, 2007, at 9:31 AM, Chris Helck wrote: Hi George, I created an issue for this in jira (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it would help? Regards, Christopher -Original Message- From: George Armhold [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 7:49 PM To: users@maven.apache.org Subject: RE: Assembly problem: Error Not a v4.0.0 POM Hi John, I'm also interested in this fix for the assembly plugin. Could you kindly commit it, or at least post it here so we can apply it locally? Thanks, George Chris Helck wrote: Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] - - -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa u lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL i f ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (Defau l tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa n d le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme n t s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLi f ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces s or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute( A b st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPlugi n Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Defa u lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. a d dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. e x ec ute(AddDependencySetsTask.java:90
RE: Assembly problem: Error Not a v4.0.0 POM
Hi John, Thanks for the reply. I tried using the snapshot version, but still get an error. First I added the following lines to my POM dependencies dependency groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2-SNAPSHOT/version scopeplugin/scope /dependency /dependencies repositories repository snapshots enabledtrue/enabled /snapshots idcentral-snaps/id nameMaven Repository Snaps/name urlhttp://people.apache.org/repo/m2-snapshot-repository/url /repository /repositories pluginRepositories pluginRepository releases updatePolicynever/updatePolicy /releases snapshots enabledtrue/enabled /snapshots idcentral-plugin-snaps/id nameMaven snap Plugin Repository/name urlhttp://people.apache.org/repo/m2-snapshot-repository/url /pluginRepository /pluginRepositories Everything seemed to download ok. When I ran (with -X) I get this stack trace: [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:commons:jar:3.0.5-SNAPSHOT; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:commons:jar:3.0.5-SNAPSHOT; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:commons:jar:3.0.5-SNAPSHOT; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:115) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec ute(AddDependencySetsTask.java:91) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1299) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1270) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:471) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:225) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:110) ... 22 more [INFO] [INFO] Total
RE: Assembly problem: Error Not a v4.0.0 POM
Hi John, I'm also interested in this fix for the assembly plugin. Could you kindly commit it, or at least post it here so we can apply it locally? Thanks, George Chris Helck wrote: Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] -- -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ad dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ex ec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPh as e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.creat eA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab st ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM av enProjectBuilder.java:1299) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM av enProjectBuilder.java:1270) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos it ory(DefaultMavenProjectBuilder.java:471) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepositor y( DefaultMavenProjectBuilder.java:225
RE: Assembly problem: Error Not a v4.0.0 POM
Was this ever fixed? I still see it in maven 2.0.6 -- am about to try with 2.0.7. I don't see any direct mention of the problem in the jira thingy. Thanks, Christopher Helck -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 3:53 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] -- -- [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau lt LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul tL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand le Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif ec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j av a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess or Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab st ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin Ma nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau lt LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ad dD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ex ec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPh as e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.creat eA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab st ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM av enProjectBuilder.java:1299) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM av enProjectBuilder.java:1270) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepos it ory(DefaultMavenProjectBuilder.java:471) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepositor y( DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepositor y( DefaultMavenProjectBuilder.java:235) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ad dD
Re: Assembly problem: Error Not a v4.0.0 POM
Actually, the stacktrace for this error would be pretty valuable, just to see whether it's coming from the assembly plugin itself, or from maven's core...Maven's supposed to detect and ignore legacy poms. -john On 5/7/07, Chris Helck [EMAIL PROTECTED] wrote: I have an error that I don't understand. I have a maven 1 project that builds a jar file called pps-3.0.2.jar. The jar (and it's pom) are moved into my legacy style repository. I have a maven 2 project that depends on pps-3.0.2. It compiles and tests the code fine. During the assembly it is suppose to creates a directory of dependent jar files and it blows up with the message: - Error building POM (may not be this project's POM). Project ID: ebs:pps POM Location: /home/chelck/.m2/repository/ebs/pps/3.0.2/pps-3.0.2.pom Reason: Not a v4.0.0 POM. --- Running with -X doesn't supply any more usefull info. In a sense the error is correct: pps-3.0.2.pom is not v4.0.0 -- it's legacy. So why is mvn trying to build it's POM and why doesn't it realize it's a legacy pom? Thanks, Christopher Helck ** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the Information) is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates (ICAP) or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ** -- John Casey --- Maven Developer (http://maven.apache.org) --- Blog: http://www.ejlife.net/blogs/buildchimp
RE: Assembly problem: Error Not a v4.0.0 POM
I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1299) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1270) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:471) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:235) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:109) ... 22 more [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Tue May 08 14:49:00 EDT 2007 [INFO] Final Memory: 9M/18M [INFO] -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 12:22 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0 POM Actually, the stacktrace for this error would be pretty valuable, just to see whether it's coming from the assembly plugin itself, or from maven's core...Maven's supposed to detect and ignore legacy poms. -john On 5/7/07, Chris Helck [EMAIL PROTECTED] wrote: I have an error that I don't understand. I have a maven 1 project that builds a jar file called pps-3.0.2.jar. The jar (and it's pom) are moved into my legacy style repository. I have
Re: Assembly problem: Error Not a v4.0.0 POM
Okay, I've found the problem; it's in the assembly plugin, where I'm not using the correct method to retrieve the transitive POM set (there is one that allows stub models when it detects a non-4.0.0 POM, and another that doesn't). I'm fixing it now, but it won't be released for a little while (there are several more things that need to go into that release). Thanks, and sorry for the inconvenience. -john On 5/8/07, Chris Helck [EMAIL PROTECTED] wrote: I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1. I'll be happy to supply more data it needed. Stack trace is below. Thanks, Christopher Helck [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:302) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM. at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:114) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec ute(AddDependencySetsTask.java:90) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas e.execute(DependencySetAssemblyPhase.java:54) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA rchive(DefaultAssemblyArchiver.java:98) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst ractAssemblyMojo.java:278) ... 18 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1299) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav enProjectBuilder.java:1270) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:471) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:235) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD ependencySet(AddDependencySetsTask.java:109) ... 22 more [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Tue May 08 14:49:00 EDT 2007 [INFO] Final Memory: 9M/18M [INFO] -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 12:22 PM To: Maven Users List Subject: Re: Assembly problem: Error Not a v4.0.0
