Here's a legacy M1 repo: https://maven-repository.dev.java.net/nonav/repository/
Notice the following negative attributes: - flat directory structure (now imagine 2000 projects) [DIR] javax.activation/ 10-May-2006 21:35 - [DIR] javax.faces/ 10-May-2006 21:35 - [DIR] javax.mail/ 10-May-2006 21:35 - [DIR] javax.servlet/ 10-May-2006 21:35 - [DIR] javax.servlet.jsp/ 10-May-2006 21:35 - [DIR] javax.servlet.jsp.jstl/ etc -versioning exists only inside pom/jar directories, not broken up into different directories, see here for an example (now imagine 50 releases instead of 7) https://maven-repository.dev.java.net/nonav/repository/javax.faces/jars/ That's just what I've noticed between M1 and M2 repos. There are certainly other differences as well. Personally I find the M2 repo format a lot more scalable and approachable. If you're only going to have a few projects with a handful of releases each, then there's not necessarily a strong reason to prefer M2 over M1, esp since M2 can read from M1 repos. Wayne On 5/11/06, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote:
> This was discussed a couple days ago, so search the User list > at Nabble (or your own email archive) to find the discussion. Ack, sorry. I did search, but apparently did not choose my search terms wisely... just got an old message from last Oct. :-/ > As I recall, there is no "built-in" way to deploy to multiple > repos. The Apache team has set up some kind of automatic > sync'ing to keep repos in sync, perhaps using rsync or > something similar, but you will need to set this up yourself. > > Wayne This does seem to be the case. Has anyone filed a feature request for this? I definitely do not want to synchronize my repositories. There's just one jar file that my M1 projects will need. I don't suppose there's any chance Maven 1.1 (if it is ever released) would support downloading from a M2 repository? What advantages does a M2 repository have, anyway? I assume there are some features of M2 that a legacy repository couldn't support, but does anyone know what? I guess for now I'll have to manually deploy the jar file to the old repository. Thanks, ~Daniel --------------------------------------------------------------------- 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]
