On 7-Jul-08, at 12:19 PM, Oleg Gusakov wrote:
That's exactly what the problem is.
To clarify: the new resolver only cares about metadata, not actual
binary. Current artifact, even as late as 3.0-SN, dictates that even
when you try to get artifact metadata, you get all the goods in the
local repo, and then get the metadata. I am trying the other way
around - get metadata only, resolve conflicts, and then download
actual artifacts that are required.
Yes, but downloading the set once known is relatively easy compared to
finding out what's required. What's import is that the two processes
are separated.
Oleg
The problem is that nowhere are the plugins told that maven 2.0.9
jars should be used instead of whatever they specified.
That is exactly a metadata analysis problem. Look at everything
that might be used and make a selection. Not download everything
and then decide.
Instead, it appears there is some "special" code that checks for
maven jars and as a last step ignores artifacts that are already
part of the distribution. In other words, the metadata to
correctly resolve this isn't even present.
It's all part of looking at the metadata. All the stuff gets
downloaded and then there is an artifact filter which blocks all
artifacts that are in the distribution. If the metadata was pulled
in first. Then it could be compared with what is in the
distribution, along with any other calculations, and then what is
actually required to satisfy the session whether that be artifacts,
plugins, or other resources are retrieved.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
---------------------------------------------------------------------
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]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more
examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
