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]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
