+1
On Wed, Feb 18, 2009 at 6:45 AM, Jason van Zyl wrote:
> +1
>
>
> On 17-Feb-09, at 8:42 PM, Brian E. Fox wrote:
>
> New parents need to be released with the new distributionManagement
>> sections pointed at repository.apache.org:
>>
>> Apache Pom Diffs:
>> http://svn.apache.org/viewvc/maven/p
ok. We are waiting to see if parents can be released quickly or if we hav to
adapt the plugin to use new settings (nexus)
On Wed, Feb 18, 2009 at 4:18 AM, Barrie Treloar wrote:
> On Tue, Feb 17, 2009 at 4:12 PM, Arnaud HERITIER
> wrote:
> > oh right. thx for this warning. I'll wait few days to
Brett Porter wrote:
On 18/02/2009, at 7:23 AM, John Casey wrote:
It will take less effort for me to just keep working on issues until
they are done, so that's what I'll do. So, agreed, next version is
2.1.0, standard RC cycle applies.
I'm fine whittling away some of what's left out there.
+1
On 17-Feb-09, at 8:42 PM, Brian E. Fox wrote:
New parents need to be released with the new distributionManagement
sections pointed at repository.apache.org:
Apache Pom Diffs:
http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584&r
2=745325&diff_format=h
Staged at:
https://
On Tue, Feb 17, 2009 at 4:12 PM, Arnaud HERITIER wrote:
> oh right. thx for this warning. I'll wait few days to see if we can release
> new parents.
Ahh.
Yes you can try releasing Arnaud.
My computer went boom on 26th Jan, i've only just got it back up to
limping speed and a default check out o
+1
Brian E. Fox wrote:
New parents need to be released with the new distributionManagement
sections pointed at repository.apache.org:
Apache Pom Diffs:
http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584&r
2=745325&diff_format=h
Staged at:
https://repository.apache.org/conte
New parents need to be released with the new distributionManagement
sections pointed at repository.apache.org:
Apache Pom Diffs:
http://svn.apache.org/viewvc/maven/pom/tags/apache-5/pom.xml?r1=639584&r
2=745325&diff_format=h
Staged at:
https://repository.apache.org/content/repositories/staging-48
On 18/02/2009, at 7:23 AM, John Casey wrote:
I fully agree with Brian about the version naming for the next
release.
I couldn't possibly care less what version we use at this point, only
that we start doing releases again. I want to see 2.1 out as much as
anyone. However, it was frustrat
+1. The sooner the better.
Brian E. Fox wrote:
Well lets get a release then so we have something to try. It's been a
waiting game it seems so far. If there's a release we can integrate soon
enough into the cycle, then we have a chance of detecting and fixing any
issues. It always seems to come u
The new staging repo location is:
https://repository.apache.org/content/repositories/maven-staging-4847e34
062fc70/
Just double check that everything looks ok to you.
-Original Message-
From: Dennis Lundberg [mailto:denn...@apache.org]
Sent: Tuesday, February 17, 2009 2:26 PM
To: Maven D
Well lets get a release then so we have something to try. It's been a
waiting game it seems so far. If there's a release we can integrate soon
enough into the cycle, then we have a chance of detecting and fixing any
issues. It always seems to come up far too late in the cycle to do
anything about i
I'm undecided about what version number to use, and leave that decision
to others.
One issue that I strongly feel needs to go into 2.1.0 final is MNG-3602,
the inclusion of Doxia 1.1 into the core. According to the release plan
for Doxia [1], Lukas had agreed to release Doxia 1.1. If he's not
avai
Hi Brian,
Do you plan to release the parent shortly?
Vincent
2009/2/13, bri...@apache.org :
> Author: brianf
> Date: Fri Feb 13 23:54:30 2009
> New Revision: 744300
>
> URL: http://svn.apache.org/viewvc?rev=744300&view=rev
> Log:
> use the new parent
>
> Modified:
> maven/doxia/doxia-s
Kool and the gang.
On 17-Feb-09, at 2:49 PM, Hervé BOUTEMY wrote:
ITs passed without any problem
upgrade done in r745216
Regards,
Hervé
Le lundi 16 février 2009, Jason van Zyl a écrit :
I assume you've tried it with 2.1? If all the same integration tests
pass then I don't see any downside.
WhoopsI had the filtering on for my src/main/resources/assemblies
directory.
jmaxwell wrote:
>
> When using a shared assembly descriptor the ${artifact.id} and
> ${project.id} properties are set to the shared assembly descriptor values
> and NOT to the values of the executing project.
>
> T
I fully agree with Brian about the version naming for the next release.
Given its track record over the last 6 months, using -M1 for the last
release crippled it unfairly in the public view; it's at least as stable
as 2.0.9, even with the problems we had concerning wagon 1.0-beta-4.
IMO, there
ITs passed without any problem
upgrade done in r745216
Regards,
Hervé
Le lundi 16 février 2009, Jason van Zyl a écrit :
> I assume you've tried it with 2.1? If all the same integration tests
> pass then I don't see any downside.
>
> On 15-Feb-09, at 5:52 PM, Hervé BOUTEMY wrote:
> > I'll try to
Thanks Brian.
I'm reading up on the new repo as we speak.
Brian E. Fox wrote:
> I'll copy the artifacts to a staging repo for you tonight and then you can
> promote it when the vote is closed.
>
>
> On 2/17/09 1:25 PM, "Dennis Lundberg" wrote:
>
>> +1 from me
>>
>> Dennis Lundberg wrote:
>>>
I'll copy the artifacts to a staging repo for you tonight and then you can
promote it when the vote is closed.
On 2/17/09 1:25 PM, "Dennis Lundberg" wrote:
> +1 from me
>
> Dennis Lundberg wrote:
>> Hi,
>>
>> (resending due to SMTP-server problems)
>>
>> The time has finally come to release
Sorry, I only read the first part of your email. I think the controlling the
threads with a setting is a good idea.
I don't see any point in doing another milestone release. The current code
is as stable as 2.0.9/10 yet noone can use it because it's a milestone. It
serves us no point because we do
Hi,
Igor has submitted patches to make the operation of the resources
plugin work in an incremental environment like m2e. So I want to
release maven-filtering and the resources plugin. There is a patch for:
http://jira.codehaus.org/browse/MSHARED-78
And we've been using a patch version of
+1 from me
Dennis Lundberg wrote:
> Hi,
>
> (resending due to SMTP-server problems)
>
> The time has finally come to release Doxia 1.0. For more info on the
> relationship to plugins and other components, see the Doxia Release Plan at
> http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
>
Oleg Gusakov wrote:
>
>
> Dennis Lundberg wrote:
>> If it's possible I'd like to continue this release with the artifacts
>> that were already built. I've been through hell and back already trying
>> to get this release out the door.
>>
> This is an interesting remark. I felt exactly the same
Thanks Stéphane,
I've renamed the 2.1 version in JIRA to 2.1-beta-1.
I also added a new 2.1 version in JIRA.
Stephane Nicoll wrote:
> I'd say beta-1 is fine.
> Thanks,
> Stéphane
>
> On Sun, Feb 15, 2009 at 6:32 PM, Dennis Lundberg wrote:
>
>> I'm looking at releasing a new version of Maven WA
On 17-Feb-09, at 4:05 AM, Mark Hobson wrote:
2009/2/16 pi song :
I have just noticed that Maven3 is on the way. The new dependency
resolver
really looks very interesting. Just curious how would that affect
maven-shared/maven-dependency-tree. Will this API stay the same or be
replaced?
I'd
Additional clarifications:
Oleg Gusakov wrote:
pi song wrote:
I just had a look at Mercury artifact resolver. It currently returns a list
of artifacts.
Mercury has the following resolution APIs - see DependencyBuilder
interface:
I became so addicted to m2eclipse that completely forgot tha
pi song wrote:
I just had a look at Mercury artifact resolver. It currently returns a list
of artifacts.
Mercury has the following resolution APIs - see DependencyBuilder interface:
- buildTree - creates a full metadata tree
- resolveConflicts has two flavors
-- List resolveConflicts( Meta
not plugin devs only. I've started using dependency-tree component in
netbeans maven support extensively as well. It's very convenient..
Milos
On Tue, Feb 17, 2009 at 1:20 PM, pi song wrote:
> I just had a look at Mercury artifact resolver. It currently returns a list
> of artifacts.
> I think y
I just had a look at Mercury artifact resolver. It currently returns a list
of artifacts.
I think you will need a middle man to help expose that list as simplified
tree anyway (for plug-in developers).
Am I right? Just want to understand a bit more.
Pi Song
On Tue, Feb 17, 2009 at 8:05 PM, Mark
Benjamin Bentmann wrote:
Alright, I just requested infra to remove the jobs [0].
[0] http://issues.apache.org/jira/browse/INFRA-1901
According to infra, it's up to either Brian, Wendy or Jason to remove
the jobs. Anyone of you three willing to push the button? Please :-)
Benjamin
---
2009/2/16 pi song :
> I have just noticed that Maven3 is on the way. The new dependency resolver
> really looks very interesting. Just curious how would that affect
> maven-shared/maven-dependency-tree. Will this API stay the same or be
> replaced?
I'd personally be in favour of mercury supersedin
31 matches
Mail list logo
