I don't think it would affect day to day usage, because we aren't changing
anything about the existing repository.
The snapshot repo could be set up as a simple file server where developers can upload new
snapshots as needed and/or automated builds are uploaded on a nightly or weekly basis.
These files would not need to be in CVS or SVN. You wouldn't need to check out a copy
of the repository locally because maven "deploy" can be configured to copy the
file to the server via ftp or through a share or one of a few other ways.
The current /maven2 repository would be only for releases. That might keep it a little
cleaner than if the two are combined. Eventually we could have the release engineering
team responsible for doing releases, and take away developer access to the releases
repository.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012652#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...