We are mixing several issues here though.

1. Ruel's attempt to replicate the build using maven was a question as
to whether maven could handle a screwed up build structure.
2. Since this is not ideal and maven has an even stricter notion of a
source tree/per artificat, should the build be restructured to more
closely mirror this notion to remove the hacks Ruel used.
3. There are additional changes being discussed with regard to breaking
up existing cvs modules and artifacts (common -> jboss-common.jar) to
separate out projects like jbossxb which should be evolvoing
indepedently of the app server.
4. svn blah blah.  

The point I take from Adrian is that if we have to do something beyond
what maven supports via an existing plugin, it needs to be encapsulated
in a custom plugin. It cannot be ad hoc scripting in the build
descriptors.

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Ruel Loehr
> Sent: Monday, February 13, 2006 8:44 AM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: Maven build and scripting was Re: [JBoss-dev] 
> RE: Ongoing build changes: was RE: [JBoss-dev] 
> OntheedgeoftheMavencliff
> 
> In our current configuration, the jar plugin is not adequate. 
>  For a given module, we need to build many artifacts (see the 
> build forum post
> here):
> 
> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=39233
> 33#3923333
> 
> I spent some time looking at the assembly plugin as well, but 
> did not find it suitable for the following reasons.
> 
> 1)  It must be called manually.   We don't want to have to 
> call this for
> each module.
> 2)  It lacks functionality for adding classes from 
> dependencies into a jar.  E.g, I want to create a jar and add 
> some classes from another modules output.
> 3)  It seemed to me overall that the assembly plugin was best 
> used for creating the final project structure, not for 
> building the outputs of each subproject.
> 
> If I am wrong, please correct me.
> 
> Ruel Loehr
> JBoss QA


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to