> [I wrote:} > Sent: Thursday, August 30, 2007 7:29 PM > To: [email protected] > Subject: Aggregator project war plugin context > > 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-ignore > d-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.) >
I have confirmed this issue exists when using the ejb plugin. The optional field is not set when the project is built from the parent project. > 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. Right now I'm lost on where to address this. I thought perhaps DefaultMavenProjectHelper needed to attach the ejb-client artifact differently, now I see this probably the wrong direction. I could try to address this in the war plugin by adding an additional step to check the dependency list, but I'm not sure I'll get the <optional> information here either. Any pointers on how to get the war project's dependencies <optional> attribute into this attached artifact? Also, I'm not sure where to post the sample project to re-create this. I think I will start with the war plugin? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
