maven-release-plugin: apply patches for MRELEASE-294 and MRELEASE-389?

Hello, I would like to start a discussion to get the patches of issues MRELEASE-294 and MRELEASE-389 applied. Can the responsible persons for maven-release-manager and maven-release-plugin review the patches and comment on any issues they see with the provided patches? http://jira.codehaus.o

How can a first mojo set properties for the second mojo?

Hello, I have a custom mojo that calculates the values for the properties releaseVersion and developmentVersion of the maven-release-plugin. I would like to invoke the release as follows: mvn telenet:getNextVersion release:prepare How should I define these properties so the release plugin p

RE: How to get path to the local repository?

John, > Subject: Re: How to get path to the local repository? > > If you're injecting this information into a plugin parameter, > you can use the expression '${localRepository}' to get the > ArtifactRepository instance, then call getBasePath() from that, IIRC. For a custom plugin, I also need

RE: Invoking maven in a plugin?

> -Original Message- > From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu] > Sent: dinsdag 23 december 2008 17:29 > To: Maven Developers List > Subject: Re: Invoking maven in a plugin? > > De Smet Ringo wrote: > > > What is the best way for a pl

Invoking maven in a plugin?

Hello, We have a custom plugin that, for some functionality, spawns Maven again but with other arguments. The current implementation depends on the MavenExecutor from the maven-release-plugin:2.0-beta-4. I updated the dependency to 2.0-beta-8, but in there, the API to MavenExecutor has changed

RE: Alternative to mojo-executor but with more control?

Brett, > -Original Message- > From: Brett Porter > Sent: maandag 22 december 2008 1:02 > To: Maven Developers List > Subject: Re: Alternative to mojo-executor but with more control? > - write your own, use the maven-invoker to run the instances > of release:prepare / perform / clean My

Alternative to mojo-executor but with more control?

Hello, Before I head of starting a custom plugin, I would like to know if anyone is aware of a plugin like the mojo-executor plugin, but with a bit more features. http://code.google.com/p/mojo-executor/ My intent is to automate making releases usin

RE: BUG? Profile properties not used to resolve dependencies transitively. (was RE: Version property in root POM & multi-level dependency resolution)

vel dependency resolution) > > > On 15/12/2008, at 7:44 PM, De Smet Ringo wrote: > > > Brett, > > > > OK, you don't have the time, but I can spare some cycles. Should I > > start with filing a JIRA? > > Yes, if there isn't one already. Thanks

RE: BUG? Profile properties not used to resolve dependencies transitively. (was RE: Version property in root POM & multi-level dependency resolution)

Brett, > -Original Message- > From: Brett Porter > Sent: donderdag 11 december 2008 17:23 > To: Maven Developers List > Subject: Re: BUG? Profile properties not used to resolve > dependencies transitively. (was RE: Version property in root > POM & multi-level dependency resolution) > >

RE: BUG? Profile properties not used to resolve dependencies transitively. (was RE: Version property in root POM & multi-level dependency resolution)

Brett, > -Original Message- > From: Brett Porter > > Ok, I see what you mean. You illustrated the property in the > project which should not work. But from settings.xml and the > command line it should. Unfortunately, it doesn't, or again I'm misinterpreting you. :-) The three attac

RE: BUG? Profile properties not used to resolve dependencies transitively. (was RE: Version property in root POM & multi-level dependency resolution)

Brett, > -Original Message- > From: Brett Porter > > It looks like the intended behaviour to me, the same as if > you pulled the properties out of the profile. Properties are > not transitively applied. Can you give me some more background on the why of this decision. If you re-read m

BUG? Profile properties not used to resolve dependencies transitively. (was RE: Version property in root POM & multi-level dependency resolution)

before the interpolation is executed. Any comments? Ringo > -Original Message----- > From: De Smet Ringo > Sent: woensdag 10 december 2008 12:49 > To: dev@maven.apache.org > Subject: Version property in root POM & multi-level > dependency resolution > > Hello, &

RE: Version property in root POM & multi-level dependency resolution

Stephen, > -Original Message- > From: Stephen Connolly [mailto:[EMAIL PROTECTED] > Sent: woensdag 10 december 2008 14:01 > To: Maven Developers List > Subject: Re: Version property in root POM & multi-level > dependency resolution > > I'm not sure where you see the run-time error? In

RE: Version property in root POM & multi-level dependency resolution

Stephen, > -Original Message- > From: Stephen Connolly [mailto:[EMAIL PROTECTED] > Sent: woensdag 10 december 2008 13:12 > To: Maven Developers List > Subject: Re: Version property in root POM & multi-level > dependency resolution > > Have a look at versions:update-properties... (you'd

Version property in root POM & multi-level dependency resolution

Hello, [Repost from users list, hoping to get more in-depth answer here] I am busy creating an easy Maven2 setup for a 200+ module system, both targeted to an easier release and an easier development setup. It is a multi-level system, with common modules, service modules and presentation (web-u

RE: Custom plugin goalprefix not correct in generated site

Benjamin, > That's an unusual artifact id, the convention is to use > something like "telenet-maven-plugin", compare [0]. I didn't choose this id unfortunately. :-) > > In the POM, I have specified the goalprefix to be > "telenet". However, > > in the generated site, all my goals are listed

Custom plugin goalprefix not correct in generated site

Hello, I have written a custom Maven2 plugin, in our CVS repo called maven2.plugin. In the POM, I have specified the goalprefix to be "telenet". However, in the generated site, all my goals are listed as: 2.: Is there still a known bug that this goalprefix is not correctly picked up for the sit

RE: Java version for 2.1 branch

> Is there any reason that the 2.1 branch cannot require java > 1.5 to compile and execute? I am not a developer on Maven, so my vote would not count anyway. I am an independent IT consultant and want to offer some background information why this would be a "bad" decision. During my work for th

RE: How to refer to different Maven classpaths in Ant-based mojo's?

> -Original Message- > Eventually, I found out what was wrong with my code. It took > me a while... :-) > > It seems one cannot use the refid. I changed my Ant-based mojo to: > > > > > > This works fine now. I was a bit too fast claiming success. Final question: does it *really

RE: How to refer to different Maven classpaths in Ant-based mojo's?

Hello, > Can someone post a snippet of Ant file showing me how I can > refer to these classpaths? In our Maven1 jelly setup, I found > references like "maven.compile.classpath", but using this as > > Eventually, I found out what was wrong with my code. It took me a while... :-) It seems one

How to refer to different Maven classpaths in Ant-based mojo's?

Hello, This is a bit a re-post of an earlier message I posted to the user list. I got no replies, so I hope the developer community can help me better. I have been searching mailing list archives, Googled, etc. for days, but I can't get my problem resolved. I have two Ant-based mojo's that cause