Yes, looking at the log it is clear that they are ignored. Yet when I
was running under my IntelliJ debugger in one case it actually stepped
into the 2.0 version of DefaultMavenProjectBuilder. I don't really know
why. But I couldn't debug it since I had the 2.0.9 version of the source
and it was only showing me the class file.
As you may or may not know, I'm not a fan of "intelligent resolution of
versions", especially since artifacts can't declare how they are
compatible with their various versions. I don't believe that relying on
projects "knowing" what versions of their dependencies they are
compatible with won't scale and will lead to incorrect version ranges
all over the place.
I guess I'd rather see Maven be able to automatically add
managedDependencies for the Maven artifacts to the plugins it ships
with. Unfortunately, that isn't really possible since plugins can't have
a dependencyManagement section.
Ralph
Brett Porter wrote:
Yes.
Considering that Maven will actually only use the built-in ones at
runtime for plugins it is actually quite silly to download all the
other ones for plugins.
Though this is really indicative of a wider problem where we don't do
much in the way of intelligent resolution of versions. Hopefully this
is something any work on the artifact code works to address.
- Brett
On 07/07/2008, at 5:29 PM, Ralph Goers wrote:
Maybe this won't strike you as strange but it did me. I ran a mvn
install on a project using 2.0.9. In the course of that
maven-project-2.0, maven-project-2.0.6, maven-2.0.7, and
maven-project-2.0.9 were downloaded, installed into the local repo
and then used in the build. As you would expect this is due to the
use of the various plugins used during the build. Knowing what I know
about maven I understand why this us. But the question remains,
doesn't this just seem wrong? Shouldn't maven 2.0.9 only use maven
2.0.9 jars?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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]
