« Return to Thread: problem with velocity:velocity:1.5

Re: problem with velocity:velocity:1.5

by Clifton :: Rate this Message:

Is there a process where POM corruption like this can be reported/fixed on repo1? It makes me a little nervous to see these issues in the middle of crunch time where we really don't have the availability to add a cmd line option, restart, remove the option and restart. It's also a bit much to fight with recoding someone else's pom which seems to imply testing cycles to make sure transitive dependencies are correctly resolved and so on. Has there been any talk of an auto-fix for corrupt poms using a best guess algorithm? Would that open the door to many other dangers?

Yoav Landman wrote:

You have 2 options:
Either fix the POM and deploy it into a local repository (preferably
dedicated to third party libraries), where it will be found before the
corrupt POM from repo1. You can also add the POM to the excludes
pattern of the remote repo1 repository to make sure it is never
downloaded.
Or, run Artifactory with
-Dartifactory.maven.suppressPomConsistencyChecks=true to suppress this
consistency checks and have the broken POM silently installed (not
recommended, and if you choose to go this way it is best to turn the
checks back on and restart Artifactory).

HTH,

Yoav

On Jan 21, 2008 10:14 PM, TomHuybrechts <tom.huybrechts@gmail.com> wrote:
>
> Hi all,
>
> I just installed artifactory and am attempting to do my normal builds from a
> clean repository.
> These are failing because of problems with Velocity. Apparently one of my
> Maven plugins depends on velocity:velocity1.5. Unfortunately, this
> artifact's POM in central is faulty: it has a different groupId than its
> actual location.
>
> This means that artifactory does not download the POM although it does
> download the jar. Maven will complain, but continue. But at runtime
> everything falls apart because velocity's transitive dependencies are not
> available.
>
> Is there anything I can do about this ? Updating the artifact that has the
> dependency is not an option.
> The problem can be reproduced on the demo install:
> http://www.jfrog.org/artifactory/repo/velocity/velocity/1.5/velocity-1.5.pom
>
> Tom
> --
> View this message in context: http://www.nabble.com/problem-with-velocity%3Avelocity%3A1.5-tp15005415p15005415.html
> Sent from the Artifactory-Users mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Artifactory-users mailing list
> Artifactory-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Artifactory-users mailing list
Artifactory-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Cliff
http://codeforfun.wordpress.com

« Return to Thread: problem with velocity:velocity:1.5