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
You should google for egit...it's only in 0.3, IIRC, but seems to
work relatively well for the basics of commit, update, add, remove, etc.
-john
On Nov 13, 2007, at 9:15 AM, Paul Gier wrote:
Jason van Zyl wrote:
On 12 Nov 07, at 4:21 PM 12 Nov 07, Mark Struberg wrote:
--- Johan Kindgren <[
Yeah that makes sense. Which way is it now?
-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 15, 2007 11:30 PM
To: Maven Developers List
Subject: Re: moving forward with 2.0.8
Brian E. Fox wrote:
> I think classes should be first. (before test-class
Max O Bowsher wrote:
>
> Brian E. Fox wrote:
>> I think classes should be first. (before test-classes)
>
> Presumably the rationale is to allow test-classes to contain resources
> which override same-named resources in the main classes dir, or something?
Test-classes should be first, as reques
Why ?
is it documented somewhere ?
On Nov 15, 2007 4:51 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> You need to add an element when you update to maven-plugins:10.
>
> [EMAIL PROTECTED] wrote:
> > Author: vsiveton
> > Date: Thu Nov 15 04:09:48 2007
> > New Revision: 595283
> >
> > URL: http
On Thursday 15 November 2007, Brian E. Fox wrote:
> Ultimately I think the intent was that the order be slightly
> controllable via the order in the dependencies list. If that's still
> the case, then it seems ok to me.
I completely agree with that. If it makes it PREDICTABLE and
CONTROLLABLE,
Brian E. Fox wrote:
> I think classes should be first. (before test-classes)
Wasn't that the old way, and it's recently been switched?
Presumably the rationale is to allow test-classes to contain resources
which override same-named resources in the main classes dir, or something?
Max.
signat
Ultimately I think the intent was that the order be slightly controllable via
the order in the dependencies list. If that's still the case, then it seems ok
to me.
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 15, 2007 7:49 AM
To: Maven Develo
I think classes should be first. (before test-classes)
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 15, 2007 11:14 PM
To: dev@maven.apache.org
Cc: Brian E. Fox
Subject: Re: moving forward with 2.0.8
On Thursday 15 November 2007, Brian E. Fox wro
nobody to review the change?
nobody against me merging it to trunk?
Le dimanche 04 novembre 2007, Hervé BOUTEMY a écrit :
> can someone expert in release plugin review this commit?
> I had to upgrade the dependency and fix expected POM files: I don't see any
> problem in the new POM content, but I
You need to add an element when you update to maven-plugins:10.
[EMAIL PROTECTED] wrote:
Author: vsiveton
Date: Thu Nov 15 04:09:48 2007
New Revision: 595283
URL: http://svn.apache.org/viewvc?rev=595283&view=rev
Log:
o bumped to maven-plugins:10
o removed junit dependency
Modified:
maven/
Brian E. Fox wrote:
All,
It's time to move forward with 2.0.8. I stopped to evaluate MNG-3259 but
I think this is an edge case and the fix has a greater chance of
breaking more stuff. I'd rather fix this early in 2.0.9 so there is
plenty of time for any issues to surface. I've placed a new build
Hi,
I have comitted a fix in rev 595059.
--
Olivier
2007/11/14, Vincent Siveton <[EMAIL PROTECTED]>:
>
> Dennis,
>
> I am aware with this. I will implement MCLEAN-8
>
> Cheers,
>
> Vincent
>
> 7/11/14, [EMAIL PROTECTED] <
> [EMAIL PROTECTED]>:
> > Online report :
> http://maven.zones.apache.org/c
13 matches
Mail list logo
