On 04/02/2009, at 11:51 AM, Nick Pellow wrote:
Hi Brett,
It's always hard to tell from the output - is the resources call in
the forked lifecycle or the main one afterwards? The latter would
not retain all the settings.
I'm not 100% certain, however it looks like the resources call is
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
Jason van Zyl-5 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 Brian and I are guinea pigging the
whole setup. We deployed with a
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
This is the url jason meant to use:
https://repository.zones.apache.org/content/repositories/maven-staging-4
45ef7146ac750/
The group url logically combines the artifacts into a single repository
in case you're trying to build against it, but they are separated into
different repos.
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:
Hello,
I have a plugin with the following configuration:
configuration
featureId
groupIdcom.axway.md/groupId
artifactIdcom.axway.md/artifactId
version${project.version}/version
typezip/type
/featureId
pluginsUnpackFolderaoleu/pluginsUnpackFolder
featuresUnpackFolderaoleu/featuresUnpackFolder
Costin Caraivan wrote:
Hello,
I have a plugin with the following configuration:
configuration
featureId
groupIdcom.axway.md/groupId
artifactIdcom.axway.md/artifactId
version${project.version}/version
typezip/type
/featureId
pluginsUnpackFolderaoleu/pluginsUnpackFolder
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
Brett Porter wrote:
(c) support only ranges [,]; (,); etc
+1, I agree with Paul and Stephen, the version range syntax supports a
superset of the +/- suffix and is already established in Maven land so
we should save ourselves from maintaining the other code.
Benjamin
Costin Caraivan wrote:
By the way, this works when I move the configuration section in the root
of the plugin.
We have a (passing) IT [0] to test execution configuration which
includes a Map parameter so I wonder how do you invoke your mojo in the
first place? From the command line? Per
Georgy Bolyuba wrote:
But I was looking for 2.x (2.1?).
Development on 2.0.x and 2.1.x happens on branches, see [0] for more
details on their checkout.
If anyone
could advice on how to start helping with maven 2.x (should I submit
patches against a tag or branch? should I build it from a
The trunk is under heavy development right now. Your best bet is to grab the
2.1.x branch instead.
-Original Message-
From: Georgy Bolyuba [mailto:boly...@gmail.com]
Sent: Thursday, February 05, 2009 12:58 PM
To: Maven Developers List
Subject: Same problem: cannot build the trunk
Hi,
Thanks Benjamin !
I put [MERCURY-69] off till I fix more urgent issues, that's why this
workaround. Will get to it as soon as I can :)
Benjamin Bentmann wrote:
Hi Oleg,
Author: ogusakov
Date: Thu Feb 5 16:56:40 2009
New Revision: 741180
URL:
OK, but I get these errors *without* the Clirr plugin, i.e. on a clean
checkout from svn.
Vincent Siveton wrote:
Hi Dennis,
Clirr plugin doesnt support ${reactorProjects} or aggregate so it is a
normal behaviour IMHO (and javadoc plugin 2.5 is correct).
As a workaround, you could create a
As proposed in separate threads[1][2] and Infra jira[3], we have setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is now setup and
several releases of Maven are already staged there.
The initial idea was to use LDAP for
+1
Brian E. Fox wrote:
As proposed in separate threads[1][2] and Infra jira[3], we have setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is now setup and
several releases of Maven are already staged there.
The initial
+1
On Thu, Feb 5, 2009 at 12:43 PM, John Casey jdca...@commonjava.org wrote:
+1
Brian E. Fox wrote:
As proposed in separate threads[1][2] and Infra jira[3], we have setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is
+1
On 5-Feb-09, at 12:31 PM, Brian E. Fox wrote:
As proposed in separate threads[1][2] and Infra jira[3], we have
setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is now setup and
several releases of Maven are already
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 it into something
like:
Staged artifacts being
Good idea. We will also change the urls of the generated staged repos to
be more like maven-staging-[userid]-[short uniq number] to make them
less onerous.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, February 05, 2009 3:58 PM
To: dev@maven.apache.org
I'll be writing a plugin for Nexus to publish all the correct release
information.
On 5-Feb-09, at 12:58 PM, Daniel Kulp wrote:
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
+1
Brian E. Fox wrote:
As proposed in separate threads[1][2] and Infra jira[3], we have setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is now setup and
several releases of Maven are already staged there.
The initial
+1 if nexus' team promises to fix as soon as possible any issue encountered
in it (to not block apache releases).
cheers
Arnaud
On Thu, Feb 5, 2009 at 9:50 PM, Jason van Zyl jvan...@sonatype.com wrote:
+1
On 5-Feb-09, at 12:31 PM, Brian E. Fox wrote:
As proposed in separate
+1 if nexus' team promises to fix as soon as possible any issue
encountered
in it (to not block apache releases).
Yes we will support it including mods needed, like the new security
realm and the plugin being built to make life easier.
On 5-Feb-09, at 2:04 PM, Arnaud HERITIER wrote:
+1 if nexus' team promises to fix as soon as possible any issue
encountered
in it (to not block apache releases).
We plan to take care of this part of the infrastructure and work with
the infrastructure team. We hope that other projects
Thus you have my +1
thx
On Thu, Feb 5, 2009 at 11:42 PM, Jason van Zyl jvan...@sonatype.com wrote:
On 5-Feb-09, at 2:04 PM, Arnaud HERITIER wrote:
+1 if nexus' team promises to fix as soon as possible any issue
encountered
in it (to not block apache releases).
We plan to take care of
On 05/02/2009, at 7:28 PM, Brett Porter wrote:
Is there anything the clover2 plugin should be doing to ensure that
these modifications are made on the transitively resolved projects?
I'd have to dig a bit - it has been a while. I thought that the
project in a forked lifecycle was
+1, conditional
- I'd like to see some simple, direct documentation on how to use this
(just reading chapter 9 of the Nexus book). I'll need it shortly for
2.1.0-M2.
- I'd like to make sure the old technique continues to work for the
foreseeable future
- This doesn't rule out using
On 03/02/2009, at 12:03 PM, Brett Porter wrote:
What's left before this is releasable as part of 2.1.x?
Just some manual testing and docs updates for the site when it's
ready.
In the mean time, can someone please release the dependency so that
we can move forward with the next
Weird, I was able to do it out of box
mvn site:stage -Preporting
http://people.apache.org/~vsiveton/doxia-1.0.x/
Cheers,
Vincent
2009/2/5 Dennis Lundberg denn...@apache.org:
OK, but I get these errors *without* the Clirr plugin, i.e. on a clean
checkout from svn.
Vincent Siveton wrote:
Hi
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
+1, conditional
- I'd like to see some simple, direct documentation on how to use this
(just reading chapter 9 of the Nexus book). I'll need it shortly for
2.1.0-M2.
This is step 4 below.
- I'd like to make sure the old technique continues to work for the
foreseeable future
If needed,
On 06/02/2009, at 11:44 AM, Brian E. Fox wrote:
+1, conditional
- I'd like to see some simple, direct documentation on how to use
this
(just reading chapter 9 of the Nexus book). I'll need it shortly for
2.1.0-M2.
This is step 4 below.
Sorry, lack of sleep. Must have glazed over
I'm not sure why this needs a vote. Just do it.
Ralph
On Feb 5, 2009, at 12:31 PM, Brian E. Fox wrote:
As proposed in separate threads[1][2] and Infra jira[3], we have
setup a
new zone and repository manager for hosting Apache artifacts at
https://repository.zones.apache.org. The service is
On 5-Feb-09, at 9:53 PM, Ralph Goers wrote:
I'm not sure why this needs a vote. Just do it.
This requires pulling all of the org.apache.maven.* artifacts into
Nexus and that's where they stay for this project because we can't
keep partial bits here and over on people. We are suggesting
42 matches
Mail list logo
