"Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote on 20/07/2005 06:44:49 PM:
> > On Jul 19, 2005, at 9:56 PM, [EMAIL PROTECTED] wrote: > > > "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote on 12/07/2005 > > 10:57:34 PM: > > > > > >> > >> On Jul 11, 2005, at 11:07 PM, [EMAIL PROTECTED] wrote: > >> > >>> > >>> > >>> It appears we have already been building defacto releases of > >>> external > >>> libraries, e.g. the cglib library in our repo: > >>> http://cvs.apache.org/repository/cglib/jars/ > >>> > >> > >> You're right - there is a problem we have to deal with, but I'd > >> rather see us try another approach to make things very clear and > >> accountable. > >> > >> For any code that we must do this to we could adopt a strategery : > >> > >> 1) Make a copy in Apache SVN. This code must be appropriately > >> licensed (the Apache License) and there should be a very clear NOTICE > >> about the source, what we're doing, that it's not a fork, etc, > >> etc.... > >> > >> 2) Produce a jar : > >> > >> geronimo-private-cglib-20050711.jar > >> > >> 3) put that in > >> > >> geronimo/jars > >> > >> So it's very clear that it's not a release by CGLib, but rather code > >> from us, by us, from our repo. > >> > > > > Are planning on formalising the privately built jars using the above > > strategy proposed by Geir for M4 or would our time be better spent > > starting in M5? > > Well, someone is *already* doing it, right? The difference is that > I'm suggesting we put in our SVN and change the name of the jar... I don't think any replied to your suggestion before, so I wanted to get people to indicate whether they agree with your suggestion so there is no argument about what we are doing before we release. +1 from me for putting in SVN and changing the name of the jar. John
