Re: [m2] How to exclude modules from site:site
Thanks so much! On 9/7/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > > module-2/pom.xml: > > [...] > > maven-site-plugin > >false > > > [...] > > Mick Knutson schrieb: > > How would I configure that for just one module? > > > > ROOT:pom.xml > >|-->module-1: pom.xml (Generate site) > >|-->module-2: pom.xml (DO NOT Generate site) > >|-->module-3: pom.xml (Generate site) > > > > > > > > > > On 9/7/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> have you tried false in the > >> site-plugin's configuration [1]? > >> > >> -Tim > >> > >> [1] http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html > >> > >> Mick Knutson schrieb: > >>> I have a multi-module project that when I run site:site, there are > some > >>> modules I want to exclude. > >>> > >>> This is due to a strange bug in ant-run where I get PMD errors when > this > >>> modules runs site:site. I do not have time to spend on that error as I > >> have > >>> already posted that here several times with zero response. > >>> > >>> So now so I can hit my Wednesday deadline, I just need to be able to > >> turn > >>> site:site off for this one module. > >>> > >>> Please someone help... > >>> > >> > >> - > >> 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] > > -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: [m2] How to exclude modules from site:site
module-2/pom.xml: [...] maven-site-plugin false [...] Mick Knutson schrieb: How would I configure that for just one module? ROOT:pom.xml |-->module-1: pom.xml (Generate site) |-->module-2: pom.xml (DO NOT Generate site) |-->module-3: pom.xml (Generate site) On 9/7/07, Tim Kettler <[EMAIL PROTECTED]> wrote: Hi, have you tried false in the site-plugin's configuration [1]? -Tim [1] http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html Mick Knutson schrieb: I have a multi-module project that when I run site:site, there are some modules I want to exclude. This is due to a strange bug in ant-run where I get PMD errors when this modules runs site:site. I do not have time to spend on that error as I have already posted that here several times with zero response. So now so I can hit my Wednesday deadline, I just need to be able to turn site:site off for this one module. Please someone help... - 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: [m2] How to exclude modules from site:site
How would I configure that for just one module? ROOT:pom.xml |-->module-1: pom.xml (Generate site) |-->module-2: pom.xml (DO NOT Generate site) |-->module-3: pom.xml (Generate site) On 9/7/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > > Hi, > > have you tried false in the > site-plugin's configuration [1]? > > -Tim > > [1] http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html > > Mick Knutson schrieb: > > I have a multi-module project that when I run site:site, there are some > > modules I want to exclude. > > > > This is due to a strange bug in ant-run where I get PMD errors when this > > modules runs site:site. I do not have time to spend on that error as I > have > > already posted that here several times with zero response. > > > > So now so I can hit my Wednesday deadline, I just need to be able to > turn > > site:site off for this one module. > > > > Please someone help... > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: [m2] How to exclude modules from site:site
Hi, have you tried false in the site-plugin's configuration [1]? -Tim [1] http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html Mick Knutson schrieb: I have a multi-module project that when I run site:site, there are some modules I want to exclude. This is due to a strange bug in ant-run where I get PMD errors when this modules runs site:site. I do not have time to spend on that error as I have already posted that here several times with zero response. So now so I can hit my Wednesday deadline, I just need to be able to turn site:site off for this one module. Please someone help... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to exclude modules from site:site
I have a multi-module project that when I run site:site, there are some modules I want to exclude. This is due to a strange bug in ant-run where I get PMD errors when this modules runs site:site. I do not have time to spend on that error as I have already posted that here several times with zero response. So now so I can hit my Wednesday deadline, I just need to be able to turn site:site off for this one module. Please someone help... -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
Re: how to exclude modules
1- I know, but sadly it is not enough to justify the move to my manager! :( 2- Good idea, I can define a profile per module + 1 for all, and enable only the specific profiles I need. My only problem is that the release plugin will still update all dependencies to SNAPSHOT in my webapp pom, I'm not sure I like that idea, maybe I can patch the plugin to work differently! Thanks for your help! On 23/04/07, Wayne Fay <[EMAIL PROTECTED]> wrote: 1. Move to Subversion. File refactoring does not lose history. 2. There is no module excludes. Instead we have a notion of profiles in M2. So you would set your default in the top parent pom.xml to have say either zero or very few modules defined, and then in a separate profile (call it "all"), you would have all modules listed. Thus when you normally built your project from the top parent dir, only the default modules would be built. But then when you specified -Pall, all your modules would be built. Perhaps this gives you something to think about. I'm not sure if it solves all your problems. Wayne On 4/23/07, Daniel Beland <[EMAIL PROTECTED]> wrote: > Hi, > > > I have some questions about aggregation modules in maven2. > > Let me explain how we were working with maven 1.1 and why I don`t fully > understand how we should work with maven 2. > > We have some maven 1 multi-projects saved in CVS as a single project. > A developer checks out the complete project in 1 operation. > > Most of the time, it consists of N jar artifacts to be included in a webapp. > Since we do not modify all the N artifacts but just a subset of them between > each release, we would work intensively with the > maven.multiproject.excludesproperty to set only the projects we want > to build between each release > (projects that are SNAPSHOT and are needed in the webapp project.xml, and it > means we reset the value to all projects every time we release a beta). > Since the rest is already released (be it production version or previous > unchanged beta), there is no need to compile and deploy them again the next > time. > > Now in maven 2, there is no such property. > After a release, everything is put back to SNAPSHOT, even all the > dependencies in the webapp pom (as I understand it would do). > How can I release a project and have only each artifact's current version > set to SNAPSHOT, but have the webapp dependencies left to the just released > version? > (Keep in mind I didn't release an aggregation module with inter-dependencies > yet and maybe it is not what it does). > > How can I have something similar to maven.multiproject.excludes? > Should I comment the modules I don't want to compile in the pom? > > > Finally, is it in your opinion better to simply have N projects in CVS other > than a big aggregation project to achieve what I want? > (But would still use the same parent pom, I would just release each > sub-module independently and have better control on what to release each > time). > My only concern with that is the major refactoring of the CVS modules and > losing all the file history. > > Thanks for your input, > Daniel > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to exclude modules
1. Move to Subversion. File refactoring does not lose history. 2. There is no module excludes. Instead we have a notion of profiles in M2. So you would set your default in the top parent pom.xml to have say either zero or very few modules defined, and then in a separate profile (call it "all"), you would have all modules listed. Thus when you normally built your project from the top parent dir, only the default modules would be built. But then when you specified -Pall, all your modules would be built. Perhaps this gives you something to think about. I'm not sure if it solves all your problems. Wayne On 4/23/07, Daniel Beland <[EMAIL PROTECTED]> wrote: Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to exclude modules
Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel
RE: How to exclude modules from a build lifecycle?
Thanks Wayne and Wendy. I will experiment with both options - multiple pom.xmls and profiles. I'll post what I find. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: June 08, 2006 2:21 PM To: Maven Users List Subject: Re: How to exclude modules from a build lifecycle? On 6/8/06, Chris Wall <[EMAIL PROTECTED]> wrote: > In a mutli-level project, is there a way to exclude modules from a > build? Our use case is that we want to minimize build lifecycle time > for developer check-ins by excluding less frequently changed modules. > For our full builds (nightly), we obviously want to include all modules. > > An example would be: Given that module A is the parent of module B > which has sub-modules 1 and 2, and the parent of module C which has > sub-modules 3 and 4, how might we exclude sub-modules 2 and sub-modules > 4 when executing the build of module A. Profiles? We (Struts) have some modules that can't be in the 'default build' because they have dependencies that aren't freely available or have incompatible licenses. So 'mvn install' will not build those modules, but 'mvn install -Pextras' will. HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to exclude modules from a build lifecycle?
On 6/8/06, Chris Wall <[EMAIL PROTECTED]> wrote: In a mutli-level project, is there a way to exclude modules from a build? Our use case is that we want to minimize build lifecycle time for developer check-ins by excluding less frequently changed modules. For our full builds (nightly), we obviously want to include all modules. An example would be: Given that module A is the parent of module B which has sub-modules 1 and 2, and the parent of module C which has sub-modules 3 and 4, how might we exclude sub-modules 2 and sub-modules 4 when executing the build of module A. Profiles? We (Struts) have some modules that can't be in the 'default build' because they have dependencies that aren't freely available or have incompatible licenses. So 'mvn install' will not build those modules, but 'mvn install -Pextras' will. HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to exclude modules from a build lifecycle?
Others have asked this question and I've not seen any responses, so I'll assume there is no obvious/built-in way to exclude certain modules from being built. Here's a few alternatives I can think of off the top of my head... 1. Use no modules, only dependencies. Build everything independently. This breaks the entire concept of parents, modules, full builds etc. 2. Create multiple pom.xml files for your parent. Only include the specific modules you want to build in each one ie pom_mod1_only.xml and then specify it when you run your build ie mvn -f pom_mod1_only.xml. You will need to make sure the other modules have been built and installed in your local repo prior to attempting this partial build, of course. Probably 2 is the best option for your situation. Wayne On 6/8/06, Chris Wall <[EMAIL PROTECTED]> wrote: In a mutli-level project, is there a way to exclude modules from a build? Our use case is that we want to minimize build lifecycle time for developer check-ins by excluding less frequently changed modules. For our full builds (nightly), we obviously want to include all modules. An example would be: Given that module A is the parent of module B which has sub-modules 1 and 2, and the parent of module C which has sub-modules 3 and 4, how might we exclude sub-modules 2 and sub-modules 4 when executing the build of module A. Thanks. -Chris ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to exclude modules from a build lifecycle?
In a mutli-level project, is there a way to exclude modules from a build? Our use case is that we want to minimize build lifecycle time for developer check-ins by excluding less frequently changed modules. For our full builds (nightly), we obviously want to include all modules. An example would be: Given that module A is the parent of module B which has sub-modules 1 and 2, and the parent of module C which has sub-modules 3 and 4, how might we exclude sub-modules 2 and sub-modules 4 when executing the build of module A. Thanks. -Chris ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
