>3) Moreover, you can define more than one repository with the property >maven.repo.remote. For instance, a dev repository and a production one. > > This is probably the best way to handle it. Split your repository into a "current" and "archive". Don't promote builds that require the archive (unless they are old builds).
- Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
