You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Erick Dovale <er...@carosys.com> on 2005/09/29 19:47:35 UTC

[Fwd: Re: Assembly plugin -- couple of questions [m2a3]]

Hello there,

I was trying to do exactly what this email is explaining below and had 
exactly the same problem now using M2b1 which is that m2 tries to run 
the assembly plugin on each and every subproject.  If I want to generate 
a single assembly file containing all sub projects and their 
dependencies do I still have to go by creating another project that 
depends on the subprojects??
Right now I am using the assembly plugin in this manner, having an extra 
project that depends on the projects I need to include in the assembly. 
The problem with this approach is that because the real projects are now 
dependencies as apposed to artifacts I have no controll over where they 
will be located in the final assembly file.. or I should say I have no 
total control over theml I can move them around but as a dependency and 
all the dependencies will go "bundled" with them. Is there a way to 
specify location for individual dependencies in the assembly 
descriptor?? Or maybe m2b1 has a way to tweek the way the assmbly plugin 
is invoked.
Any hint will be very much appreciated.

Thanks
edovale

-------- Original Message --------
Subject: 	Re: Assembly plugin -- couple of questions [m2a3]
Date: 	Sun, 14 Aug 2005 13:09:09 +1000
From: 	Brett Porter <br...@gmail.com>
Reply-To: 	Maven Users List <us...@maven.apache.org>
To: 	Maven Users List <us...@maven.apache.org>
References: 	<20...@web53408.mail.yahoo.com>

This is eomthing we want to make possible in beta-1.

In Maven 1 (and what we have supported so far), aggregation was done
through a separate project, pulling in the dependencies (eg, an EAR).

However, we want to support top level aggregation that pulls in
subprojects instead, as well.

A workaround is to create a suproject that depends on all the modules
you want to aggregate and includes them (their transitive deps will
also be included).

- Brett

On 8/13/05, Sidart Kurias <si...@yahoo.com> wrote:
> All,
> 
> I am trying to build an assembly for a multiproject
> setup in m2a3.
> 
> I would like to verify what I am doing is ok (even if
> it may  not be correct).
> 
> What I would like to do is to build one tar/zip
> containing the jars (and dependencies) of all
> subprojects.
> 
> I have defined an assembly  descriptor only in the
> parent project. This descriptor defines a fileset for
> each subproject. Each fileset identifies the files I
> want to pick up from that particular subproject.
> 
> This works fine. But since this is a multiproject
> build, after building the parent project, m2 tries to
> run the assembly goal the subprojects(modules) and
> fails (right now this is not an issue for me). I guess
> the way the assembly pluginis meant to work is to have
> individual descriptors for the subprojects(I suppose
> they could be empty descriptors in my case). is this
> understanding correct?
> 
> I haven't got the dependencies to be included as yet.
> My question is - are the dependencies that the
> assembly plugin expects to be defined in the
> dependencyset element specific to that project or can
> I  define the dependencies at the parent project level
> itself, even if they are really dependencies for the
> sub projects.
> 
> Thanks
> Sid
> 
> 
> 
> 
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
> 
> 
> ---------------------------------------------------------------------
> 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

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

Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]

Posted by Erick Dovale <er...@carosys.com>.

Either I am missing somethinghere or we have some bug hanging around.
I did what you suggested first and got this behaivor where the zip file 
is created but no resources (dependencies and artifacts) from the 
modules is added to it.
The modules are been iterated through and the jars for each one of them 
is been created and everything but when the time for creating the 
assembly comes, none of the modules dependecies/artifacts gets added to 
the zip.
Perhaps I am missing something in the dependencySets. All I have there is:
    <dependencySets>
        <dependencySet>
            <outputDirectory>lib</outputDirectory>
        </dependencySet>
    </dependencySets>

I am assuming that this is enough as to have all the dependencies from 
all the modules and the root project to be included in the lib folder 
but apparently it is not.

Any hint at all??

Thanks

Erick.
Jason van Zyl wrote:

>On Wed, 2005-10-05 at 11:07 -0400, Erick Dovale wrote:
>  
>
>>Hi Brett,
>>I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning 
>>after downloading the m2-beta-3. It seems to be working fine except for 
>>the fact that it is not including the jars for the modules nor their 
>>dependencies. Maybe I am missing something here:
>>At first it was complaining about not being able to find the bin.xml 
>>file in the modules. I put a bin.xml just into each one of them 
>>containing the dependecySets with the output directory set exactly as it 
>>is in the bin.xml that I am pasting below and it started to work but, as 
>>I said, without anything from the modules.
>>    
>>
>
>You need to provide the path to the assembly descriptor:
>
>  <build>
>    <plugins>
>      <plugin>
>        <artifactId>maven-assembly-plugin</artifactId>
>        <version>2.0-beta-1</version>
>        <configuration>
>          <descriptor>src/main/assembly/dep.xml</descriptor>
>        </configuration>
>      </plugin>
>    </plugins>
>  </build>
>
>And you only need to put it in that single location, you don't need to
>put in each project just the project that is responsible for creating an
>assembly.
>
>  
>


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

Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]

Posted by Jason van Zyl <ja...@maven.org>.

On Wed, 2005-10-05 at 11:07 -0400, Erick Dovale wrote:
> Hi Brett,
> I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning 
> after downloading the m2-beta-3. It seems to be working fine except for 
> the fact that it is not including the jars for the modules nor their 
> dependencies. Maybe I am missing something here:
> At first it was complaining about not being able to find the bin.xml 
> file in the modules. I put a bin.xml just into each one of them 
> containing the dependecySets with the output directory set exactly as it 
> is in the bin.xml that I am pasting below and it started to work but, as 
> I said, without anything from the modules.

You need to provide the path to the assembly descriptor:

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-assembly-plugin</artifactId>
        <version>2.0-beta-1</version>
        <configuration>
          <descriptor>src/main/assembly/dep.xml</descriptor>
        </configuration>
      </plugin>
    </plugins>
  </build>

And you only need to put it in that single location, you don't need to
put in each project just the project that is responsible for creating an
assembly.

-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

  -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks 

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