> We do need the password security changes finished. Oleg, are you working on
> the docs or should I put them together based on your blog? Is there anything
> else left to do in the code? I think that dependency needs to be out of
> alpha before we go final - I think we discussed that sort of crite
I don't believe the existing Its test parallel downloads specifically.
-Original Message-
From: Don Brown [mailto:mr...@twdata.org]
Sent: Saturday, February 07, 2009 10:48 PM
To: Maven Developers List
Subject: Re: Maven 2.1.0 Plans (a proposal of sorts)
It would be a shame to drop such a
It would be a shame to drop such a useful feature like parallel
downloads when it is working perfectly and been used by developers for
months with no reports of problems. While more integration tests are
always good, the bits of code I modified are covered by existing
tests, so to say it has no te
All set.
-Original Message-
From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett
Porter
Sent: Saturday, February 07, 2009 9:53 PM
To: Maven Developers List
Subject: requesting admin access to the Maven projects on
grid.sonatype.org
Hi,
The Maven 2.1.x group on the CI is wr
Hi,
The Maven 2.1.x group on the CI is wrong so I'd like to fix it up. My
username is 'brett' - can someone give me access?
Thanks,
Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
On 07/02/2009, at 7:12 PM, Torben S. Giesselmann wrote:
John Casey wrote:
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...
Yes, I was surprised too - I appli
(for some reason this got bounced as spam earlier, so I rewrote it and
chopped the quotation in the hope it gets through...)
I thought this was already the direction we were going... (see
"releasing 2.0.10" thread).
I already suggested we drop the auto parent version and PGP stuff from
th
yes you can remove them from trunk.
Maven 1.1 (http://svn.apache.org/repos/asf/maven/maven-1/core/tags/maven-1.1)
uses Maven Model 3.0.2 (
http://svn.apache.org/repos/asf/maven/components/tags/maven-model-3.0.2/).
cheers
Arnaud
On Sat, Feb 7, 2009 at 3:53 AM, Brett Porter wrote:
> They can be
I agree to have a 2.1 ASAP with well tested features.
We'll move others like // downloads in a 2.2
Arnaud
On Fri, Feb 6, 2009 at 5:36 PM, John Casey wrote:
> 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 issue
It might be worth adding a warning if a second plugin entry is
detected, as that will begin to create an awareness of this non-
recommended practice.
Christian.
On 7-Feb-09, at 06:12 , Torben S. Giesselmann wrote:
John Casey wrote:
Is there a reason we haven't banned multiple plugin entries
John Casey wrote:
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...
I would recommend such a change for 2.1, not 2.0.x, since that would
probably break a lot of e
Costin Caraivan wrote:
The invocation is from the pom.xml, inside a profile. So execution bound to
a build lifecycle.
Then consider to drop an example project in JIRA so we can have closer
look and something to reproduce the issue. From the few bits given so
far, I have no idea what might be
12 matches
Mail list logo
