Hey Oleg,
Curious, will the Mecury wagon provider be the new handler for the dav:
protocol extension?
Cheers
James
On Thu, 2008-10-02 at 22:34 -0700, Oleg Gusakov wrote:
> I have been testing Mercury wagon provider with 2.2.x and 2.1.x branches
> and successfully pass all the ITs but one, please
I have been testing Mercury wagon provider with 2.2.x and 2.1.x branches
and successfully pass all the ITs but one, please see the tracking
comments in http://jira.codehaus.org/browse/MERCURY-8 and it's subtasks
The missing test - it0031 - deals with plugin alias remapping, which
happens well
On 03/10/2008, at 3:16 PM, Oleg Gusakov wrote:
* Does it make sense to release the mercury transport stuff (I
believe otherwise known as awesome-jetty-bits) separately to have
it available sooner?
I am working on that, will try to stage tomorrow.
Ah, so you mean release the whole thing, b
Brett Porter wrote:
Ping
Sorry - did not catch this posting.
On 26/09/2008, at 11:22 PM, Brett Porter wrote:
Oleg,
Sorry for the delay. I'm still planning to dig into this once I get
my head above water, but a couple of questions occurred to me in the
mean time:
* Does it make sense t
Ping
On 26/09/2008, at 11:22 PM, Brett Porter wrote:
Oleg,
Sorry for the delay. I'm still planning to dig into this once I get
my head above water, but a couple of questions occurred to me in the
mean time:
* Does it make sense to release the mercury transport stuff (I
believe otherwis
On 29/09/2008, at 12:05 PM, Jason van Zyl wrote:
Hi,
Some issues have been fixed in the shade plugin but I wanted to get
them out.
Issues Resolved (5):
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11540&fixfor=14381
Staging Repository:
http://people.apache.org/~jvanz
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
htt
On 2-Oct-08, at 8:24 PM, Paul Benedict wrote:
Jason,
It wasn't clear. This thread has a little problem with clarity. :-)
Not if you know that all releases get voted on. Nothing can be
distributed without a vote from the governing PMC.
I
am glad to know alphas get voted on.
Paul
--
That's reasonable. We're not writing documentation for ephemeral
changes but a note is not a problem.
On 2-Oct-08, at 8:18 PM, Brian E. Fox wrote:
There should have been a comment for each one taken out as it was
taken
out, this should just be the rule.
-Original Message-
From: Jas
Jason,
It wasn't clear. This thread has a little problem with clarity. :-) I
am glad to know alphas get voted on.
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 03/10/2008, at 10:18 AM, Brian E. Fox wrote:
There should have been a comment for each one taken out as it was
taken
out, this should just be the rule.
+1
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---
Who said anything about not voting?
On 2-Oct-08, at 8:18 PM, Paul Benedict wrote:
I am confused about if this is going to be "released" or not? But as a
reminder, ASF policy says a "release" is strictly a build that has
been voted on and approved. Without a votes, it's not a release --
just a b
I am confused about if this is going to be "released" or not? But as a
reminder, ASF policy says a "release" is strictly a build that has
been voted on and approved. Without a votes, it's not a release --
just a build. And builds cannot be advertised for downloading due to
legal reasons, from what
There should have been a comment for each one taken out as it was taken
out, this should just be the rule.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 7:31 PM
To: Maven Developers List
Subject: Re: Shooting for 3.0-alpha-1 staging for
This is not required for the alphas, the second we start into the
betas then yes I would agree. Some of the ITs will go on/off while
we're changing things.
On 2-Oct-08, at 7:24 PM, Brett Porter wrote:
One thing I would like to see before any release is documentation on
why each of the inte
One thing I would like to see before any release is documentation on
why each of the integration tests excluded for 3.0 are excluded. This
goes hand in hand with a compatibility document that explains to users
what functionality they can expect not to work and what to change
(particularly e
Yes, we will be there. We have Maven training that Bruce and I will be
doing (to be announced shortly). We have also booked a room the night
of November 5th to talk about Maven related stuff and provide a venue
where we can talk for 4-5 hours. We also have some pretty big
announcements to m
On 02/10/2008, at 11:18 PM, Brian E. Fox wrote:
In that case, I suggest that while we should vote to make it
official,
it shouldn't be placed on the mirror infrastructure or website then
as
a tarball (ie, just the synced repository, and people.apache.org/
builds).
*checks the list to
>In that case, I suggest that while we should vote to make it official,
>it shouldn't be placed on the mirror infrastructure or website then as
>a tarball (ie, just the synced repository, and people.apache.org/
>builds).
*checks the list to make sure he's still on the Maven list and not that
ot
Jason, are you and some of the other sonatype folks going to make
apachecon? would be good to do something like this while a mess of us
are there as well...
cheers
jesse
On Thu, Oct 2, 2008 at 7:11 AM, Christian Edward Gruber
<[EMAIL PROTECTED]> wrote:
> Crap! I was there (right in Mountain Vie
On 2-Oct-08, at 8:21 AM, Brett Porter wrote:
On 02/10/2008, at 9:51 PM, Jason van Zyl wrote:
Just a note that Shane and I are now going through the 3.0-alpha-1
list in JIRA to try and close and knock off as many issues as we can.
Colour me confused since you were the one arguing against t
On 02/10/2008, at 9:51 PM, Jason van Zyl wrote:
Just a note that Shane and I are now going through the 3.0-alpha-1
list in JIRA to try and close and knock off as many issues as we can.
Colour me confused since you were the one arguing against this months
ago :) Sounds good.
Did the proje
Crap! I was there (right in Mountain View) last week Thursday.
Oh well.
Christian.
On 2-Oct-08, at 07:49 , Jason van Zyl wrote:
Hi,
Next week Oleg, Shane and I are planning on doing some work on
Maven, to try and do some hacking and planning. It looks like Brian
is going to come now,
I don't grok that either - Maven 2.0.8 builds it just fine and doesn't
bundle the httpclient.
- Brett
On 02/10/2008, at 9:23 PM, Jason van Zyl wrote:
I don't think adding httpclient to the distribution to build a
certain project is a good idea. That seems extremely heavy handed.
Is this J
Please provide a write up for the rest of us (or a streaming video
feed, snapshots of whiteboards, whatever).
On 02/10/2008, at 9:49 PM, Jason van Zyl wrote:
Hi,
Next week Oleg, Shane and I are planning on doing some work on
Maven, to try and do some hacking and planning. It looks like Bri
Just a note that Shane and I are now going through the 3.0-alpha-1
list in JIRA to try and close and knock off as many issues as we can.
This will certainly be an alpha and we don't recommend anyone go near
it, we just want to get the ball rolling on releases.
Thanks,
Jason
--
Hi,
Next week Oleg, Shane and I are planning on doing some work on Maven,
to try and do some hacking and planning. It looks like Brian is going
to come now, Bruce Snyder and possibly Ralph are going to show up as
well. So Sonatype is going to organize a room and it looks like we'll
have r
https://ci.sonatype.org/view/Reports/
http://www.sonatype.org/~j2ee-hudson/reports/
They are launched every night and every 5 minutes if the code changed.
cheers
..
Arnaud HERITIER
..
I don't think adding httpclient to the distribution to build a certain
project is a good idea. That seems extremely heavy handed.
Is this JAR actually being specified in the target project?
On 1-Oct-08, at 9:48 PM, [EMAIL PROTECTED] wrote:
Author: sisbell
Date: Wed Oct 1 18:48:18 2008
New R
No one was suggesting putting Mercury into 2.0.x. That would be a bad
idea.
Only in a cycle, the next major version, would it make sense to make
changes.
We already made many changes that were too drastic. The wagon changes
were not a good idea, just many of the other significant changes
30 matches
Mail list logo
