t; 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-classes)
>
> Wasn't that
her
> 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-classes)
>
> Wasn't that the old way, and it's recently been switched
Benjamin Bentmann wrote:
>
> ... as requested by MNG-3118
>
MNG-2365 is a duplicate and could be closed as well. I attached a unit test
to this issue that checks the test class path ordering.
I would also like to point out trivial issues (documentation) that would
require less than an hour to
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 t
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
etely OK with the change. I've fixed my testcase
so it works properly either way now.
Dan
>
> -Original Message-
> From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 15, 2007 7:49 AM
> To: Maven Developers List
> Subject: Re: moving forward with
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
Maven Developers List
Subject: Re: moving forward with 2.0.8
Perhaps I know the code that changed the order:
while fixing "[MANTTASKS-22] ensure proper order of artifacts in
ArtifactResolutionResult", the fix in trunk (r591996) was to transform a
HashSet to a L
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
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
Perhaps I know the code that changed the order:
while fixing "[MANTTASKS-22] ensure proper order of artifacts in
ArtifactResolutionResult", the fix in trunk (r591996) was to transform a
HashSet to a LinkedHashSet in
o.a.m.artifact.resolver.ArtifactResolutionResult.
But when porting the fix back
worked for my build
Raphaël
2007/11/13, Brian E. Fox <[EMAIL PROTECTED]>:
> 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
>
Brian,
2.0.8 seems to have re-ordered the classpath or something such that if I
have a unit test that does:
System.out.println(getClass().getResource(".").toString());
it prints out the directory in the target/classes dir instead of the
target/test-classes.With 2.0.5 - 2.0.7, it returned th
Brian,
CXF doesn't build with 2.0.8-SNAPSHOT. It builds fine with 2.0.7, but
I'm getting test failures with 2.0.8-SNAPSHOT. I'll try and dig into
it in a bit.
Also, the README.txt needs updating before you release it.
Dan
> 2007/11/13, Brian E. Fox <[EMAIL PROTECTED]>:
> > All,
> >
> >
14 matches
Mail list logo
