There is actually a maven-one-plugin for deploying to the m1 repository. - Brett
On 1/24/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > As a workaround: > > Create a profile with the distributionManagement defined for the > second repository. Then you can run deploy a second time with the > profile specified to deploy to the second repostiory. > > -Stephen > > > On 1/24/06, Matthew Beermann <[EMAIL PROTECTED]> wrote: > > Unless I'm misreading the XSD file (which is entirely possible), it looks > > as if you can only deploy to one remote repository - that is, the > > <distributionManagement/> tag will only take one <repository/> item. This > > seems like an odd limitation to impose. > > > > We'd like to deploy all of our artifacts to TWO remote repositories: one > > in the Maven 2 format, and one in the legacy Maven 1 format. This will make > > our upgrade path vastly simpler, as there are other teams within our > > organization that consume artifacts from our repository, but won't be ready > > to upgrade to M2 for a long while yet. > > > > Is there a way to do this I'm not seeing? Surely it's something that > > someone somewhere has wanted to do before... > > > > --Matthew Beermann > > > > > > --------------------------------- > > Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more on > > new and used cars. > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > --------------------------------------------------------------------- > 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]
