a) should be fine as in the m1 repo there are no snapshots now, they were deleted before and copied on demand.
A problem is that we'll be publishing things like log4j 1.1-dev, probably we should relocate this to log4j-1.1-2005.... to keep it consistent. m1 would still get the 1.1-dev but m2 will get the snapshot and a warning if somebody tries to use it. On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Heh, that's interesting. I'll put a rule in for that one specifically. > > Another issue just discovered: we let all kinds of crap to sync into the > m1 repo, including development builds. We don't convert them to the > maven 2.x repo. That now breaks builds that depended on the snapshots. > > Do we: > a) do a one time sync of old snapshots, but no new ones? > b) copy them on demand, case by case? > c) do nothing? > > Currently leaning to (a). > > - Brett > > Carlos Sanchez wrote: > > I believe that's caused by the rewrite rules, they don't work well > > with dirs but they do with artifacts > > > > On 1/9/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > >> Weird, it was screwed a couple of minutes ago (the > >> http://www.ibiblio.org/maven was redirecting to the > >> http://www.ibiblio.org/maven/public/html/maven, which in turn didn't have > >> any groupId dir)... > >> > >> -- Felipe > >> > >> > >> > >> > >> On 1/9/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > >>> http://www.ibiblio.org/maven/ > >>> > >> > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
