Thank you for your help. It continued to not find it as it started only looking
in one place for it: plugins-snapshot-local (the last of the four places it
previously looked for it). Clearly, it wasn’t going to find it there. I
eventually went into my .m2 directory and removed all references to it, and
then it found it. ☺
-ste
From: Yoav Landman [mailto:[email protected]]
Sent: Friday, March 04, 2011 6:15 PM
To: [email protected]
Subject: Re: [Artifactory-users] plugin dependency exists, but not found
The commons-io-1.3.2.pom that's on repo1 is broken: it has wrong group id
information that doesn't match its path coordinates; and so, Artifactory
shields you from caching it.
You can turn off this gate-keeping, which we don't recommend - but it's
available under the remote repository configuration: Advanced Settings/Turn off
POM Consistency Checks.
A better approach is to deploy a good version of this POM to a local
(third-party libs) repository. You can grab it from:
http://repo.jfrog.org/artifactory/third-party-releases-local/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom
I guess you started seeing this because M3 uses different versions of default
plugins that introduced this new dependency.
HTH and good to see you moving to 2.3.2 :)
Yoav
On Sat, Mar 5, 2011 at 12:49 AM,
<[email protected]<mailto:[email protected]>> wrote:
I have attached log excerpts.
I should note that I am starting my build with an empty Artifactory 2.3.2 and
an empty .m2, to cause everything to get pulled down, so that everything gets
populated (this artifactory will become our production install – our current
one runs version 1.2.5!). When I do that with maven2, it works. When I do it
with maven3, it fails on this particular artifact, which apparently is NOT
getting into my Artifactory (just the directory tree up to it). From looking at
the logs, I suspect there is something wrong with the artifact’s pom file which
maven2 apparently can cope with, but maven3 chokes on. That’s just my guess
anyway. I’ll leave it to you experts to tell me. ☺
Thank you, in advance, for your time and help. I’m reading and learning, as
fast as I can, about both Artifactory and Maven. With any luck, I won’t remain
clueless long. ☺
-ste
From: Yoav Landman [mailto:[email protected]<mailto:[email protected]>]
Sent: Friday, March 04, 2011 5:27 PM
To:
[email protected]<mailto:[email protected]>
Subject: Re: [Artifactory-users] plugin dependency exists, but not found
Hi,
Can you attach the log from your Maven 3 build that includes the Maven requests
for the unfound dependency?
Do you manage to download it from a browser by specifying the same URL?
On Fri, Mar 4, 2011 at 10:58 PM,
<[email protected]<mailto:[email protected]>> wrote:
My end-users (I’m their SysAdmin) are trying to move from Maven2 to Maven3.
A plugin that builds fine under maven2 can't find a dependency under maven3,
yet I see it cached under repo1-cache where it's always been. Maven3 only
appears to look in:
plugins-release
plugins-snapshot
plugins-release-local
plugins-snapshot-local
That it only looks there, makes sense, as I’ve read on the maven list that:
> In Maven 3, dependencies for plugins are only retrieved from
> pluginRepositories. This was not the case in Maven 2.
What I don’t understand is why the artifact isn’t found, as both the
plugins-release and plugins-snapshot virtual repositories include the
remote-repos virtual repository, and it includes the remote repository repo1.
Please forgive my newbie questions – I only started dealing with Artifactory
(2.3.2) and Maven (2.2.1 & now 3.0.2) four days ago or so. ☺
This works fine with Maven2, so I assume I need to tweak my Artifactory
configuration to make Maven3 happy, somehow …
-ste
________________________________
This message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information. If you have received it in
error, please notify the sender immediately and delete the original. Any other
use of the email by you is prohibited.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Artifactory-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Artifactory-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
