I have been working on migrating the pieces from our m102 environment and haven't gotten back to this problem. I could use some hints on how to set up an assembly extension that would allow me to do the consolidation of web.xml and portlet.xml values as the bits are assembled (at least a pointer to an example in the current code and how to add a custom one to the mix). I am guessing that I should use the dependencies as the means to define which war files to assemble (assuming I can get at that list from the mojo in a form that will allow me to get to the project build directories so I can assemble from them), since that will automatically take care of the processing order problem.
-----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 06:33 To: Maven Developers List Subject: Re: Question About Reactor Operation Sorry for the late response. Did you establish how you would do these? John has recently implemented some functionality to enable aggregation and maybe we can work through these. - Brett Allison, Bob wrote: >After doing some experimentation, I think I have a means to accomplish >what I want without altering the way the reactor works. > >I think I can convince my coworkers that we should only document the >production projects; this collapses the first two use cases into a >single use case that I think can be handled using the <module> stanza in >the POM. > >The third use case is a bit harder, but with the ability to build >Java-based plugins I think I can build a plugin to do the aggregation as >a separate process. The main things I need to figure out are: >-- How do I define a new packaging value? Looking at the m2 code, it >appears to involve something called an extension plugin but I could not >find a description of what is required to make one. >-- How do I link the items to be aggregated to the project? The likely >answer here is configuration information provided to the plugin which >does the aggregation. >-- How do I ensure that the components to be aggregated are built by the >reactor before the aggregation occurs? If I declare the components as >dependencies, what scope can I use to ensure the correct build order >without also causing the web application war files to be automatically >added to the artifact being built? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
