It seems that many circumstances are converging at the same time to show
that we need to make the next step and use active repository management
on the Apache repository. The increased pace of releases lately is
showing the flaws in the current system and it's not even possible to
deploy a release
Shane/Benjamin,
Go ahead and roll your changes into trunk.
The alpha-2 is tagged. No messages about the vote because of a problem
with the upgrade on people.apache.org which is preventing me from
deploying.
Thanks,
Jason
--
Jason va
On 30-Jan-09, at 3:04 PM, Vincent Siveton wrote:
Hi Jason,
2009/1/29 Jason van Zyl :
Howdy,
I've been looking at reporting in Maven 3.x and I've been following
the work
that Vincent Massol has been doing over at XWiki where he has made
some
attempts at melding Doxia, the XWiki rendering
On 31/01/2009, at 12:52 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
What I did was changed the IT base class to ignore -SNAPSHOT - it's
irrelevant to the range consideration and allows us to be clearer
(eg, use [2.0.10,) instead of (2.0.9,) for "fixed in 2.0.10").
However, we still
+1
Arnaud
2009/1/30 Jesse McConnell
> +1
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
>
>
>
> On Fri, Jan 30, 2009 at 3:47 PM, Jason van Zyl
> wrote:
> > +1
> >
> > On 30-Jan-09, at 12:18 PM, Oleg Gusakov wrote:
> >
> >> This is iterative improvements release of Mercury.
> >>
> >> The ma
+1
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Fri, Jan 30, 2009 at 3:47 PM, Jason van Zyl wrote:
> +1
>
> On 30-Jan-09, at 12:18 PM, Oleg Gusakov wrote:
>
>> This is iterative improvements release of Mercury.
>>
>> The major change:
>> - timestamped artifacts can now have dependencies - a
+1
On 30-Jan-09, at 12:18 PM, Oleg Gusakov wrote:
This is iterative improvements release of Mercury.
The major change:
- timestamped artifacts can now have dependencies - a bug was fixed
1 issue fixed: http://jira.codehaus.org/browse/MERCURY/fixforversion/14889
Staged release in repository a
This is iterative improvements release of Mercury.
The major change:
- timestamped artifacts can now have dependencies - a bug was fixed
1 issue fixed: http://jira.codehaus.org/browse/MERCURY/fixforversion/14889
Staged release in repository at
http://people.apache.org/~ogusakov/repos/staging/
No idea what version of maven that is, probably really old version that
is part of the now 3.0 branch. The new 2.1's are called 2.1.0M1 /
2.1.0M2-SNAPSHOT
-Original Message-
From: Petar Tahchiev [mailto:paranoia...@gmail.com]
Sent: Friday, January 30, 2009 9:14 AM
To: Maven Developers Lis
Did you test the last SNAPSHOT ?
Barrie can we launch the release process ?
Arnaud
On Fri, Jan 30, 2009 at 2:24 PM, djeanprost wrote:
>
> Hello,
>
> Judging from
>
> http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
> ,
> it seems that every
Hi guys,
maybe it's not a good descision to interfere in this thread,
but the Cactus project is failing on the Apache Hudson CI
server (http://hudson.zones.apache.org/), when being built with
Maven 2.1-SNAPSHOT.
The error message is:
ERROR: No classworlds*.jar found in
/home/hudson/apache-maven-2
There's a new 2.1 cut from the 2.0.x branch that provides a space to put
features. We did this back in Aug/Sept but there's been little forward
progress, so a release should get it started. When we planned it out,
there was a lot of interest in new features but I don't think much has
been done in t
Brett Porter wrote:
What I did was changed the IT base class to ignore -SNAPSHOT - it's
irrelevant to the range consideration and allows us to be clearer (eg,
use [2.0.10,) instead of (2.0.9,) for "fixed in 2.0.10").
However, we still have "2.1.0-M2-RC1 not in range [2.1.0-M2,)", i.e. the
RC
I was thinking :
2.0.x is the current Maven 2
2.1 deprecated and will became 3.0
But what is 2.2 ? or 2.1 ?
I'm puzzled
2009/1/30 Brian E. Fox :
> My original intent was to shift the focus to 2.1 and bring that quickly
> to GA. The development on it has stalled so it's irrelevant if it's
> fe
Hello,
Judging from
http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel,
it seems that everything got fixed for the 2.6 version of
maven-eclipse-plugin. Can someone tell us when it will be available to
everybody ?
regards,
dom
--
View this messa
My original intent was to shift the focus to 2.1 and bring that quickly
to GA. The development on it has stalled so it's irrelevant if it's
feature complete or not, it's stable and usable as it is. Future
features can go into 2.1.x or 2.2.
-Original Message-
From: paulus.benedic...@gmail.c
16 matches
Mail list logo
