[M2] assembly plugin - best practices and concepts - questions OR how do i move files around using maven2

[Ruel Loehr <ru...@jboss.com>]

I've setup a multiproj build using maven2 which covers a subset of my
project.  (I'm basically doing a proof of concept type thing).  The
portion I now need to explore is building my distribution.

I've ran into a few questions here which I can't find in the
documentation or the mailing lists. 

Our legacy build sets up an output structure sort of like this:

/build/output/servers
                     /all
                     /minimal
                     /default

Inside the all, minimal, and default directories, I have different
subsets of the jars built from my project, as well as a number of
thirdparty dependencies.

I have a few tasks to cover:
1)  Setting up a directory structure similar to this
2)  Copying built jars into these directories
3)  Copying thirdparty jars into these directories?

First off, is the assembly plugin adequate for this task?
Assembly:assembly doesn't look quite right, as it just builds a bin
file.   Assembly:directory I suspect is the one to use.  Does it use the
same style of descriptor file?

So the net of this is, after building, it is common to move the
artifacts of the build into an ordered structure.   What is the best way
to accomplish this using m2?





Ruel Loehr
JBoss QA
 
-----------------------------
512-626-2782
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] assembly plugin - best practices and concepts - questions OR how do i move files around using maven2

[Edwin Punzalan <ep...@exist.com>]

Hi,

The assembly plugin accepts an xml configuration file called "assembly 
descriptor" instructing it how to build your project.  You are right 
that assembly:assembly can create a bin jar but that is just one of the 
many things it can do.  Read 
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html for 
more info on how to use/configure the assembly plugin.

By executing assembly:assembly with three different configurations, you 
can setup your desired builds.

If you think the assembly plugin is still lacking capabilities, you can 
create your own plugin to tailor the way you build your projects since 
the plugin will be usable to other projects anyway.


Ruel Loehr wrote:

>I've setup a multiproj build using maven2 which covers a subset of my
>project.  (I'm basically doing a proof of concept type thing).  The
>portion I now need to explore is building my distribution.
>
>I've ran into a few questions here which I can't find in the
>documentation or the mailing lists. 
>
>Our legacy build sets up an output structure sort of like this:
>
>/build/output/servers
>                     /all
>                     /minimal
>                     /default
>
>Inside the all, minimal, and default directories, I have different
>subsets of the jars built from my project, as well as a number of
>thirdparty dependencies.
>
>I have a few tasks to cover:
>1)  Setting up a directory structure similar to this
>2)  Copying built jars into these directories
>3)  Copying thirdparty jars into these directories?
>
>First off, is the assembly plugin adequate for this task?
>Assembly:assembly doesn't look quite right, as it just builds a bin
>file.   Assembly:directory I suspect is the one to use.  Does it use the
>same style of descriptor file?
>
>So the net of this is, after building, it is common to move the
>artifacts of the build into an ordered structure.   What is the best way
>to accomplish this using m2?
>
>
>
>
>
>Ruel Loehr
>JBoss QA
> 
>-----------------------------
>512-626-2782
>Yahoo: ruelloehr
>Skype: ruelloehr
>AOL: dokoruel
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org