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
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/continuum/buildResult.action?buildId=35042&projectId=9
>
> Build statistics:
> State: Failed
> Previous State: Failed
>
Thanks for the trick!
WDYT to update the release-process doc?
Cheers,
Vincent
2007/11/14, Dennis Lundberg <[EMAIL PROTECTED]>:
> I could have sworn there was a JIRA for this, but I couldn't find an
> open one when I looked.
>
> To see if a pom is affected by this pom-rewrite-bug, I usually do
>
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
>
Thats right,
I'll first focus on writting such test-cases. This was in my todo list for
long time :-/
Nico.
2007/11/14, Joakim Erdfelt <[EMAIL PROTECTED]>:
>
> Don't we have unit testing around the server side relocation?
> If not, I think we need to get them into place as part of the solution
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,
> >
> >
I could have sworn there was a JIRA for this, but I couldn't find an
open one when I looked.
To see if a pom is affected by this pom-rewrite-bug, I usually do
mvn release:prepare -DdryRun=true
After that I diff the original file pom.xml with the one called
pom.xml.tag to see if the license h
