On 15 Jan 07, at 6:29 AM 15 Jan 07, Fabrice Bellingard wrote:
Hi Jason,
I've just tested Maven 2.0.5 on complex projects, and I've had 2
problems
who broke the builds.
The first is about dependency resolution. In the dependency tree of
one of
my projects, I have 2 versions of the same lib at the same depth:
version
3.1 and 2.1. With Maven 2.0.4, version 3.1 is selected for
compiling and
testing, which is what I want. With Maven 2.0.5, version 2.1 is
selected,
which breaks my unit tests because the code requires version 3.1 to
run. I'm
not sure if this is a bug or not - maybe this resolution principle
was to be
the default behaviour, but the fact is that there's a difference
between
2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but
haven't found
any fixed issue related to that.
I myself have intentionally stayed away from artifact resolution on
the branch so do you have a test project I can use. I need to be able
to reproduce your problem and turn it into some form of test. So I
can see what's going on and so it doesn't regress again, if it is
indeed a regression.
I had the second problem when executing the Checkstyle plugin
(version 2.1).
So I dug a bit to see if this could be related to maven core or
not, and
here is what I found.
I isolated the code that breaks the build in the checkstyle plugin: it
happens when the plugin tries to load my Checkstyle configuration
file,
which is actually located in a JAR that is specified in the build
extensions. The code lies in the Locator#resolveLocation() method:
*// Attempt a Resource.
* URL url =
*this*.getClass().getClassLoader().getResource( location );
This code returns null for the "url" variable, which in turns
breaks the
plugin because it doesn't find any configuration file.
I haven't had the time to dig more into it, but I found the
following issue
that might be related to this problem: "MNG-2228 : Classloader problem
loading jars from build extensions"<http://jira.codehaus.org/browse/
MNG-2228>.
Brett and Carlos worked on it and fixed it, so maybe they could
tell more
about it.
That doesn't sound good though 2.0.4 and 2.0.5 both use the same
versions of classworlds and plexus so you're sure you have the same
version of the checkstyle plugin there?
Apart from that, everything else works perfectly. Maybe some of us
can tell
a bit more about those problems?
Cheers,
Fabrice.
On 1/12/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
The entire release is staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/
The assemblies that people are interested in are staged here:
http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven-
core/2.0.5/
Here is the JIRA roadmap:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&fixfor=12294&sorter/field=issuekey&sorter/
order=DESC
That's about it. Play around with it, if there are things wrong and
I'll fix stuff. We haven't released in so long there very well may be
some problems.
We should probably let it sit until Tuesday as most folks won't try
it out over the weekend.
+1
Thanks,
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
