On 22 Feb 07, at 8:39 AM 22 Feb 07, Eus wrote:


Hi Ho!

Why the public repository for Maven2 (http://repo1.maven.org/ maven2/) does
not contain all jars exists in the public repository for Maven1
(http://repo1.maven.org/maven/)?
For example, in the Maven1's repo you can get maven-xdoclet- plugin-1.2.3.jar in http://repo1.maven.org/maven/xdoclet/plugins/, but you cannot get it in
the Maven2's repo in
http://repo1.maven.org/maven2/xdoclet/maven-xdoclet-plugin/ because the
latest version there is 1.2.
My hypothesis is that many developers still actively using Maven1 so that they deploy the most current version of their work to the Maven1's repo. Is that true? If it is true, then there are people (or, better, machines) whose duty is to copy and modify jars in the Maven1's repo to the Maven2's
repo, right?

Thank you very much for your explanation.

It means our conversion process is not working well enough for projects that don't have POMs. The XDoclet plugin you speak of doesn't look like it has a valid POM which makes it hard to convert. And right now if a POM is not available in conjunction with xdoclet stuff in m1, which is a mess BTW, results in it not getting converted. Maven 2.x is strict about having a POM. No POM, no place in the repository, that's how it works. So you have a couple options.

Complain to the Xdoclet people to fix their projects and provide the correct metadata, or provide us with POMs to fix the problem. We cannot be watchdogs for everything though we will in the future have better reporting for things that are wrong with artifacts submitted.

Jason.

--
View this message in context: http://www.nabble.com/Maven1%27s-repo- is-more-up-to-date-than-Maven2%27s-repo--%28missing-jars-in-Maven2% 27s-repo%29-tf3272775s177.html#a9099988
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to