[jira] Updated: (MNG-3821) Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets
[ http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3821: --- Fix Version/s: (was: 3.0-alpha-1) 3.0-alpha-2 Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets Key: MNG-3821 URL: http://jira.codehaus.org/browse/MNG-3821 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, POM Affects Versions: 3.0-alpha-1 Reporter: Benjamin Bentmann Assignee: Shane Isbell Fix For: 3.0-alpha-2 Running the core IT 2695 with trunk delivered: {noformat} java.io.IOException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name /plugin must match start t ag name executions from line 43 (position: START_TAG seen ...executions/plugin... @43:22) : [...] at org.apache.maven.project.builder.PomClassicTransformer.transformToDomainModel(PomClassicTransformer.java:237) at org.apache.maven.shared.model.ModelTransformerContext.transform(ModelTransformerContext.java:286) at org.apache.maven.project.builder.impl.DefaultProjectBuilder.buildFromLocalPath(DefaultProjectBuilder.java:176) at org.apache.maven.project.DefaultMavenProjectBuilder.readModelFromLocalPath(DefaultMavenProjectBuilder.java:544) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:132) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:286) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:256) at org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:93) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:147) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) [ERROR] Failed to build MavenProject instance for: M:\maven\core-it\core-it-suite\src\test\resources\mng-2695\pom.xml {noformat} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3821) Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets
[ http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3821: --- Summary: Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets (was: Project builder blows up when POM declares two plugins which use the same id for one their executions) Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets Key: MNG-3821 URL: http://jira.codehaus.org/browse/MNG-3821 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle, POM Affects Versions: 3.0-alpha-1 Reporter: Benjamin Bentmann Assignee: Shane Isbell Fix For: 3.0-alpha-1 Running the core IT 2695 with trunk delivered: {noformat} java.io.IOException: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name /plugin must match start t ag name executions from line 43 (position: START_TAG seen ...executions/plugin... @43:22) : [...] at org.apache.maven.project.builder.PomClassicTransformer.transformToDomainModel(PomClassicTransformer.java:237) at org.apache.maven.shared.model.ModelTransformerContext.transform(ModelTransformerContext.java:286) at org.apache.maven.project.builder.impl.DefaultProjectBuilder.buildFromLocalPath(DefaultProjectBuilder.java:176) at org.apache.maven.project.DefaultMavenProjectBuilder.readModelFromLocalPath(DefaultMavenProjectBuilder.java:544) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:132) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:286) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:256) at org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:93) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:147) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176) at org.apache.maven.cli.MavenCli.main(MavenCli.java:63) 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) at org.codehaus.classworlds.Launcher.main(Launcher.java:31) [ERROR] Failed to build MavenProject instance for: M:\maven\core-it\core-it-suite\src\test\resources\mng-2695\pom.xml {noformat} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira