+1!
- Fabrice
[EMAIL PROTECTED]
On Tue, Nov 18, 2008 at 10:57 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> I'd like to release maven-changes-plugin version 2.1.
>
> We solved 27 issues :
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14064&styleName=Html&projectId=11212&Cr
Shane Isbell wrote:
Another problem is that some poms in the repo contain uninterpolated
${mavenVersion} values. If we specify the runtime version of say Maven 3.0,
when the artifact provider compiled with Maven 2.0, then we could get all
sorts of nasty class cast exceptions. Outside of cleaning
Another problem is that some poms in the repo contain uninterpolated
${mavenVersion} values. If we specify the runtime version of say Maven 3.0,
when the artifact provider compiled with Maven 2.0, then we could get all
sorts of nasty class cast exceptions. Outside of cleaning up the repo
metadata,
It would cause a circular dependency so we're doing this for the time
being.
On 18-Nov-08, at 5:12 PM, Brett Porter wrote:
There are libraries for getting the current version of Maven from
within Maven - it used to be called RuntimeInfo. Jason did the same
thing for settings reading a litt
There are libraries for getting the current version of Maven from
within Maven - it used to be called RuntimeInfo. Jason did the same
thing for settings reading a little while back. I'm not sure since
settings was folded back in how this might work from outside of the
core, but it needs to
Hi,
I'd like to release maven-changes-plugin version 2.1.
We solved 27 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14064&styleName=Html&projectId=11212&Create=Create
Staging repo: http://people.apache.org/~olamy/staging-repo/
Staging site: http://maven.apache.org/plugins/ma
