[ http://jira.codehaus.org/browse/MOJO-223?page=comments#action_82607 ] Corridor Software Developer commented on MOJO-223: --------------------------------------------------
So what are we proposing here? The patch is against the xdoclet/xdoclet-1.2.3.jar. Mojo doesn't own that artifact, so the best we can do is make a patch to a copy on our snapshot repository & to test against, then release to the mojo repo. Problem is, I cannot create the root directory (my god! I almost said folder!), i.e., xdoclet in these environments. So it have to be under org.codehaus.mojo.xdoclet... and the dependency for xdoclet-maven-plugin updated to correspond to this "1.2.3.1" hack. Now, this will work, but it will be awfully confusing for kenney or whomever chooses to update the plugin in the future. Is this the only alternative? Brett, Kenney & Trygvis, would you please chime in on this? I'd like to get a second opinion before I create some sort of bride-of-frankenstein xdoclet-maven-plugin-1.0-beta-2-SNAPSHOT monster... Alternatives? > xdoclet maven plugin: Ambiguous subtask definition exception > ------------------------------------------------------------ > > Key: MOJO-223 > URL: http://jira.codehaus.org/browse/MOJO-223 > Project: Mojo > Issue Type: Bug > Components: xdoclet > Environment: maven 2.0.1 > Reporter: Corridor Software Developer > Assigned To: Corridor Software Developer > Priority: Blocker > Attachments: xdoclet.patch > > > Get the following error when building a project with webapp and ejb projects > which both use the maven xdoclet plugin. Running the installs from the > individual project dirs does not produce the same result: > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Error executing ant tasks > Embedded error: Ambiguous subtask definition for logical name > service-endpoint: xdoclet.modules.ejb.intf.ServiceEndpointSubTask and > xdoclet.modules.web.ServiceEndpointSubTask > [INFO] > ---------------------------------------------------------------------------- > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant > tasks > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) > 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:249) > 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: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: Error executing > ant tasks > at > org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:77) > at org.codehaus.mojo.xdoclet.XDocletMojo.execute(XDocletMojo.java:102) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:432) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:530) > ... 16 more > Caused by: Ambiguous subtask definition for logical name service-endpoint: > xdoclet.modules.ejb.intf.ServiceEndpointSubTask and > xdoclet.modules.web.ServiceEndpointSubTask > at xdoclet.DocletTask.registerModules(DocletTask.java:566) > at xdoclet.DocletTask.createDynamicElement(DocletTask.java:336) > at > org.apache.tools.ant.IntrospectionHelper.getNestedCreator(IntrospectionHelper.java:505) > at > org.apache.tools.ant.IntrospectionHelper.getElementCreator(IntrospectionHelper.java:583) > at > org.apache.tools.ant.UnknownElement.handleChild(UnknownElement.java:545) > at > org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:326) > at > org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:182) > at > org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:158) > at org.apache.tools.ant.Task.perform(Task.java:363) > at org.apache.tools.ant.Target.execute(Target.java:341) > at > org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:71) > ... 19 more > the task for the ejb: > <ejbdoclet destdir="${project.build.outputDirectory}"> > <fileset dir="src/main/java"/> > <entitycmp/> > <deploymentdescriptor > destDir="${project.build.outputDirectory}/META-INF" /> > </ejbdoclet> > the task for the webapp: > <webdoclet > destdir="${project.build.directory}/${project.build.finalName}/WEB-INF" > verbose="true" > excludedtags="@version,@author"> > <fileset dir="${basedir}/src/main/java" > includes="**/*.java" /> > <strutsconfigxml > destDir="${project.build.directory}/${project.build.finalName}/WEB-INF"/> > </webdoclet> -- 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 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
