+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
...@maven.apache.org
--
View this message in context:
http://www.nabble.com/-VOTE--Maven-3.0-alpha-2-tp21846015p21849460.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev
I checked it with on a simple project using jaxws wsgen and it works
now (it was failing with 3.0-alpha1), good news.
I tried on other projects where I got an maven ant involved to grab
some system informations :
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
-1 on a procedural basis.
There needs to be a URL for JUST the artifacts going into this release.
Right now, I see 2.0.10-RC8 stuff along with 3.0-alpha-2 stuff and enforcer
stuff in the URL presented. I should have to sift through all the files in
the URL to figure out which is stuff
.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, February 05, 2009 9:21 AM
To: dev@maven.apache.org
Subject: Re: [VOTE] Maven 3.0-alpha-2
-1 on a procedural basis.
There needs to be a URL for JUST the artifacts going into this release.
Right now, I see 2.0.10-RC8
On 4-Feb-09, at 11:35 PM, Oleg Gusakov wrote:
+1
This is awesome news - real repository manager at last !! When can
we start using it?
I'm going to stage a few 3.0 alphas, Brian is going to do the 2.0.x
and I believe John is going to stage the 2.1.x releases there so lets
work
On 5-Feb-09, at 3:48 AM, Henri Gomez wrote:
I checked it with on a simple project using jaxws wsgen and it works
now (it was failing with 3.0-alpha1), good news.
I tried on other projects where I got an maven ant involved to grab
some system informations :
Ant stuff doesn't work properly.
On 5-Feb-09, at 6:21 AM, Daniel Kulp wrote:
-1 on a procedural basis.
That's the grouping for convenience but everything is separate under
the covers. I see Brian gave you the separate. Don't worry nothing
gets staged together in blobs, each deployment is actually separated.
If I
Ant stuff doesn't work properly. Let's do the same thing, make a test
project and we'll work through it.
Do you need a sample projet using ant task or something without ant ?
-
To unsubscribe, e-mail:
I think your problem is specifically with ant so something that
represents what you tried to do in the project that failed would be
handy.
If you pull a new update-dev build of m2e you'll notice that we have
the problem reporting integrated now. With latest build you can go
down to the
I think your problem is specifically with ant so something that represents
what you tried to do in the project that failed would be handy.
I'll do a sample project.
If you pull a new update-dev build of m2e you'll notice that we have the
problem reporting integrated now. With latest build
I'll do a sample project.
Done
If you pull a new update-dev build of m2e you'll notice that we have the
problem reporting integrated now. With latest build you can go down to the
Maven menu and at the bottom you'll see the Report Issue... option. You
can put in the summary, description, and
[mailto:dk...@apache.org]
Sent: Thursday, February 05, 2009 9:21 AM
To: dev@maven.apache.org
Subject: Re: [VOTE] Maven 3.0-alpha-2
-1 on a procedural basis.
There needs to be a URL for JUST the artifacts going into this release.
Right now, I see 2.0.10-RC8 stuff along with 3.0-alpha-2 stuff
Subject: Re: [VOTE] Maven 3.0-alpha-2
I'll withdraw my -1 and put a +1
That said, in the future, make sure the appropriate URL is used in the
VOTE
message. The vote needs to be very clear exactly which artifacts (and
no
others) are being voted on. It might be best to separate
in case you're trying to build against it, but they are separated
into
different repos.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, February 05, 2009 9:21 AM
To: dev@maven.apache.org
Subject: Re: [VOTE] Maven 3.0-alpha-2
-1 on a procedural basis
Hi,
This release worked out better and the release profile is working now
and everything is signed. This release is being staged with Nexus that
we've installed in a new zone. So Brian and I are guinea pigging the
whole setup. We deployed with a self-signed SSL cert and we've asked
for a
+1
This is awesome news - real repository manager at last !! When can we
start using it?
Jason van Zyl wrote:
Hi,
This release worked out better and the release profile is working now
and everything is signed. This release is being staged with Nexus that
we've installed in a new zone. So
17 matches
Mail list logo
