They can be removed from trunk - it was to produce a 3.0.0 model
version for Maven 1.1.
On 06/02/2009, at 11:05 PM, Jason van Zyl wrote:
I Arnaud and Lukas would know best. The last version of Maven 1.x
started using these I believe, so if someone wanted to work on the
older version they w
Just an idea:
don't forget the archetype plugin:
https://docs.sonatype.com/display/NX/Nexus+Archetype+Plugin
Having it on r.a.o would be awesome. I can easily "downgrade" is to support
Nexus 1.2.x (until 1.3 is not released).
~t~
On Fri, Feb 6, 2009 at 4:52 PM, Brian E. Fox wrote:
> I have tho
Can we implement modello's identity/identifier element in maven.mdo
rather than hand-coding the identity methods?
-john
br...@apache.org wrote:
Modified:
maven/components/branches/maven-2.0.x/maven-model/src/main/mdo/maven.mdo
URL:
http://svn.apache.org/viewvc/maven/components/branches/maven
Is there a reason we haven't banned multiple plugin entries in a single
POM? I thought we talked about this ages ago...frankly, I'm a little
shocked that we never got it in code...
-john
br...@apache.org wrote:
Author: brett
Date: Fri Feb 6 10:48:10 2009
New Revision: 741522
URL: http://svn
I thought the parallel download was already in there? I reached out to
Don several times about tests and never heard back which is unfortunate.
In my testing it did seem to work fine and was faster even with a repo
manager in place. If it's not already in there and we have no tests,
then I guess we
I don't really get a vote, but as a user, implementer, and
recommender, I heartily agree with this. parallel resolution in 2.2,
and tie off a 2.1 final as quickly as possible.
Cheers,
Christian.
On 6-Feb-09, at 12:12 , John Casey wrote:
Benjamin Bentmann wrote:
John Casey wrote:
At that p
Benjamin Bentmann wrote:
John Casey wrote:
At that point, we can make plans for a relatively fast release of
2.1.1 for the higher-risk issues that are sitting in the 2.1.0-M*
buckets now...possibly parallel artifact downloads if we can ever get
test coverage for that.
IMHO the introduction
John Casey wrote:
In light of the above, along with the good stability we've seen in the
first milestone release, I'd *much* prefer pushing toward a release of
2.1.0-final.
+1.
At that point, we can make plans for a relatively fast release of 2.1.1
for the higher-risk issues that are sittin
Hi everyone,
I wanted to step back from the current Maven 2.1.0-M* release plan for a
second and reassess our progress on the issues we were planning as the
centerpiece for each release.
I've been trying to match up the milestone issues found on
http://docs.codehaus.org/display/MAVEN/Maven+2
I have thought about backing up the repo as well but haven't acted on it for
one main reason: the entire content of the apache repository is replicated to
central and then around the world to countless sites. There isn't much to lose
here that makes me overly concerned about replicating the repo
well might be a bit belated but I am +1 for this as well, bringing a
bit of order to the staging process is a good thing..
my only concern which I have written a number of responses to only to
just delete and not send is something that has been brought up a
number of times on the infra list...
ne
On 6-Feb-09, at 12:23 AM, Ralph Goers wrote:
On Feb 5, 2009, at 10:34 PM, Jason van Zyl wrote:
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 sta
I Arnaud and Lukas would know best. The last version of Maven 1.x
started using these I believe, so if someone wanted to work on the
older version they would most likely need these. They probably don't
need to be in trunk but we should keep a copy around somewhere in the
event someone wants
I already fixed up his account.
On 6-Feb-09, at 12:42 AM, Petar Tahchiev wrote:
Hi Jason,
I just forwarded your email to the codehaus support.
They should take care for this.
Cheers.
2009/2/5 Jason Chaffee :
I am not sure if anyone can help me, but I wasn't able to find an
admin email on
Thanks for pointing it out. The symlink following should be false by
default to prevent this (and obviously the ability to actually set it
would be handy)
-Original Message-
From: Bouiaw [mailto:bou...@gmail.com]
Sent: Friday, February 06, 2009 8:18 AM
To: dev@maven.apache.org
Subject: Cr
Benjamin Bentmann wrote:
>
> Costin Caraivan wrote:
>
>> By the way, this works when I move the section in the
>> root
>> of the plugin.
>
> We have a (passing) IT [0] to test configuration which
> includes a Map parameter so I wonder how do you invoke your mojo in the
> first place? From
Hi,
I think I have a found a huge bug in Maven clean plugin that could lead to
dataloss :
http://jira.codehaus.org/browse/MCLEAN-39
I am not used to highlight bugs in this list, but if it is confirmed, it is
a really critical issue that could lead to very dangerous dataloss.
Regards,
Bouiaw
Hi,
the core module maven-model in all three dev branches contains the files
- maven.xml
- project.xml
- project.properties
Are these just relicts from former M1 days and could be deleted or do
they still serve a purpose?
Benjamin
Hello,
I have a custom mojo that calculates the values for the properties
releaseVersion and developmentVersion of the maven-release-plugin. I would like
to invoke the release as follows:
mvn telenet:getNextVersion release:prepare
How should I define these properties so the release plugin p
John,
> Subject: Re: How to get path to the local repository?
>
> If you're injecting this information into a plugin parameter,
> you can use the expression '${localRepository}' to get the
> ArtifactRepository instance, then call getBasePath() from that, IIRC.
For a custom plugin, I also need
Hi Jason,
I just forwarded your email to the codehaus support.
They should take care for this.
Cheers.
2009/2/5 Jason Chaffee :
> I am not sure if anyone can help me, but I wasn't able to find an admin email
> on jira.
>
> I changed companies and thus my email changed. I thought I had changed
On Feb 5, 2009, at 10:34 PM, Jason van Zyl wrote:
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 parti
22 matches
Mail list logo
