Re: [mojo-dev] Creating MOJO for maintaining POMs?

versions:set changes the version of the module you run it in. the then jumps up the directory tree as long as you have aggregator projects, and then updates all references to the old version to be the new version, including updating child pom's that inherit the version Sent from my [rhymes

[mojo-dev] [jira] Commented: (MOJO-1199) Build number plugin to support GIT SCM

[ http://jira.codehaus.org/browse/MOJO-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178522#action_178522 ] Dan Tran commented on MOJO-1199: sorry I cant, dont know git enough to patch and test > Build number

[mojo-dev] [jira] Commented: (MOJO-1199) Build number plugin to support GIT SCM

[ http://jira.codehaus.org/browse/MOJO-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178518#action_178518 ] Lachlan Deck commented on MOJO-1199: Is this still outstanding? If the original poster isn't avail

Re: [mojo-dev] Creating MOJO for maintaining POMs?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, > and mvn versions:set -DnewVersion=_ is already implemented in trunk > for 1.0-beta-1 mhm, I do not know if that is exactly what I am looking for. Can I specify the artifactId and or groupId so such module in my reactor will be changed

Re: [mojo-dev] Creating MOJO for maintaining POMs?

and mvn versions:set -DnewVersion=_ is already implemented in trunk for 1.0-beta-1 2009/5/28 nicolas de loof > The versions-maven-plugin allready support some of the features you > suggest.Please contribute ! > > 2009/5/28 Joerg Hohwiller > > -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1

Re: [mojo-dev] Creating MOJO for maintaining POMs?

The versions-maven-plugin allready support some of the features you suggest.Please contribute ! 2009/5/28 Joerg Hohwiller > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi there, > > I am about to write a new MOJO that can change version or rename artifactId > in the entire POM-hierarchie

Re: [mojo-dev] pkg-maven-plugin

Joerg Hohwiller wrote: > Hi there, > >> Stephen Connolly wrote: >>> the issue I see for you is just when creating the tar with symbolic links >>> >>> you would not be untaring with your plugin, so all you have to do is >>> handle detecting the symbolic links and adding them into the tar file >>> c

[mojo-dev] Creating MOJO for maintaining POMs?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I am about to write a new MOJO that can change version or rename artifactId in the entire POM-hierarchie including parent-references, dependencies and dependency-management (if version matches). Maybe I will also build a goal ontop that open

Re: [mojo-dev] pkg-maven-plugin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, > Stephen Connolly wrote: >> the issue I see for you is just when creating the tar with symbolic links >> >> you would not be untaring with your plugin, so all you have to do is >> handle detecting the symbolic links and adding them into the

[mojo-dev] [jira] Commented: (MGWT-58) mergewebxml goal doesn't rename packages when using rename-to

[ http://jira.codehaus.org/browse/MGWT-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178423#action_178423 ] nicolas de loof commented on MGWT-58: - Not so simple as the mojo plugin uses GwtModule class to mani

[mojo-dev] [jira] Closed: (MGWT-65) GWT compiler command should not be invoked if all modules are up to date

[ http://jira.codehaus.org/browse/MGWT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MGWT-65. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 1.1 > GWT compiler command should n

[mojo-dev] [jira] Closed: (MGWT-70) Invalid version number "1.5" passed to external.gwtOnLoad(), expected "1.6"

[ http://jira.codehaus.org/browse/MGWT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MGWT-70. --- Resolution: Cannot Reproduce > Invalid version number "1.5" passed to external.gwtOnLoad(), expected "1.6" > -

[mojo-dev] [jira] Closed: (MGWT-82) Better support for m2eclipse integration

[ http://jira.codehaus.org/browse/MGWT-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nicolas de loof closed MGWT-82. --- Assignee: nicolas de loof Resolution: Fixed Fix Version/s: 1.1 support for m2eclipse + Google

[mojo-dev] [jira] Commented: (MFINDBUGS-57) SAX driver must be specified manually for filter file

[ http://jira.codehaus.org/browse/MFINDBUGS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178396#action_178396 ] Stephen Pack commented on MFINDBUGS-57: --- How is this issue fixed with version 2.0.1, when the

Re: [mojo-dev] [jira] Closed: (MASPECTJ-68) Update to AspectJ version 1.6.4 (which is now in the maven repo)

Thanks David! Simone David J. M. Karlsen (JIRA) wrote: [ http://jira.codehaus.org/browse/MASPECTJ-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David J. M. Karlsen closed MASPECTJ-68. --- Resolution: Fixed Fix Vers

[mojo-dev] [jira] Updated: (MNBMODULE-53) Build fails when no manifest file is present [PATCH]

[ http://jira.codehaus.org/browse/MNBMODULE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint updated MNBMODULE-53: -- Fix Version/s: 3.1 thanks for the patch, I'll look into it in a few days (after vacation) > Build

[mojo-dev] [jira] Closed: (MFINDBUGS-57) SAX driver must be specified manually for filter file

[ http://jira.codehaus.org/browse/MFINDBUGS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garvin LeClaire closed MFINDBUGS-57. Resolution: Fixed Fix Version/s: (was: 1.2.1) 2.0.1 > SAX driver

Re: [mojo-dev] [VOTE] Release unix-maven-plugin 1.0-alpha-4

Trygve Laugstøl wrote: I'd like to release unix-maven-plugin 1.0-alpha-4, codename "fire". This is the fourth release. +1 -- Best regards Erik Drolshammer - To unsubscribe from this list, please visit: http://xircles.code