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. A
Barrie Treloar wrote:
On Wed, Jul 9, 2008 at 2:05 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
At the moment - metadata includes a URI to the actual binary. I am working
on integrating it with a new delivery vehicle, and that will be the "first"
found. So all is defined by the order of repos
On Wed, Jul 9, 2008 at 2:05 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
> At the moment - metadata includes a URI to the actual binary. I am working
> on integrating it with a new delivery vehicle, and that will be the "first"
> found. So all is defined by the order of repositories. As Nexus reposi
Barrie Treloar wrote:
On Tue, Jul 8, 2008 at 1:49 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
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
On Tue, Jul 8, 2008 at 1:49 AM, Oleg Gusakov
<[EMAIL PROTECTED]> wrote:
> 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 t
On 08/07/2008, at 2:38 AM, Oleg Gusakov wrote:
Jason van Zyl wrote:
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
eve
Jason van Zyl wrote:
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
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
lo
Jason van Zyl wrote:
On 7-Jul-08, at 10:19 AM, Ralph Goers wrote:
Jason van Zyl wrote:
On 7-Jul-08, at 3:29 AM, 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
On 7-Jul-08, at 10:42 AM, Ralph Goers wrote:
Jason van Zyl wrote:
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
Jason van Zyl wrote:
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 w
On 7-Jul-08, at 10:19 AM, Ralph Goers wrote:
Jason van Zyl wrote:
On 7-Jul-08, at 3:29 AM, 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, a
Jason van Zyl wrote:
On 7-Jul-08, at 3:29 AM, 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
On 7-Jul-08, at 3:29 AM, 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
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 wa
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. H
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 t
17 matches
Mail list logo
