Reactor never installs the master pom
We are using a the reactor plugin extensively but have noticed that it never installs the master pom to the local repository. We manage all of our dependency version information in the master pom, so it is important that it be updated in the repository. Example: /pom.xml -- master pom containing version information for all dependencies /projectA/pom.xml -- project pom indicating which of the dependencies it includes /projectB/pom.xml -- etc... If projectB depends on projectA and I say: mvn reactor:make -Dmake.folders=projectB -Dmake.goals=clean,install then the reactor will build and install both projectA and projectB, but the master pom is not updated in the repository. I'd really hate to have to run two build commands every time I build something. Is there a way I can get this to install the master pom? I've even created a customization of the reactor that changes the command that the plugin issues from: [INFO] [reactor:make] [INFO] Executing: /bin/sh -c cd [path] && [path]/maven/2.0.9/bin/mvn -B -N -r -D maven.reactor.includes=projectA/pom.xml,projectB/pom.xml clean install To: [INFO] [reactor:make] [INFO] Executing: /bin/sh -c cd [path] && [path]/maven/2.0.9/bin/mvn -B -N -r -D maven.reactor.includes=pom.xml,projectA/pom.xml,projectB/pom.xml clean install But it seems the reactor really only wants to build subfolders of the master. Is there any way to get the reactor to install the master? I've already gotten to the point of customizing the plugin, so code-based solutions are acceptable. Thanks! -- View this message in context: http://www.nabble.com/Reactor-never-installs-the-master-pom-tp25410249p25410249.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deprecating and banning artifacts with repository metadata
Sounds useful to me. We were going to build a similar plugin - but the plan for it to be a sonar plugin rather than a maven plugin. Jim On Fri, Sep 11, 2009 at 10:23 AM, Ben Lidgey wrote: > > It sounds like it could be useful, but perhaps with a warning as there are > maintenance projects applying bug fixes to existing projects that may not > want to update older components to avoid too many changes. > > Ben > > > On 10/09/2009 22:03, "Wendy Smoak" wrote: > > A group I work with had a requirement to be able to deprecate and ban > old versions of their artifacts. The dev team is very large and > simply sending out an email telling everyone not to use version 1.0 of > some artifact won't work. The team needed a way to warn and/or > enforce that the old version is no longer supported and should not (or > must not) be used. > > I think they started out writing a rule for the Enforcer plugin, but > at some point it turned into a separate plugin. (There was a concern > about teams simply re-configuring the Enforcer plugin to get around > the rules.) > > In the repository, they have a versions-metadata.xml file sitting next > to the maven-metadata.xml file. The plugin examines all the > dependencies in the build and looks for the versions-metadata.xml > file to see if it needs to warn or fail. > > They're considering contributing the plugin and are wondering whether > it sounds useful to the general Maven community before they start > wading through the corporate legal stuff that would be necessary to > make that happen. > > Does it sound like something you might use? Let me know if you want > more details on it, or perhaps one of the devs that's involved will > chime in. > > Thanks, > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > > > E-Mail : blid...@movenetworks.com > __ > Move Networks UK > Enterprise House > Navigation Park > Abercynon > CF45 4SN > t: +44 (0)8445 460100 > f: +44 (0)8445 460200 / (0)1443 742 568 > w: www.movenetworks.com > >
Re: Question about site deployment
That aspect could certainly be better. At least here we'd like to
publish snapshots every time to the same location, and each release to
a separate location plus the latest to a fixed location. You can do
something like
scp://myproject.mycompany.com/var/www/maven-site/versions/${project.version}.
After that, we take care of the rest by adjusting the symbolic links
(with a script). So you can do it, but some manual assembly required
to get that going.
Kalle
On Fri, Sep 11, 2009 at 8:52 AM, Roland Asmann wrote:
> Hi all,
>
> I am currently refactoring a lot of our projects and this means updating all
> POMs. I was looking at the ditributionmanagement-part of my POMs, and I was
> wondering why there is no different setting for the SNAPSHOT- and
> RELEASE-sites, like with the repositories.
>
> We are running nightly builds, that both deploy the SNAPSHOT artifacts and the
> SNAPSHOT sites. However, it would be nice to have these deployed to a
> different location for SNAPSHOTS, so we can delete them when we release the
> projects (in other words: when they are obsolete).
>
> Is there an easy way to accomplish something like this with the 2.0 branch of
> Maven?
>
> Thanks,
>
> --
> Roland Asmann
>
> CFC Informationssysteme Entwicklungsgesellschaft m.b.H
> Bäckerstrasse 1/2/7
> A-1010 Wien
> FN 266155f, Handelsgericht Wien
>
> Tel.: +43/1/513 88 77 - 27
> Fax.: +43/1/513 88 62
> Email: roland.asm...@cfc.at
> Web: www.cfc.at
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to update parent during release:prepare
But the release cycles of the company pom and your project shouldn't be connected. I'd argue that you should only be using the same released version of the company pom until it doesn't work for that project anymore, and only then change to a new released version. Furthermore, I think you should never use a snapshot version of a parent unless it's part of the same multi-module build (i.e. shares the same release cycle). Kalle On Fri, Sep 11, 2009 at 7:03 AM, Lewis, Eric wrote: > Yes, that would be the ideal solution. > In the meantime, I'm avoiding manual and error-prone work by putting the > process into a shell script. > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com] >> Gesendet: Freitag, 11. September 2009 15:57 >> An: Maven Users List >> Betreff: Re: How to update parent during release:prepare >> >> I certainly have the exact same problem. And using the >> versions plugin only >> helps somewhat in partially automating what I currently do >> manually. Last >> time I made the mistake of not manually changing the parent >> version, the >> release plugin, I believe, offered to update to a released >> version, but >> didn't actually change it, resulting in what was essentially a broken >> release (since it had a SNAPSHOT parent). Similarly I face >> problems with >> the release plugin not handling SNAPSHOT versions of >> "dependencies" declared >> outside the dependencies section (typically using the maven-dependency >> plugin instead). I would like to see the release plugin >> updated to handle >> these rather than work around them with the versions plugin. >> >> -Stephen >> >> On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric >> wrote: >> >> > Thanks, that works well! >> > >> > However, I'm still wondering whether I'm the only one >> releasing that way. >> > It seems to me that the release plugin can only be used >> together with the >> > versions plugin. >> > I think that most developers have some sort of company-wide >> parent POM >> > which they refer to, and when releasing, they probably all >> have the same >> > problem as I do. >> > >> > Best regards, >> > Eric >> > >> > >> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Depending on all submodules of a parent
Hi folks, Getting started with Maven 2.0.9, I want to use the Sesame RDF library. The POM is here: http://repo.aduna-software.org/maven2/releases/org/openrdf/sesame/sesame/2.2.4/sesame-2.2.4.pom It has 3 modules, and those modules contain many submodules. Can I include ALL the submodules of sesame-2.2.4 in my project, without listing each one separately? That is, I want to write something like this and get all the submodules: org.openrdf.sesame sesame-model 2.2.4 pom Thanks, -Stuart - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping deployment of module
Regarding the link: I don't want to deploy one of the artifacts in my multi-module build. Can I skip deployment? Yes, you can skip deployment of individual modules by configuring the deploy plugin as follows: maven-deploy-plugin X.Y true This example doesn't show how to skip one of the artifacts, rather it seems to be an all or nothing example. Can someone confirm if you can skip certain artifacts and if so how? -Dave On Fri, Sep 11, 2009 at 8:17 AM, Anders Hammar wrote: > I'm a little bit confused. Is the aggregator pom also the parent of the > modules? If it is, it should also be deployed. > > If not, I guess it should be able to make it not deploy by doing exactly as > described in: > http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip > Declare this in the aggregator pom. Have you tried it and it doesn't work? > > /Anders > > On Fri, Sep 11, 2009 at 15:48, Roland Asmann wrote: > >> Hi all, >> >> Is it possible to skip deployment of a specific module when triggering 'mvn >> deploy'? I've read in [1] that it's possible, but I think this will only >> work >> on sub-modules. >> >> My problem is that I have an aggregator-pom that is only used as an >> aggregator >> and should not be deployed. Since itś just a small POM, it wouldn't be a >> real >> big problem if it finds it's way into our company's repository, but seeing >> how we have a lot of those small aggregator-POMs, it might clutter the >> repo. >> >> So, can anybody tell me if [1] works for the parent as well? If nobody >> knows, >> I might just give it a try and see what it does... >> >> Thanks. >> >> >> [1] http://maven.apache.org/plugins/maven-deploy-plugin/faq.html >> >> -- >> Roland Asmann >> >> CFC Informationssysteme Entwicklungsgesellschaft m.b.H >> Bäckerstrasse 1/2/7 >> A-1010 Wien >> FN 266155f, Handelsgericht Wien >> >> Tel.: +43/1/513 88 77 - 27 >> Fax.: +43/1/513 88 62 >> Email: roland.asm...@cfc.at >> Web: www.cfc.at >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Question about site deployment
Hi all, I am currently refactoring a lot of our projects and this means updating all POMs. I was looking at the ditributionmanagement-part of my POMs, and I was wondering why there is no different setting for the SNAPSHOT- and RELEASE-sites, like with the repositories. We are running nightly builds, that both deploy the SNAPSHOT artifacts and the SNAPSHOT sites. However, it would be nice to have these deployed to a different location for SNAPSHOTS, so we can delete them when we release the projects (in other words: when they are obsolete). Is there an easy way to accomplish something like this with the 2.0 branch of Maven? Thanks, -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: roland.asm...@cfc.at Web: www.cfc.at - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Exclude subversion files in war
If you'll forgive another bump on this thread, I found that including the trailing '/' in the pattern will exclude the .svn directories: **/.svn/ I am using maven-2.1.0 and maven-war-plugin-2.1-alpha-2. -- View this message in context: http://www.nabble.com/Exclude-subversion-files-in-war-tp5288845p25403227.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping deployment of module
No, it's not the parent. I haven't tried the skipping yet, I'm currently turning our projects upside-down, so I don't have the time yet... I just wanted to check if somebody might now the answer... On Friday 11 September 2009 16:17, Anders Hammar wrote: > I'm a little bit confused. Is the aggregator pom also the parent of the > modules? If it is, it should also be deployed. > > If not, I guess it should be able to make it not deploy by doing exactly as > described in: > http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip > Declare this in the aggregator pom. Have you tried it and it doesn't work? > > /Anders > > On Fri, Sep 11, 2009 at 15:48, Roland Asmann wrote: > > Hi all, > > > > Is it possible to skip deployment of a specific module when triggering > > 'mvn deploy'? I've read in [1] that it's possible, but I think this will > > only work > > on sub-modules. > > > > My problem is that I have an aggregator-pom that is only used as an > > aggregator > > and should not be deployed. Since itś just a small POM, it wouldn't be a > > real > > big problem if it finds it's way into our company's repository, but > > seeing how we have a lot of those small aggregator-POMs, it might clutter > > the repo. > > > > So, can anybody tell me if [1] works for the parent as well? If nobody > > knows, > > I might just give it a try and see what it does... > > > > Thanks. > > > > > > [1] http://maven.apache.org/plugins/maven-deploy-plugin/faq.html > > > > -- > > Roland Asmann > > > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > > Bäckerstrasse 1/2/7 > > A-1010 Wien > > FN 266155f, Handelsgericht Wien > > > > Tel.: +43/1/513 88 77 - 27 > > Fax.: +43/1/513 88 62 > > Email: roland.asm...@cfc.at > > Web: www.cfc.at > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: roland.asm...@cfc.at Web: www.cfc.at - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to update parent during release:prepare
versions:commit does not actually commit to your scm... it just removes the versionsBackup files (poor man's SCM) there is nothing stopping your from running versions:update-parent from a root aggregator pom and updating everything... then 1 big scm commit of the pom changes 2009/9/11 Stephen Duncan Jr > I think that's what he's referring to; it is in my case. First I release > the company-wide parent POM, then I begin releasing the rest of the > projects, each of which need to have their parent declaration updated from > the SNAPSHOT version to the just-released version. Currently I do this > manually to all projects I'm releasing (with the advantage of only adding > one extra commit, whereas the versions-approach would be one extra commit > PER project). > > -Stephen > > On Fri, Sep 11, 2009 at 9:57 AM, David Hoffer wrote: > > > Woudn't it better to first release your company-wide parent poms > > first? Then release projects that refer to released poms? Otherwise > > it seems you would now have to chase down all the old references to > > the prior snapshot parent and manually update. > > > > -Dave > > > > On Fri, Sep 11, 2009 at 7:51 AM, Lewis, Eric wrote: > > > Thanks, that works well! > > > > > > However, I'm still wondering whether I'm the only one releasing that > way. > > > It seems to me that the release plugin can only be used together with > the > > versions plugin. > > > I think that most developers have some sort of company-wide parent POM > > which they refer to, and when releasing, they probably all have the same > > problem as I do. > > > > > > Best regards, > > > Eric > > > > > >> -Ursprüngliche Nachricht- > > >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > > >> Gesendet: Freitag, 11. September 2009 15:41 > > >> An: Maven Users List > > >> Betreff: Re: How to update parent during release:prepare > > >> > > >> before you run a release just run > > >> > > >> mvn versions:update-parent > > >> mvn versions:commit > > >> mvn release:prepare release:perform > > >> > > >> 2009/9/11 Lewis, Eric > > >> > > >> > Hi Dave > > >> > > > >> > Thanks for the answer, but it's not quite what I meant :-) > > >> > > > >> > I don't mean the parent version within the modules, but the > > >> parent version > > >> > within the project (i.e. the module's parent). > > >> > > > >> > Let's say I have a company wide POM in the repo > > >> > > > >> > company-pom:1.2.0-SNAPSHOT > > >> > > > >> > which has been released to > > >> > > > >> > company-pom:1.2.0 > > >> > > > >> > > > >> > All my projects depend on this (showing hierarchies by > > >> indenting and the > > >> > specified parent in the POM with an arrow): > > >> > > > >> > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT > > >> > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > > >> > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > > >> > > > >> > Now I need to release my-project, so the result should be > > >> > > > >> > my-project:3.0.0 -> company-pom:1.2.0 > > >> > my-module-1:2.1.0 -> my-project:3.0.0 > > >> > my-module-2:5.3.7 -> my-project:3.0.0 > > >> > > > >> > As you say, changing the modules from my-project:3.0.0-SNAPSHOT to > > >> > my-project:3.0.0 is done with -DautoVersionSubmodules=true, > > >> but how do I > > >> > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 > > >> within my-project? > > >> > > > >> > Best regards, > > >> > Eric > > >> > > > >> > > -Ursprüngliche Nachricht- > > >> > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > > >> > > Gesendet: Donnerstag, 10. September 2009 19:03 > > >> > > An: Maven Users List > > >> > > Betreff: Re: How to update parent during release:prepare > > >> > > > > >> > > The autoVersionSubmodules property can be used to tell the release > > >> > > plugin to use the Parent's version for all of the child > > >> modules. Are > > >> > > your modules all the same version as your parent? If so, then > > >> > > it should > > >> > > work as-is. I normally use the command: > > >> > > > > >> > > mvn -DautoVersionSubmodules=true release:prepare > > >> > > > > >> > > to start the process on a project with about 8 modules. It'll > > >> > > ask me for > > >> > > the release version of the parent and then the next > > >> > > development version. > > >> > > Beyond that, it's all automatic. > > >> > > > > >> > > Dave > > >> > > > > >> > > > > >> > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > > >> > > > Hi > > >> > > > > > >> > > > I'm trying to use release:prepare for a project with > > >> > > several modules. > > >> > > > The project has a parent which is a SNAPSHOT. Now my > > >> > > question is: How can I tell release:prepare to update the > > >> > > project's parent version to the parent's released version? > > >> > > > > > >> > > > Best regards, > > >> > > > Eric > > >> > > > > > >> > > > > >> - > > >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.o
Re: Deprecating and banning artifacts with repository metadata
It sounds like it could be useful, but perhaps with a warning as there are maintenance projects applying bug fixes to existing projects that may not want to update older components to avoid too many changes. Ben On 10/09/2009 22:03, "Wendy Smoak" wrote: A group I work with had a requirement to be able to deprecate and ban old versions of their artifacts. The dev team is very large and simply sending out an email telling everyone not to use version 1.0 of some artifact won't work. The team needed a way to warn and/or enforce that the old version is no longer supported and should not (or must not) be used. I think they started out writing a rule for the Enforcer plugin, but at some point it turned into a separate plugin. (There was a concern about teams simply re-configuring the Enforcer plugin to get around the rules.) In the repository, they have a versions-metadata.xml file sitting next to the maven-metadata.xml file. The plugin examines all the dependencies in the build and looks for the versions-metadata.xml file to see if it needs to warn or fail. They're considering contributing the plugin and are wondering whether it sounds useful to the general Maven community before they start wading through the corporate legal stuff that would be necessary to make that happen. Does it sound like something you might use? Let me know if you want more details on it, or perhaps one of the devs that's involved will chime in. Thanks, -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org E-Mail : blid...@movenetworks.com __ Move Networks UK Enterprise House Navigation Park Abercynon CF45 4SN t: +44 (0)8445 460100 f: +44 (0)8445 460200 / (0)1443 742 568 w: www.movenetworks.com
Re: Skipping deployment of module
I'm a little bit confused. Is the aggregator pom also the parent of the modules? If it is, it should also be deployed. If not, I guess it should be able to make it not deploy by doing exactly as described in: http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip Declare this in the aggregator pom. Have you tried it and it doesn't work? /Anders On Fri, Sep 11, 2009 at 15:48, Roland Asmann wrote: > Hi all, > > Is it possible to skip deployment of a specific module when triggering 'mvn > deploy'? I've read in [1] that it's possible, but I think this will only > work > on sub-modules. > > My problem is that I have an aggregator-pom that is only used as an > aggregator > and should not be deployed. Since itś just a small POM, it wouldn't be a > real > big problem if it finds it's way into our company's repository, but seeing > how we have a lot of those small aggregator-POMs, it might clutter the > repo. > > So, can anybody tell me if [1] works for the parent as well? If nobody > knows, > I might just give it a try and see what it does... > > Thanks. > > > [1] http://maven.apache.org/plugins/maven-deploy-plugin/faq.html > > -- > Roland Asmann > > CFC Informationssysteme Entwicklungsgesellschaft m.b.H > Bäckerstrasse 1/2/7 > A-1010 Wien > FN 266155f, Handelsgericht Wien > > Tel.: +43/1/513 88 77 - 27 > Fax.: +43/1/513 88 62 > Email: roland.asm...@cfc.at > Web: www.cfc.at > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
AW: How to update parent during release:prepare
Yes, that would be the ideal solution. In the meantime, I'm avoiding manual and error-prone work by putting the process into a shell script. Best regards, Eric > -Ursprüngliche Nachricht- > Von: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com] > Gesendet: Freitag, 11. September 2009 15:57 > An: Maven Users List > Betreff: Re: How to update parent during release:prepare > > I certainly have the exact same problem. And using the > versions plugin only > helps somewhat in partially automating what I currently do > manually. Last > time I made the mistake of not manually changing the parent > version, the > release plugin, I believe, offered to update to a released > version, but > didn't actually change it, resulting in what was essentially a broken > release (since it had a SNAPSHOT parent). Similarly I face > problems with > the release plugin not handling SNAPSHOT versions of > "dependencies" declared > outside the dependencies section (typically using the maven-dependency > plugin instead). I would like to see the release plugin > updated to handle > these rather than work around them with the versions plugin. > > -Stephen > > On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric > wrote: > > > Thanks, that works well! > > > > However, I'm still wondering whether I'm the only one > releasing that way. > > It seems to me that the release plugin can only be used > together with the > > versions plugin. > > I think that most developers have some sort of company-wide > parent POM > > which they refer to, and when releasing, they probably all > have the same > > problem as I do. > > > > Best regards, > > Eric > > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to update parent during release:prepare
I think that's what he's referring to; it is in my case. First I release the company-wide parent POM, then I begin releasing the rest of the projects, each of which need to have their parent declaration updated from the SNAPSHOT version to the just-released version. Currently I do this manually to all projects I'm releasing (with the advantage of only adding one extra commit, whereas the versions-approach would be one extra commit PER project). -Stephen On Fri, Sep 11, 2009 at 9:57 AM, David Hoffer wrote: > Woudn't it better to first release your company-wide parent poms > first? Then release projects that refer to released poms? Otherwise > it seems you would now have to chase down all the old references to > the prior snapshot parent and manually update. > > -Dave > > On Fri, Sep 11, 2009 at 7:51 AM, Lewis, Eric wrote: > > Thanks, that works well! > > > > However, I'm still wondering whether I'm the only one releasing that way. > > It seems to me that the release plugin can only be used together with the > versions plugin. > > I think that most developers have some sort of company-wide parent POM > which they refer to, and when releasing, they probably all have the same > problem as I do. > > > > Best regards, > > Eric > > > >> -Ursprüngliche Nachricht- > >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > >> Gesendet: Freitag, 11. September 2009 15:41 > >> An: Maven Users List > >> Betreff: Re: How to update parent during release:prepare > >> > >> before you run a release just run > >> > >> mvn versions:update-parent > >> mvn versions:commit > >> mvn release:prepare release:perform > >> > >> 2009/9/11 Lewis, Eric > >> > >> > Hi Dave > >> > > >> > Thanks for the answer, but it's not quite what I meant :-) > >> > > >> > I don't mean the parent version within the modules, but the > >> parent version > >> > within the project (i.e. the module's parent). > >> > > >> > Let's say I have a company wide POM in the repo > >> > > >> > company-pom:1.2.0-SNAPSHOT > >> > > >> > which has been released to > >> > > >> > company-pom:1.2.0 > >> > > >> > > >> > All my projects depend on this (showing hierarchies by > >> indenting and the > >> > specified parent in the POM with an arrow): > >> > > >> > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT > >> > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > >> > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > >> > > >> > Now I need to release my-project, so the result should be > >> > > >> > my-project:3.0.0 -> company-pom:1.2.0 > >> > my-module-1:2.1.0 -> my-project:3.0.0 > >> > my-module-2:5.3.7 -> my-project:3.0.0 > >> > > >> > As you say, changing the modules from my-project:3.0.0-SNAPSHOT to > >> > my-project:3.0.0 is done with -DautoVersionSubmodules=true, > >> but how do I > >> > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 > >> within my-project? > >> > > >> > Best regards, > >> > Eric > >> > > >> > > -Ursprüngliche Nachricht- > >> > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > >> > > Gesendet: Donnerstag, 10. September 2009 19:03 > >> > > An: Maven Users List > >> > > Betreff: Re: How to update parent during release:prepare > >> > > > >> > > The autoVersionSubmodules property can be used to tell the release > >> > > plugin to use the Parent's version for all of the child > >> modules. Are > >> > > your modules all the same version as your parent? If so, then > >> > > it should > >> > > work as-is. I normally use the command: > >> > > > >> > > mvn -DautoVersionSubmodules=true release:prepare > >> > > > >> > > to start the process on a project with about 8 modules. It'll > >> > > ask me for > >> > > the release version of the parent and then the next > >> > > development version. > >> > > Beyond that, it's all automatic. > >> > > > >> > > Dave > >> > > > >> > > > >> > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > >> > > > Hi > >> > > > > >> > > > I'm trying to use release:prepare for a project with > >> > > several modules. > >> > > > The project has a parent which is a SNAPSHOT. Now my > >> > > question is: How can I tell release:prepare to update the > >> > > project's parent version to the parent's released version? > >> > > > > >> > > > Best regards, > >> > > > Eric > >> > > > > >> > > > >> - > >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > >> > > > > >> > > > >> > > > >> - > >> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > >> > > > >> > > >> - > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.o
AW: How to update parent during release:prepare
Yes, this is exactly what I'm doing. Still, I want to change the parent to the released version *and* release the project in one go. And it seems like this is only possible by combining the versions and the release plugins. Best regards, Eric > -Ursprüngliche Nachricht- > Von: David Hoffer [mailto:dhoff...@gmail.com] > Gesendet: Freitag, 11. September 2009 15:57 > An: Maven Users List > Betreff: Re: How to update parent during release:prepare > > Woudn't it better to first release your company-wide parent poms > first? Then release projects that refer to released poms? Otherwise > it seems you would now have to chase down all the old references to > the prior snapshot parent and manually update. > > -Dave > > On Fri, Sep 11, 2009 at 7:51 AM, Lewis, Eric > wrote: > > Thanks, that works well! > > > > However, I'm still wondering whether I'm the only one > releasing that way. > > It seems to me that the release plugin can only be used > together with the versions plugin. > > I think that most developers have some sort of company-wide > parent POM which they refer to, and when releasing, they > probably all have the same problem as I do. > > > > Best regards, > > Eric > > > >> -Ursprüngliche Nachricht- > >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > >> Gesendet: Freitag, 11. September 2009 15:41 > >> An: Maven Users List > >> Betreff: Re: How to update parent during release:prepare > >> > >> before you run a release just run > >> > >> mvn versions:update-parent > >> mvn versions:commit > >> mvn release:prepare release:perform > >> > >> 2009/9/11 Lewis, Eric > >> > >> > Hi Dave > >> > > >> > Thanks for the answer, but it's not quite what I meant :-) > >> > > >> > I don't mean the parent version within the modules, but the > >> parent version > >> > within the project (i.e. the module's parent). > >> > > >> > Let's say I have a company wide POM in the repo > >> > > >> > company-pom:1.2.0-SNAPSHOT > >> > > >> > which has been released to > >> > > >> > company-pom:1.2.0 > >> > > >> > > >> > All my projects depend on this (showing hierarchies by > >> indenting and the > >> > specified parent in the POM with an arrow): > >> > > >> > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT > >> > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > >> > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > >> > > >> > Now I need to release my-project, so the result should be > >> > > >> > my-project:3.0.0 -> company-pom:1.2.0 > >> > my-module-1:2.1.0 -> my-project:3.0.0 > >> > my-module-2:5.3.7 -> my-project:3.0.0 > >> > > >> > As you say, changing the modules from > my-project:3.0.0-SNAPSHOT to > >> > my-project:3.0.0 is done with -DautoVersionSubmodules=true, > >> but how do I > >> > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 > >> within my-project? > >> > > >> > Best regards, > >> > Eric > >> > > >> > > -Ursprüngliche Nachricht- > >> > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > >> > > Gesendet: Donnerstag, 10. September 2009 19:03 > >> > > An: Maven Users List > >> > > Betreff: Re: How to update parent during release:prepare > >> > > > >> > > The autoVersionSubmodules property can be used to tell > the release > >> > > plugin to use the Parent's version for all of the child > >> modules. Are > >> > > your modules all the same version as your parent? If so, then > >> > > it should > >> > > work as-is. I normally use the command: > >> > > > >> > > mvn -DautoVersionSubmodules=true release:prepare > >> > > > >> > > to start the process on a project with about 8 modules. It'll > >> > > ask me for > >> > > the release version of the parent and then the next > >> > > development version. > >> > > Beyond that, it's all automatic. > >> > > > >> > > Dave > >> > > > >> > > > >> > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > >> > > > Hi > >> > > > > >> > > > I'm trying to use release:prepare for a project with > >> > > several modules. > >> > > > The project has a parent which is a SNAPSHOT. Now my > >> > > question is: How can I tell release:prepare to update the > >> > > project's parent version to the parent's released version? > >> > > > > >> > > > Best regards, > >> > > > Eric > >> > > > > >> > > > >> > - > >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > >> > > > > >> > > > >> > > > >> > - > >> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > >> > > > >> > > >> > - > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > > >
[maven-changes-plugin] jira report does not support fix for multiple versions (?)
Hi I'm using version 2.1 of the plugin ; my artifactid is 3.1.1-SNAPSHOT, I am also maintaining another branch of the project, under version 4.0.M4-SNAPSHOT. I have a resolved jira entry with a Fix For: field labelled for versions 3.1.1 and 4.0.M4. Whenever I run mvn changes:announcement-generate, it does not generate a report for this specific entry. If I modify the entry and use a single Fix For: 3.1.1, the report is generated. Can anyone confirm the jira report does not include multiple fix for versions reports ? I'll fill a JIRA if I'm not alone with this. Thanks laurent -- http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com - Mobile world, technology and more - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to update parent during release:prepare
I certainly have the exact same problem. And using the versions plugin only helps somewhat in partially automating what I currently do manually. Last time I made the mistake of not manually changing the parent version, the release plugin, I believe, offered to update to a released version, but didn't actually change it, resulting in what was essentially a broken release (since it had a SNAPSHOT parent). Similarly I face problems with the release plugin not handling SNAPSHOT versions of "dependencies" declared outside the dependencies section (typically using the maven-dependency plugin instead). I would like to see the release plugin updated to handle these rather than work around them with the versions plugin. -Stephen On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric wrote: > Thanks, that works well! > > However, I'm still wondering whether I'm the only one releasing that way. > It seems to me that the release plugin can only be used together with the > versions plugin. > I think that most developers have some sort of company-wide parent POM > which they refer to, and when releasing, they probably all have the same > problem as I do. > > Best regards, > Eric > >
Re: How to update parent during release:prepare
Woudn't it better to first release your company-wide parent poms first? Then release projects that refer to released poms? Otherwise it seems you would now have to chase down all the old references to the prior snapshot parent and manually update. -Dave On Fri, Sep 11, 2009 at 7:51 AM, Lewis, Eric wrote: > Thanks, that works well! > > However, I'm still wondering whether I'm the only one releasing that way. > It seems to me that the release plugin can only be used together with the > versions plugin. > I think that most developers have some sort of company-wide parent POM which > they refer to, and when releasing, they probably all have the same problem as > I do. > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> Gesendet: Freitag, 11. September 2009 15:41 >> An: Maven Users List >> Betreff: Re: How to update parent during release:prepare >> >> before you run a release just run >> >> mvn versions:update-parent >> mvn versions:commit >> mvn release:prepare release:perform >> >> 2009/9/11 Lewis, Eric >> >> > Hi Dave >> > >> > Thanks for the answer, but it's not quite what I meant :-) >> > >> > I don't mean the parent version within the modules, but the >> parent version >> > within the project (i.e. the module's parent). >> > >> > Let's say I have a company wide POM in the repo >> > >> > company-pom:1.2.0-SNAPSHOT >> > >> > which has been released to >> > >> > company-pom:1.2.0 >> > >> > >> > All my projects depend on this (showing hierarchies by >> indenting and the >> > specified parent in the POM with an arrow): >> > >> > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT >> > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT >> > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT >> > >> > Now I need to release my-project, so the result should be >> > >> > my-project:3.0.0 -> company-pom:1.2.0 >> > my-module-1:2.1.0 -> my-project:3.0.0 >> > my-module-2:5.3.7 -> my-project:3.0.0 >> > >> > As you say, changing the modules from my-project:3.0.0-SNAPSHOT to >> > my-project:3.0.0 is done with -DautoVersionSubmodules=true, >> but how do I >> > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 >> within my-project? >> > >> > Best regards, >> > Eric >> > >> > > -Ursprüngliche Nachricht- >> > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] >> > > Gesendet: Donnerstag, 10. September 2009 19:03 >> > > An: Maven Users List >> > > Betreff: Re: How to update parent during release:prepare >> > > >> > > The autoVersionSubmodules property can be used to tell the release >> > > plugin to use the Parent's version for all of the child >> modules. Are >> > > your modules all the same version as your parent? If so, then >> > > it should >> > > work as-is. I normally use the command: >> > > >> > > mvn -DautoVersionSubmodules=true release:prepare >> > > >> > > to start the process on a project with about 8 modules. It'll >> > > ask me for >> > > the release version of the parent and then the next >> > > development version. >> > > Beyond that, it's all automatic. >> > > >> > > Dave >> > > >> > > >> > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: >> > > > Hi >> > > > >> > > > I'm trying to use release:prepare for a project with >> > > several modules. >> > > > The project has a parent which is a SNAPSHOT. Now my >> > > question is: How can I tell release:prepare to update the >> > > project's parent version to the parent's released version? >> > > > >> > > > Best regards, >> > > > Eric >> > > > >> > > >> - >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > > For additional commands, e-mail: users-h...@maven.apache.org >> > > > >> > > > >> > > >> > > >> - >> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > For additional commands, e-mail: users-h...@maven.apache.org >> > > >> > > >> > >> - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to update parent during release:prepare
Thanks, that works well! However, I'm still wondering whether I'm the only one releasing that way. It seems to me that the release plugin can only be used together with the versions plugin. I think that most developers have some sort of company-wide parent POM which they refer to, and when releasing, they probably all have the same problem as I do. Best regards, Eric > -Ursprüngliche Nachricht- > Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > Gesendet: Freitag, 11. September 2009 15:41 > An: Maven Users List > Betreff: Re: How to update parent during release:prepare > > before you run a release just run > > mvn versions:update-parent > mvn versions:commit > mvn release:prepare release:perform > > 2009/9/11 Lewis, Eric > > > Hi Dave > > > > Thanks for the answer, but it's not quite what I meant :-) > > > > I don't mean the parent version within the modules, but the > parent version > > within the project (i.e. the module's parent). > > > > Let's say I have a company wide POM in the repo > > > > company-pom:1.2.0-SNAPSHOT > > > > which has been released to > > > > company-pom:1.2.0 > > > > > > All my projects depend on this (showing hierarchies by > indenting and the > > specified parent in the POM with an arrow): > > > > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT > > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > > > > Now I need to release my-project, so the result should be > > > > my-project:3.0.0 -> company-pom:1.2.0 > > my-module-1:2.1.0 -> my-project:3.0.0 > > my-module-2:5.3.7 -> my-project:3.0.0 > > > > As you say, changing the modules from my-project:3.0.0-SNAPSHOT to > > my-project:3.0.0 is done with -DautoVersionSubmodules=true, > but how do I > > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 > within my-project? > > > > Best regards, > > Eric > > > > > -Ursprüngliche Nachricht- > > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > > > Gesendet: Donnerstag, 10. September 2009 19:03 > > > An: Maven Users List > > > Betreff: Re: How to update parent during release:prepare > > > > > > The autoVersionSubmodules property can be used to tell the release > > > plugin to use the Parent's version for all of the child > modules. Are > > > your modules all the same version as your parent? If so, then > > > it should > > > work as-is. I normally use the command: > > > > > > mvn -DautoVersionSubmodules=true release:prepare > > > > > > to start the process on a project with about 8 modules. It'll > > > ask me for > > > the release version of the parent and then the next > > > development version. > > > Beyond that, it's all automatic. > > > > > > Dave > > > > > > > > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > > > > Hi > > > > > > > > I'm trying to use release:prepare for a project with > > > several modules. > > > > The project has a parent which is a SNAPSHOT. Now my > > > question is: How can I tell release:prepare to update the > > > project's parent version to the parent's released version? > > > > > > > > Best regards, > > > > Eric > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Skipping deployment of module
Hi all, Is it possible to skip deployment of a specific module when triggering 'mvn deploy'? I've read in [1] that it's possible, but I think this will only work on sub-modules. My problem is that I have an aggregator-pom that is only used as an aggregator and should not be deployed. Since itś just a small POM, it wouldn't be a real big problem if it finds it's way into our company's repository, but seeing how we have a lot of those small aggregator-POMs, it might clutter the repo. So, can anybody tell me if [1] works for the parent as well? If nobody knows, I might just give it a try and see what it does... Thanks. [1] http://maven.apache.org/plugins/maven-deploy-plugin/faq.html -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: roland.asm...@cfc.at Web: www.cfc.at - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to update parent during release:prepare
before you run a release just run mvn versions:update-parent mvn versions:commit mvn release:prepare release:perform 2009/9/11 Lewis, Eric > Hi Dave > > Thanks for the answer, but it's not quite what I meant :-) > > I don't mean the parent version within the modules, but the parent version > within the project (i.e. the module's parent). > > Let's say I have a company wide POM in the repo > > company-pom:1.2.0-SNAPSHOT > > which has been released to > > company-pom:1.2.0 > > > All my projects depend on this (showing hierarchies by indenting and the > specified parent in the POM with an arrow): > > my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT > my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT > > Now I need to release my-project, so the result should be > > my-project:3.0.0 -> company-pom:1.2.0 > my-module-1:2.1.0 -> my-project:3.0.0 > my-module-2:5.3.7 -> my-project:3.0.0 > > As you say, changing the modules from my-project:3.0.0-SNAPSHOT to > my-project:3.0.0 is done with -DautoVersionSubmodules=true, but how do I > update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 within my-project? > > Best regards, > Eric > > > -Ursprüngliche Nachricht- > > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > > Gesendet: Donnerstag, 10. September 2009 19:03 > > An: Maven Users List > > Betreff: Re: How to update parent during release:prepare > > > > The autoVersionSubmodules property can be used to tell the release > > plugin to use the Parent's version for all of the child modules. Are > > your modules all the same version as your parent? If so, then > > it should > > work as-is. I normally use the command: > > > > mvn -DautoVersionSubmodules=true release:prepare > > > > to start the process on a project with about 8 modules. It'll > > ask me for > > the release version of the parent and then the next > > development version. > > Beyond that, it's all automatic. > > > > Dave > > > > > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > > > Hi > > > > > > I'm trying to use release:prepare for a project with > > several modules. > > > The project has a parent which is a SNAPSHOT. Now my > > question is: How can I tell release:prepare to update the > > project's parent version to the parent's released version? > > > > > > Best regards, > > > Eric > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: WTP and M2 Plugin.
Hi, With similar issues I fought in july. Unfortunately Eclipse does not have individual classpath for just testing, therefore if the .classpath file has the test directories on sources, also WTP will put in .settings/org.eclipse.wst.common.component too. and when the dependencies are resolved from Workspace, the jar is created accordingly, that's why you see tests in newly created jar. Since WTP often writes in org.eclipse.wst.common.component, I cannot figure out if m2eclipse can take over the control of this file. Therefore manually I remove those tests web-resource lines. Until you don't update m2eclipse project configuration or add new source directories, you don't have problem with tests. At least our guys still using m2eclipse and I never heard complains about this problems. I know that this is just a workaround, but seems to work effectively. Regards Tibor On Fri, Sep 11, 2009 at 3:00 PM, Alexander Vaysberg wrote: > Hi, > > i have a problem with WTP and M2 Plugin. The problem is in file:- > .settings/org.eclipse.wst.common.component. If you I use the project > (web-project) without "Resolve dependencies from Workspace ..." it's work > fine, but if i use the project with "Resolve dependencies from Workspace > ..." then i have a problem with jars for dependent projects which was > created from maven or eclipse. > This is a context of the file:< > > > > > > > > > The jar created from this file. In this case added the plugin test data in > jars. The correct was the this data:- > > > ignore. This only for test. But it was in jars added. Why? > > Alexander Vaysberg > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
WTP and M2 Plugin.
Hi, i have a problem with WTP and M2 Plugin. The problem is in file:- .settings/org.eclipse.wst.common.component. If you I use the project (web-project) without "Resolve dependencies from Workspace ..." it's work fine, but if i use the project with "Resolve dependencies from Workspace ..." then i have a problem with jars for dependent projects which was created from maven or eclipse. This is a context of the file:< The jar created from this file. In this case added the plugin test data in jars. The correct was the this data:- ignore. This only for test. But it was in jars added. Why? Alexander Vaysberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to update parent during release:prepare
Hi Dave Thanks for the answer, but it's not quite what I meant :-) I don't mean the parent version within the modules, but the parent version within the project (i.e. the module's parent). Let's say I have a company wide POM in the repo company-pom:1.2.0-SNAPSHOT which has been released to company-pom:1.2.0 All my projects depend on this (showing hierarchies by indenting and the specified parent in the POM with an arrow): my-project:3.0.0-SNAPSHOT -> company-pom:1.2.0-SNAPSHOT my-module-1:2.1.0-SNAPSHOT -> my-project:3.0.0-SNAPSHOT my-module-2:5.3.7-SNAPSHOT -> my-project:3.0.0-SNAPSHOT Now I need to release my-project, so the result should be my-project:3.0.0 -> company-pom:1.2.0 my-module-1:2.1.0 -> my-project:3.0.0 my-module-2:5.3.7 -> my-project:3.0.0 As you say, changing the modules from my-project:3.0.0-SNAPSHOT to my-project:3.0.0 is done with -DautoVersionSubmodules=true, but how do I update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 within my-project? Best regards, Eric > -Ursprüngliche Nachricht- > Von: David C. Hicks [mailto:dhi...@i-hicks.org] > Gesendet: Donnerstag, 10. September 2009 19:03 > An: Maven Users List > Betreff: Re: How to update parent during release:prepare > > The autoVersionSubmodules property can be used to tell the release > plugin to use the Parent's version for all of the child modules. Are > your modules all the same version as your parent? If so, then > it should > work as-is. I normally use the command: > > mvn -DautoVersionSubmodules=true release:prepare > > to start the process on a project with about 8 modules. It'll > ask me for > the release version of the parent and then the next > development version. > Beyond that, it's all automatic. > > Dave > > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > > Hi > > > > I'm trying to use release:prepare for a project with > several modules. > > The project has a parent which is a SNAPSHOT. Now my > question is: How can I tell release:prepare to update the > project's parent version to the parent's released version? > > > > Best regards, > > Eric > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: question re: CI builds and maven.
The Sonatype book 2009/9/10 James Russo : > Thanks Wes, > > I understand. I guess for me, I'm really looking to automate the release > portion of things. So, when I fix something or commit a change (to a version > already released and deployed), I can just wait at the end of this big > machine (build server) for a new release to be created with a new build > number on it ready to go. > > I would think you would want to post snapshots from the CI server to the > repo so that all other developers would be constantly getting the snapshots > of dependent artifacts without someone having to do a deploy. The CI server > is doing the deploy each time there is a SCM change. > > Any good place to read more about this stuff? Like how to organize svn in a > way which permits you to fix bugs and create features at the same time..What > version do you leave on the trunk, are you working on new versions/features > in branches, etc. I'd be interested in hearing about what convention and > assumptions maven uses in this regard with the release module. > > thanks, > > -jr > > Wes Wannemacher wrote: >> >> I use CI to make sure that unit tests all still pass in other >> artifacts. For instance, I make changes in artifactA and somewhere >> down a dependency chain, artifactB is affected... I may not realize >> that my change breaks artifactB, I may not even know that artifactB >> exists, but if the CI build shows test failures, someone knows where >> to start looking (the changes the initiated the build?). >> >> The CI does push to our nexus repo, but to me the fact that it can do >> that is irrelevant. >> >> -Wes >> >> On Thu, Sep 10, 2009 at 4:20 PM, James Russo wrote: >> >>> >>> Hello, >>> >>> This is likely more of a software engineering related maven question. >>> With >>> the concept of snapshots and versioned artifacts where would a continuous >>> build system come into place? How do others use it? I guess you really >>> have >>> two options, the CI system can produce snapshots or it can produce >>> version'd >>> releases. I would imagine that you would want to have the CI server >>> publish >>> these artifacts back to your local internal repository.. >>> >>> So, how do others use continuous integration servers like hudson in their >>> maven environment? >>> >>> thanks! >>> -jr >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> >> >> >> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly plug in behaving differently between local and CI server
I added the assemply plug in to a project, and it creates a proper jar that includes config files, etc when run locally on my machine using mvn package, but the same command on our build server outputs a jar that lacks some critical config files that need to be at the default package level in the classpath. Here's the config from the pom: org.apache.maven.plugins maven-assembly-plugin 2.2-beta-4 attached package jar-with-dependencies com.medialets.service.PostEC what gives? Bill - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automated release process
Hi! It sounds as you need a CI server. It would solve your issue. Take a look at CruiseControl: http://cruisecontrol.sourceforge.net/ Hudson: https://hudson.dev.java.net/ /Thomas On Thu, Sep 10, 2009 at 13:10, Matt Milliss wrote: > I work at a company that has around 10 applications, each application is a > maven project, each of which may or may not get modified in a given 2 week > iteration. At the end of every iteration I want an automated process for > checking which applications have been modified since the last release and > then release only those applications. Something along the lines of the > following; > > 1. retrieve previous release version from our archiva repo > 2. in subversion compare that versions tag against trunk to see any > differences > 3. if any differences then perform a release of that project > 4. repeat for each application > > I've been trying to find a maven way of doing this but haven't had any luck, > has anybody done something similar with success. > > Cheers > Matt Milliss > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Thomas Sundberg M. Sc. in Computer Science Agical AB Västerlånggatan 79, 2 tr 111 29 Stockholm, SWEDEN Mobile: +46 70 767 33 15 E-mail: thomas.sundb...@agical.com http://www.agical.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
