+1
Emmanuel
On Mon, Oct 27, 2008 at 8:29 PM, Olivier Lamy [EMAIL PROTECTED] wrote:
Hi,
I'd like to release Maven Release plugin version 2.0-beta-8. (last
release is one year old).
We solved 27 issues :
Thanks for picking this up Brian, got sick over the weekend and didn't
have the time to poke at this further to where I was.
I fixed the build up after the release now, will try the binaries out
over the next day or two.
For the purpose of committing any fixes, will you be creating an RC
I was hoping this would be a quick process and not require another branch,
but if we need to then lets make a branch
On 10/28/08 5:55 AM, Brett Porter [EMAIL PROTECTED] wrote:
Thanks for picking this up Brian, got sick over the weekend and didn't
have the time to poke at this further to where
Brian E. Fox wrote:
Please try it out and see if we have any remaining regressions over
2.0.9.
It's not a regression but would nicely fit our efforts to stabilize
things: While investigating why 2.0.10-RC1 passed the IT MNG-3599 for
Brett but not for me, I discovered MNG-3805. It's just
Hi folks,
I have started to add some new versons of the our old archetypes.
Please feel free to review/change the archetypes at:
http://svn.apache.org/repos/asf/maven/archetype/trunk/archetype-samples/
Thanks in advance for any review.
Regards,
Raphaël
Brian E. Fox wrote:
Please try it out and see if we have any remaining regressions over
2.0.9. If it looks good, then I'll recut the official build as normal.
Hm, the RC prints ugly exception stack traces of
org.apache.maven.wagon.ResourceDoesNotExistException, even on INFO
level. Just try
In the new wagon beta-3 I imagine.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 4:38 PM
To: Maven Developers List
Subject: Re: [RC] Moving forward with 2.0.10
Brian E. Fox wrote:
Please try it out and see if we have any remaining
I seem to remember a fix brett put in for this when we were working on
[what became] 2.1.0-M1. I think it's in a console resolution listener,
possibly in maven-core or maven-artifact (-manager).
I'm pretty sure this is in maven, not wagon.
Benjamin Bentmann wrote:
Brian E. Fox wrote:
MNG-3775 http://jira.codehaus.org/browse/MNG-3775 is also more than
annoying
We added a testcase and I can try to create an IT if necessary.
Arnaud
On Tue, Oct 28, 2008 at 8:42 PM, Benjamin Bentmann
[EMAIL PROTECTED] wrote:
Brian E. Fox wrote:
Please try it out and see if we have any
Hi Arnaud,
The issue didn't make it clear that this is actually a regression from
2.0.8 - 2.0.9. It'd be helpful to have an IT for this that doesn't
rely on Seam to be able to get it fixed. I'd be a little reluctant to
make a dep change this far along in 2.0.10, since it's not a
Hi,
If a plugin is defined in the normal build section of a pom and has
defined a specific execution, is it possible to override this
execution by defining the same plugin in a profile?
The plugin I am working on, uses a forked build lifecycle, so when I
try to do this, I see the
11 matches
Mail list logo
