I meant deploying to m2 repo so everything in the m1 gets autogenerated. - sync'ed repos should go to a temp folder and converted to m2 repo - each upload bundle should be converted to m2 and deployed in the m2 repo, and not i the m1 one
then all the m2 repo would be converted to m1. This has sense for you? I'm not sure if now it's possible but seems that at some point this is the way to go. On 5/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Carlos Sanchez wrote: > > >At some point we definitely want to make changes to maven2 repo and > >automatically generate the maven1 as there's much more information in > >m2 poms wich can't be captured in m1 poms. > > > >For achieving that we need: > >- tool to convert m2 repo to m1 > > > > > at the moment we are doing it all in the other direction. m1 doesn't > care about the poms, so we just put the m2 poms in the m1 layout > > >- tool to convert m1 upload requests poms to m2 poms, so people keep > >uploading m1 bundles that actually will go to m2 repo > > > > > already happening > > >- process the sync'ed repos to convert m1 poms to m2 > > > > > already happening > > >I don't know the status of all this so maybe it's too soon to try it, > >in that case I will keep uploading bundles to m1 and solving pom > >related issues in m1 repo when possible. > > > > > Yep, that's the approach. m2 poms can go in directly too, and in fact > would be better. > > >does the m1 to m2 convert tool override existing m2 poms? > > > > > > > yes, which is a problem. Bug already filed. > > - Brett > > > --------------------------------------------------------------------- > 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]
