On Fri, Sep 3, 2010 at 10:58 PM, Jason van Zyl wrote:
> I write up a blog entry with the schedule and goals.
>
> i'll mention the construction if ITs and point to some examples.
These will be greatly appreciated.
-
To unsubscrib
On Fri, Sep 3, 2010 at 5:16 PM, Stephen Connolly
wrote:
> On 3 September 2010 01:38, Barrie Treloar wrote:
>> Automatic Plugin Version Resolution
>>
>> Now that plugin versions are expected to be locked down in the pom
>> has the documentation been updated to describe how to manage the
>> versio
+1
Vincent
2010/8/30 Benjamin Bentmann :
> Hi,
>
> what's a better start for a week than a new fresh release :-) ? So here we
> go!
>
> Apart from another few regression fixes, this release includes Guice and
> Aether [0] and shall help to get some more community testing on these new
> components
What I meant was to release maven 3.0, the dev needs to iron up most
of to backward compatibility blocking bugs. ( no work around )
The bug I mentioned sound like a feature that is accidentally take out
of maven core which supports flat repository structure.
-Dan
On Fri, Sep 3, 2010 at 6:28 AM,
I write up a blog entry with the schedule and goals.
i'll mention the construction if ITs and point to some examples.
On Sep 3, 2010, at 9:10 AM, Brian Fox wrote:
> On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote:
>> I think trying to release 3.0 sooner, and then sticking to 6 week release
On Friday 03 September 2010 2:34:00 am han hongfang wrote:
> Forward to dev list to see if somebody has some advice for me on this
> question.
It's not the release plugin, it's the remote-resources plugin generating them.
You would need to figure out where the remote-resources thing is configu
It's not changing at this point.
On Sep 3, 2010, at 9:14 AM, Paul Benedict wrote:
> What are the plans for the .m2 user directory? I understand keeping it
> for migration purposes, but maybe you want to bring back .mvn (so it
> doesn't need to change per version).
>
> Paul
>
> On Fri, Sep 3, 20
What are the plans for the .m2 user directory? I understand keeping it
for migration purposes, but maybe you want to bring back .mvn (so it
doesn't need to change per version).
Paul
On Fri, Sep 3, 2010 at 8:10 AM, Brian Fox wrote:
> On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote:
>> I thin
On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote:
> I think trying to release 3.0 sooner, and then sticking to 6 week release
> cycles would be a better use of time. We're going to fix anything that arises
> but I don't believe there will be widespread testing until 3.0 is released,
> and I
Woo hoo!
On Sep 2, 2010, at 7:19 PM, Brian Fox wrote:
> This is a little delayed, but still deserved. A few weeks ago,
> Kristian joined us on the Maven PMC. He's been driving a lot of
> interesting work in Maven 3 to support parallel builds. If you haven't
> tried that out yet, please do and sen
On Sep 2, 2010, at 11:46 PM, Dan Tran wrote:
> I think i agree with Jason on shooting maven 3.0 out to public as soon
> as you can, however the dev team might want fix up blocking bugs which
> prevent user like me from using maven 3
>
> one of the blocking bug for me is http://jira.codehaus.org/
Congrats Kristian!
On Fri, Sep 3, 2010 at 1:19 AM, Brian Fox wrote:
> This is a little delayed, but still deserved. A few weeks ago,
> Kristian joined us on the Maven PMC. He's been driving a lot of
> interesting work in Maven 3 to support parallel builds. If you haven't
> tried that out yet, pl
+1
On 3 September 2010 01:44, Jason van Zyl wrote:
> I think trying to release 3.0 sooner, and then sticking to 6 week release
> cycles would be a better use of time. We're going to fix anything that
> arises but I don't believe there will be widespread testing until 3.0 is
> released, and I don
On 3 September 2010 01:38, Barrie Treloar wrote:
> I didn't want to hijack the other thread with my questions after
> reading https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
> Caching of Artifact Resolution Errors
>
> Marker files are great! Is there any documentation on what
+1
On Fri, Sep 3, 2010 at 2:44 AM, Jason van Zyl wrote:
> I think trying to release 3.0 sooner, and then sticking to 6 week release
> cycles would be a better use of time. We're going to fix anything that
> arises but I don't believe there will be widespread testing until 3.0 is
> released, and
Forward to dev list to see if somebody has some advice for me on this
question.
Best regards,
Han Hong Fang
-- Forwarded message --
From: han hongfang
Date: Fri, Aug 27, 2010 at 5:27 PM
Subject: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull
16 matches
Mail list logo