Re: [Fwd: Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]]
I'm unable to reproduce this with anything similar. Can you boil it down to a small test case and attach it to JIRA? Thanks, Brett On 10/9/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > Hi there, > I really need someone to shade some light on the issue below. I have > exausted my resources and still I am unable to get the assembly plugin > to work properly. > > Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]]
Hi there, I really need someone to shade some light on the issue below. I have exausted my resources and still I am unable to get the assembly plugin to work properly. Thanks. Original Message Subject:Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]] Date: Thu, 06 Oct 2005 11:58:27 -0400 From: Erick Dovale <[EMAIL PROTECTED]> Reply-To: Maven Users List To: Maven Users List References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 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: lib 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: maven-assembly-plugin 2.0-beta-1 src/main/assembly/dep.xml 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/116 - Release Date: 30/09/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
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: lib 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: maven-assembly-plugin 2.0-beta-1 src/main/assembly/dep.xml 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
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: maven-assembly-plugin 2.0-beta-1 src/main/assembly/dep.xml 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
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. Here is my root pom symplified: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.carosys jeeves pom 1.0 Jeeves Care Caro Sys http://www.carosys.com A system that is able to produce behaivoral trends as well as point out certain health conditions out of the regular activities of daily living of a person. jeeves-common jeeves-hub org.apache.maven.plugins maven-assembly-plugin 2.0-beta-2-SNAPSHOT bin.xml jeeves-1.0-beta-1 junit junit 3.8.1 test log4j log4j 1.2.8 jar commons-logging commons-logging 1.0.4 jar Here is the assembly descriptor. bin zip README* LICENSE* NOTICE* jeeves-hub/src/main/resources resources jeeves-hub/service-wrapper service-wrapper jeeves-hub . *.bat jeeves-hub . readme.* jeeves-common/src/main/resources resources common.properties AlarmConfig.xml NewAlarmConfig.xml lib Brett Porter wrote: Tomorrow. On 10/4/05, Erick Dovale <[EMAIL PROTECTED]> wrote: When is the beta-3 goint to be realeased?? cheers, erick. Brett Porter wrote: .. fixed in SVN for the beta-3 release. On 10/3/05, Brett Porter <[EMAIL PROTECTED]> wrote: It's a bug. The aggregator isn't forking the "package" goal first as it should. I will fix it shortly. - Brett On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote: Hi Brett, I checked out the assembly plugin and was able to build it and deploy it to my local repo. I also updated the version of the pluging in my root pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built plugin. When I run the assembly plugin on my root pom it is behaiving differently becasue before it was generating the zip for the root pom first and then iterating over the rest of the modules; now its building the zip last but it is not including the dependencies for the modules nor it is including the modules them selves. I am positive that I am missing something however, can figure it out my self. Any hints?? cheers, Erick. Brett Porter wrote: On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: What is this tag? It indicates the plugin should not run over subprojects, but has access to the reactor to perform an aggregating task. How do I get my hands on the latest commited code? See the instructions on the site for building frmo source for how to obtain it. You can build the plugin itself with "m2 install" on that plugin. Is it already deployed to the repo?? No. I've been searching all over the place looking for a class called: org.apache.maven.plugins.assembly.model.Assembly which is te one that gets instantiated out of the assembly descriptor but have been unable to find it so far. Can you point me to it? It is generated from assembly.mdo. If you do the build step above, it will be in target/generated-sources. I also took a look at AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and found no significant change since 2 days a go when I last looked at it. It was not a signifcant change, just the addition of @aggregator. Chee
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
Tomorrow. On 10/4/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > When is the beta-3 goint to be realeased?? > > cheers, > erick. > > Brett Porter wrote: > > >.. fixed in SVN for the beta-3 release. > > > >On 10/3/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > >>It's a bug. The aggregator isn't forking the "package" goal first as it > >>should. > >> > >>I will fix it shortly. > >> > >>- Brett > >> > >>On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > >> > >> > >>>Hi Brett, > >>>I checked out the assembly plugin and was able to build it and deploy it > >>>to my local repo. I also updated the version of the pluging in my root > >>>pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built > >>>plugin. > >>>When I run the assembly plugin on my root pom it is behaiving > >>>differently becasue before it was generating the zip for the root pom > >>>first and then iterating over the rest of the modules; now its building > >>>the zip last but it is not including the dependencies for the modules > >>>nor it is including the modules them selves. > >>>I am positive that I am missing something however, can figure it out my > >>>self. Any hints?? > >>>cheers, > >>> > >>>Erick. > >>>Brett Porter wrote: > >>> > >>> > >>> > On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > > > > > >What is this tag? > > > > > > > > > It indicates the plugin should not run over subprojects, but has > access to the reactor to perform an aggregating task. > > > > > > >How do I get my hands on the latest commited code? > > > > > > > > > See the instructions on the site for building frmo source for how to > obtain it. You can build the plugin itself with "m2 install" on that > plugin. > > > > > > >Is > >it already deployed to the repo?? > > > > > > > > > No. > > > > > > >I've been searching all over the place > >looking for a class called: > >org.apache.maven.plugins.assembly.model.Assembly which is te one that > >gets instantiated out of the assembly descriptor but have been unable to > >find it so far. Can you point me to it? > > > > > > > > > It is generated from assembly.mdo. If you do the build step above, it > will be in target/generated-sources. > > > > > > >I also took a look at > >AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and > >found no significant change since 2 days a go when I last looked at it. > > > > > > > > > It was not a signifcant change, just the addition of @aggregator. > > Cheers, > Brett > > - > 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] > > > > > > > > > > > - > 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]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
When is the beta-3 goint to be realeased?? cheers, erick. Brett Porter wrote: .. fixed in SVN for the beta-3 release. On 10/3/05, Brett Porter <[EMAIL PROTECTED]> wrote: It's a bug. The aggregator isn't forking the "package" goal first as it should. I will fix it shortly. - Brett On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote: Hi Brett, I checked out the assembly plugin and was able to build it and deploy it to my local repo. I also updated the version of the pluging in my root pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built plugin. When I run the assembly plugin on my root pom it is behaiving differently becasue before it was generating the zip for the root pom first and then iterating over the rest of the modules; now its building the zip last but it is not including the dependencies for the modules nor it is including the modules them selves. I am positive that I am missing something however, can figure it out my self. Any hints?? cheers, Erick. Brett Porter wrote: On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: What is this tag? It indicates the plugin should not run over subprojects, but has access to the reactor to perform an aggregating task. How do I get my hands on the latest commited code? See the instructions on the site for building frmo source for how to obtain it. You can build the plugin itself with "m2 install" on that plugin. Is it already deployed to the repo?? No. I've been searching all over the place looking for a class called: org.apache.maven.plugins.assembly.model.Assembly which is te one that gets instantiated out of the assembly descriptor but have been unable to find it so far. Can you point me to it? It is generated from assembly.mdo. If you do the build step above, it will be in target/generated-sources. I also took a look at AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and found no significant change since 2 days a go when I last looked at it. It was not a signifcant change, just the addition of @aggregator. Cheers, Brett - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
.. fixed in SVN for the beta-3 release. On 10/3/05, Brett Porter <[EMAIL PROTECTED]> wrote: > It's a bug. The aggregator isn't forking the "package" goal first as it > should. > > I will fix it shortly. > > - Brett > > On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > > Hi Brett, > > I checked out the assembly plugin and was able to build it and deploy it > > to my local repo. I also updated the version of the pluging in my root > > pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built > > plugin. > > When I run the assembly plugin on my root pom it is behaiving > > differently becasue before it was generating the zip for the root pom > > first and then iterating over the rest of the modules; now its building > > the zip last but it is not including the dependencies for the modules > > nor it is including the modules them selves. > > I am positive that I am missing something however, can figure it out my > > self. Any hints?? > > cheers, > > > > Erick. > > Brett Porter wrote: > > > > >On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > > > > > > > > >>What is this tag? > > >> > > >> > > > > > >It indicates the plugin should not run over subprojects, but has > > >access to the reactor to perform an aggregating task. > > > > > > > > > > > >>How do I get my hands on the latest commited code? > > >> > > >> > > > > > >See the instructions on the site for building frmo source for how to > > >obtain it. You can build the plugin itself with "m2 install" on that > > >plugin. > > > > > > > > > > > >>Is > > >>it already deployed to the repo?? > > >> > > >> > > > > > >No. > > > > > > > > > > > >>I've been searching all over the place > > >>looking for a class called: > > >>org.apache.maven.plugins.assembly.model.Assembly which is te one that > > >>gets instantiated out of the assembly descriptor but have been unable to > > >>find it so far. Can you point me to it? > > >> > > >> > > > > > >It is generated from assembly.mdo. If you do the build step above, it > > >will be in target/generated-sources. > > > > > > > > > > > >>I also took a look at > > >>AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and > > >>found no significant change since 2 days a go when I last looked at it. > > >> > > >> > > > > > >It was not a signifcant change, just the addition of @aggregator. > > > > > >Cheers, > > >Brett > > > > > >- > > >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]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
It's a bug. The aggregator isn't forking the "package" goal first as it should. I will fix it shortly. - Brett On 10/3/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > Hi Brett, > I checked out the assembly plugin and was able to build it and deploy it > to my local repo. I also updated the version of the pluging in my root > pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built > plugin. > When I run the assembly plugin on my root pom it is behaiving > differently becasue before it was generating the zip for the root pom > first and then iterating over the rest of the modules; now its building > the zip last but it is not including the dependencies for the modules > nor it is including the modules them selves. > I am positive that I am missing something however, can figure it out my > self. Any hints?? > cheers, > > Erick. > Brett Porter wrote: > > >On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > > > > > >>What is this tag? > >> > >> > > > >It indicates the plugin should not run over subprojects, but has > >access to the reactor to perform an aggregating task. > > > > > > > >>How do I get my hands on the latest commited code? > >> > >> > > > >See the instructions on the site for building frmo source for how to > >obtain it. You can build the plugin itself with "m2 install" on that > >plugin. > > > > > > > >>Is > >>it already deployed to the repo?? > >> > >> > > > >No. > > > > > > > >>I've been searching all over the place > >>looking for a class called: > >>org.apache.maven.plugins.assembly.model.Assembly which is te one that > >>gets instantiated out of the assembly descriptor but have been unable to > >>find it so far. Can you point me to it? > >> > >> > > > >It is generated from assembly.mdo. If you do the build step above, it > >will be in target/generated-sources. > > > > > > > >>I also took a look at > >>AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and > >>found no significant change since 2 days a go when I last looked at it. > >> > >> > > > >It was not a signifcant change, just the addition of @aggregator. > > > >Cheers, > >Brett > > > >- > >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]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
Hi Brett, I checked out the assembly plugin and was able to build it and deploy it to my local repo. I also updated the version of the pluging in my root pom to use 2.0-beta-2-SNAPSHOT which is the version of the newly built plugin. When I run the assembly plugin on my root pom it is behaiving differently becasue before it was generating the zip for the root pom first and then iterating over the rest of the modules; now its building the zip last but it is not including the dependencies for the modules nor it is including the modules them selves. I am positive that I am missing something however, can figure it out my self. Any hints?? cheers, Erick. Brett Porter wrote: On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: What is this tag? It indicates the plugin should not run over subprojects, but has access to the reactor to perform an aggregating task. How do I get my hands on the latest commited code? See the instructions on the site for building frmo source for how to obtain it. You can build the plugin itself with "m2 install" on that plugin. Is it already deployed to the repo?? No. I've been searching all over the place looking for a class called: org.apache.maven.plugins.assembly.model.Assembly which is te one that gets instantiated out of the assembly descriptor but have been unable to find it so far. Can you point me to it? It is generated from assembly.mdo. If you do the build step above, it will be in target/generated-sources. I also took a look at AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and found no significant change since 2 days a go when I last looked at it. It was not a signifcant change, just the addition of @aggregator. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
On 10/2/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > What is this tag? It indicates the plugin should not run over subprojects, but has access to the reactor to perform an aggregating task. > How do I get my hands on the latest commited code? See the instructions on the site for building frmo source for how to obtain it. You can build the plugin itself with "m2 install" on that plugin. > Is > it already deployed to the repo?? No. > I've been searching all over the place > looking for a class called: > org.apache.maven.plugins.assembly.model.Assembly which is te one that > gets instantiated out of the assembly descriptor but have been unable to > find it so far. Can you point me to it? It is generated from assembly.mdo. If you do the build step above, it will be in target/generated-sources. > I also took a look at > AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and > found no significant change since 2 days a go when I last looked at it. It was not a signifcant change, just the addition of @aggregator. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
Thanks for your reply Brett, I have inlined some questions I hope you can answer for me. Brett Porter wrote: On 9/30/05, Erick Dovale <[EMAIL PROTECTED]> wrote: 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. Thanks for the reminder. I just committed the missing tag on the assembly mojo so that it is an aggregator. What is this tag? How do I get my hands on the latest commited code? Is it already deployed to the repo?? I've been searching all over the place looking for a class called: org.apache.maven.plugins.assembly.model.Assembly which is te one that gets instantiated out of the assembly descriptor but have been unable to find it so far. Can you point me to it? I also took a look at AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and found no significant change since 2 days a go when I last looked at it. So it will run "package" over every subproject, but the assembly will only run on the top level one. 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. You should be able to use multiple dependency sets (with appropriate includes/excludes) to ensure the right deps go in the right folder. (maven-core is an example of such a descriptor). Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
On 9/30/05, Erick Dovale <[EMAIL PROTECTED]> wrote: > 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. Thanks for the reminder. I just committed the missing tag on the assembly mojo so that it is an aggregator. So it will run "package" over every subproject, but the assembly will only run on the top level one. > 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. You should be able to use multiple dependency sets (with appropriate includes/excludes) to ensure the right deps go in the right folder. (maven-core is an example of such a descriptor). Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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 <[EMAIL PROTECTED]> Reply-To: Maven Users List To: Maven Users List References: <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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]
Re: Assembly plugin -- couple of questions [m2a3]
Brett Thanks I will give it a try Sid --- Brett Porter <[EMAIL PROTECTED]> wrote: > 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 <[EMAIL PROTECTED]> > 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: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly plugin -- couple of questions [m2a3]
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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly plugin -- couple of questions [m2a3]
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
