Inconsistent artifacts in Maven Central

[stug23]

I just posted the following item to the nabble Artifactory forum:

This case involves the velocity:velocity:1.5:pom which is inconsistently stored in Maven Central with respect to its proper coordinates.

http://www.nabble.com/How-to-work-around-inconsistent-artifacts-in-Maven-Central-ts19012104.html

I noted that Nexus doesn't report or fail for the same case as referenced above. When I tried this with Nexus, it "just worked". However it did proxy the inconsistent velocity artifact into the Maven Central cache.

Is the philosophy of Nexus that downloading inconsistently stored artifacts is okay? Or is just a matter of  Nexus trying to "just make things work"?

[Brian Fox]

Nexus will serve up the file if it can find it, regardless of if it's where
the pom says it should be. The indexer will complain and should create a
notice in the rss feeds for things like this. Later on we'll have
provisioning policies that can block or correct some of these issues.

-----Original Message-----
From: stug23 [mailto:pat.podenski@...]
Sent: Saturday, August 16, 2008 9:44 AM
To: nexus-user@...
Subject: [nexus-user] Inconsistent artifacts in Maven Central


I just posted the following item to the nabble Artifactory forum:

This case involves the velocity:velocity:1.5:pom which is inconsistently
stored in Maven Central with respect to its proper coordinates.

http://www.nabble.com/How-to-work-around-inconsistent-artifacts-in-Maven-Cen
tral-ts19012104.html

I noted that Nexus doesn't report or fail for the same case as referenced
above. When I tried this with Nexus, it "just worked". However it did proxy
the inconsistent velocity artifact into the Maven Central cache.

Is the philosophy of Nexus that downloading inconsistently stored artifacts
is okay? Or is just a matter of  Nexus trying to "just make things work"?
--
View this message in context:
http://www.nabble.com/Inconsistent-artifacts-in-Maven-Central-tp19012974p190
12974.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive
at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

I saw the associated thread on Artifactory-Users where this is a feature. I
take the view that even if data is non-conforming in Central, Nexus should
support it. In other words, if it works without Nexus, it should work with
Nexus. That's the default, it's not to say that we shouldn't allow the
ability to block irregular artifacts, but it should be a choice...you
shouldn't have to install something manually just to work around the RM.

--Brian

-----Original Message-----
From: Brian Fox [mailto:brianf@...]
Sent: Saturday, August 16, 2008 9:52 AM
To: nexus-user@...
Subject: RE: [nexus-user] Inconsistent artifacts in Maven Central

Nexus will serve up the file if it can find it, regardless of if it's where
the pom says it should be. The indexer will complain and should create a
notice in the rss feeds for things like this. Later on we'll have
provisioning policies that can block or correct some of these issues.

-----Original Message-----
From: stug23 [mailto:pat.podenski@...]
Sent: Saturday, August 16, 2008 9:44 AM
To: nexus-user@...
Subject: [nexus-user] Inconsistent artifacts in Maven Central


I just posted the following item to the nabble Artifactory forum:

This case involves the velocity:velocity:1.5:pom which is inconsistently
stored in Maven Central with respect to its proper coordinates.

http://www.nabble.com/How-to-work-around-inconsistent-artifacts-in-Maven-Cen
tral-ts19012104.html

I noted that Nexus doesn't report or fail for the same case as referenced
above. When I tried this with Nexus, it "just worked". However it did proxy
the inconsistent velocity artifact into the Maven Central cache.

Is the philosophy of Nexus that downloading inconsistently stored artifacts
is okay? Or is just a matter of  Nexus trying to "just make things work"?
--
View this message in context:
http://www.nabble.com/Inconsistent-artifacts-in-Maven-Central-tp19012974p190
12974.html
Sent from the Nexus Maven Repository Manager Users List mailing list archive
at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...