Hi,
We have Websphere ejb plugin which we modeled after the existing ejb plugin.
(We use the Websphere ejbDeploy command instead to generate stubs, etc.)
We are facing an issue related to this posting:
http://www.nabble.com/%3Coptional%3Etrue%3C-optional%3E-ignored-with-build-from-parent-t4349741s177.html#a12393564
It seems the ejb-client dependency comes into the war plugin incorrectly if
building from an aggregator project.
Since we don't do a lot differently from the existing ejb plugin I'm wondering
if this is an issue for both
(i can try this later if no one knows off hand.)
The root issue is...
The iteration in the war plugin's ArtifactsPackagingTask.performPackaging( ...)
is finding the the ejb-client artifact "optional" field false when it is
declared true in the web module's pom
... also of interest is the fact that the artifact is of type DefaultArtifact
and not of type ActiveProjectArtifact.
Don't know if that's the issue... if so maybe that something that the
DefaultMavenProjectHelper.attachArtifact
should or could handle?
I'm having trouble finding where in the Maven code the dependency list is build
up for
ArtifactsPackagingTask.performPackaging( ...) during execution of a war module
in an aggregator project.
Or even how I would fix this so that the artifact's optional attribute is
correct.
Let me know if you have any thoughts on a direction to look in.
