you are talking about a maven 1 plugin. M1 plugins don't work with m2,
that's why is not in the maven2 repository

On 2/22/07, Eus <[EMAIL PROTECTED]> 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.
--
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]




--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                            -- The Princess Bride

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

Reply via email to