Hi Nicolas, > I've got some difficulties managing our internal repository : as > mutliple users can update it, some artifacts are deployed on multiple > locations with != groupId. for example, java activation framework was > deployed as jaf/jar.jar, sun/activation.jar, and is also on ibiblio as > activation/activation.jar
Due to license restrictions, all sun libraries have been removed from public repositories: http://www.mail-archive.com/[email protected]/msg22097.html Maybe in the next future, things will be going to change... http://today.java.net/pub/n/2486 > It would be great for maven to include a "deprecation" mecanism for > repository download. Adding (for example) a file > artifactId-version.deprecated in the repo containing the alternative > <dependency> may be a way for maven to display a warning when > downloading dependency (or optionnaly auto-redirecting to alternative > location). > Personally, I think you have some good ideas but it pains me to have to point out a few things: 1) For me, a repository (public or private) should be updated by a release manager or a defined nightly build. Thus, developers can't update it. 2) Maven is a project management tool and not a repository management tool. If a developer needs to create their own libraries, let's have a look: http://maven-proxy.codehaus.org/ 3) Moreover, you can define more than one repository with the property maven.repo.remote. For instance, a dev repository and a production one. Cheers, Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
