On Thu, Jul 28, 2011 at 9:10 AM, Mark Struberg <strub...@yahoo.de> wrote: > Benson, you are wrong. > The answer to this question is really not clear and depends on a much more > then just the pure amount of code. There are lots of discussions around that > lately on legal and we have lots of detailed if/whens. If we have the > history, then we can do the check. Gladly github provides those. > > Also there is still the option to fork it over to apache-extras and fix it > there.
Mark, It seems to me that the net of your paragraph is to support my argument. If the committers slapped an AL dual license on Aether today, we could not just grab that code, with no further discussion, examination, and clearance, and fork it back into Apache. I spend a lot of time in the incubator, and the IP clearance policies have been hashed on this subject very recently. A podling I'm trying to launch has been told, in no uncertain terms, more or less what I wrote, by the lead legal advisor. Sure, if some of the code of some version of AEther was at ASF originally, that code could be teased out and brought back. But that's very different from 'oh, a dual license, we can grab it instantly.' Want to send some thread references? --benson > > LieGrue, > strub > > --- On Thu, 7/28/11, Benson Margulies <bimargul...@gmail.com> wrote: > >> From: Benson Margulies <bimargul...@gmail.com> >> Subject: Re: Apache Maven distribution with fixes >> To: "Maven Developers List" <dev@maven.apache.org> >> Date: Thursday, July 28, 2011, 1:06 PM >> Mark, >> >> No we cannot fork back. It is too large of a body of code >> to absorb >> without a grant, AL or no AL. >> >> I'm always happy to be proved stupid by consultation with >> legal. Until >> then, however, the policy seems perfectly clear to me. Only >> small >> amounts of code can be absorbed without a grant. >> >> --benson >> >> >> On Thu, Jul 28, 2011 at 8:52 AM, Mark Struberg <strub...@yahoo.de> >> wrote: >> > Humm, guess there are only 3 options left in this >> case >> > >> > >> > 1.) We wait 7 weeks or whatever time it takes (most >> probably it _will_ take more) >> > >> > 2.) You ship an ALv2 licensed version of Aether and >> Sisu which we can incorporate into an upcoming maven-3.0.4. >> > >> > 3.) We fork the last ALv2 licensed Aether version back >> to the Maven project and fix the bugs ourself. >> > >> > LieGrue, >> > strub >> > >> > --- On Thu, 7/28/11, Jason van Zyl <ja...@sonatype.com> >> wrote: >> > >> >> From: Jason van Zyl <ja...@sonatype.com> >> >> Subject: Re: Apache Maven distribution with fixes >> >> To: "Maven Developers List" <dev@maven.apache.org> >> >> Date: Thursday, July 28, 2011, 12:32 PM >> >> On Jul 28, 2011, at 8:25 AM, Mark >> >> Struberg wrote: >> >> >> >> > mom jason. >> >> > >> >> > Before we ship 3.0.4 I'd like to fix the SCM >> URL >> >> postfix problem which exists in lots of DSCMs. >> Will do this >> >> in the next week. >> >> > >> >> >> >> You probably have 6-7 weeks before an official >> 3.0.4 >> >> release would be made so you have plenty of time. >> >> >> >> If you are going to wait for Aether and Sisu to >> be >> >> provisioned at Eclipse then the total time for >> both of those >> >> to pass into that state is about 7 weeks. The >> build I >> >> proposed could not be an official release until >> such a time >> >> because there are fixes which rely on Sisu and >> Aether which >> >> are important for users. >> >> >> >> > LieGrue, >> >> > strub >> >> > >> >> > >> >> > --- On Thu, 7/28/11, Jason van Zyl <ja...@sonatype.com> >> >> wrote: >> >> > >> >> >> From: Jason van Zyl <ja...@sonatype.com> >> >> >> Subject: Re: Apache Maven distribution >> with fixes >> >> >> To: "Maven Developers List" <dev@maven.apache.org> >> >> >> Date: Thursday, July 28, 2011, 11:41 AM >> >> >> I'll assume that this is fine and no >> >> >> one objects. I'll announce this on the >> user list >> >> later >> >> >> today. >> >> >> >> >> >> On Jul 27, 2011, at 10:48 AM, Jason van >> Zyl >> >> wrote: >> >> >> >> >> >>> Maven PMC, >> >> >>> >> >> >>> Benjamin and I would like to make a >> >> distribution >> >> >> available that addresses several issues >> with the >> >> Apache >> >> >> Maven 3.0.3 release. We have pushed back >> all >> >> bugfixes that >> >> >> do not involve Eclipse Aether[a] and >> Eclipse >> >> Sisu[b] as >> >> >> their incorporation into the mainline and >> an >> >> official >> >> >> release is your decision. >> >> >>> >> >> >>> We haven't pushed any individual >> artifacts to >> >> Maven >> >> >> Central as part of creating the >> distribution, we >> >> have only >> >> >> created the distribution itself. If there >> is >> >> anything you >> >> >> want changed let us know and we'll change >> it, but >> >> we wanted >> >> >> to make these fixes available in a build >> for users >> >> who are >> >> >> having problems. We're not trying to >> represent it >> >> as >> >> >> anything other then a distribution that >> >> incorporates fixes >> >> >> users need. >> >> >>> >> >> >>> The build is available here: >> >> >>> >> >> >>> http://people.apache.org/~jvanzyl >> >> >>> >> >> >>> ------------------------------------ >> >> >>> Summary of the issues >> >> >>> ------------------------------------ >> >> >>> >> >> >>> Fixes pushed back to the ASF: >> >> >>> >> >> >>> [MNG-5064][1] mvn -nsu >> (--no-snapshot-updates) >> >> should >> >> >> not download snapshots (and break local >> builds) >> >> >>> [MNG-5131][2] Wrong encoding for >> encrypted >> >> passwords >> >> >>> [MNG-5113][3] NullPointerException on >> javadoc >> >> site >> >> >> generation >> >> >>> [MNG-5137][4] Reactor resolution does >> not work >> >> for >> >> >> forked multi module builds >> >> >>> [MNG-5096][5] <exclusion> on >> >> <dependency> >> >> >> with <type>test-jar</type> >> doesn't >> >> work in maven >> >> >> 3 >> >> >>> [MNG-5135][6] Regression: in some >> cases >> >> aggregator >> >> >> mojo is unable to resolve dependencies >> with >> >> custom >> >> >> packaging >> >> >>> >> >> >>> Fixes not pushed back to the ASF as >> these are >> >> >> dependent on fixes in Eclipse Aether and >> Eclipse >> >> Sisu: >> >> >>> >> >> >>> [MNG-5042][7] Regression: >> CloningClassLoader >> >> causes >> >> >> StackOverflowError in groovy >> >> >>> [MNG-5056][8] Test dependencies get >> packaged >> >> into WAR >> >> >> file. >> >> >>> [MNG-5084][9] Resolver for plugins >> failing >> >> >>> [MNG-5087][10] Maven 3 dependency >> resolution >> >> fails >> >> >> until maven-metadata-local.xml files >> (created by >> >> >> maven-invoker-plugin) are deleted >> >> >>> [MNG-5125] [11]Regression: mvn 3.0.3 >> is >> >> extreemly slow >> >> >> with a large number of dependencies >> >> >>> [MNG-5138][12] Dependency conflicts >> are >> >> extremely >> >> >> opaque >> >> >>> >> >> >>> [1]: http://jira.codehaus.org/browse/MNG-5064 >> >> >>> [2]: http://jira.codehaus.org/browse/MNG-5131 >> >> >>> [3]: http://jira.codehaus.org/browse/MNG-5113 >> >> >>> [4]: http://jira.codehaus.org/browse/MNG-5137 >> >> >>> [5]: http://jira.codehaus.org/browse/MNG-5096 >> >> >>> [6]: http://jira.codehaus.org/browse/MNG-5135 >> >> >>> >> >> >>> [7]: http://jira.codehaus.org/browse/MNG-5042 >> >> >>> [8]: http://jira.codehaus.org/browse/MNG-5056 >> >> >>> [9]: http://jira.codehaus.org/browse/MNG-5084 >> >> >>> [10]: http://jira.codehaus.org/browse/MNG-5087 >> >> >>> [11]: http://jira.codehaus.org/browse/MNG-5125 >> >> >>> [12]: http://jira.codehaus.org/browse/MNG-5138 >> >> >>> >> >> >>> [a]: http://eclipse.org/proposals/technology.aether/ >> >> >>> [b]: http://eclipse.org/proposals/technology.sisu/ >> >> >>> >> >> >>> Thanks, >> >> >>> >> >> >>> Jason >> >> >>> >> >> >>> >> >> >> >> >> >> ---------------------------------------------------------- >> >> >>> Jason van Zyl >> >> >>> Eclipse Board Member >> >> >>> Founder, Apache Maven >> >> >>> http://twitter.com/jvanzyl >> >> >>> >> >> >> >> >> >> --------------------------------------------------------- >> >> >>> >> >> >>> If I find ten thousand ways something >> won't >> >> work, I >> >> >> haven't failed. I am not discouraged, >> >> >>> because every wrong attempt discarded >> is just >> >> one more >> >> >> step forward. >> >> >>> >> >> >>> -- Thomas Edison >> >> >>> >> >> >>> >> >> >>> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> Jason >> >> >> >> >> >> >> >> >> ---------------------------------------------------------- >> >> >> Jason van Zyl >> >> >> Founder, Apache Maven >> >> >> http://twitter.com/jvanzyl >> >> >> >> >> >> --------------------------------------------------------- >> >> >> >> >> >> Our achievements speak for themselves. >> What we >> >> have to keep >> >> >> track >> >> >> of are our failures, discouragements and >> doubts. >> >> We tend to >> >> >> forget >> >> >> the past difficulties, the many false >> starts, and >> >> the >> >> >> painful >> >> >> groping. We see our past achievements as >> the end >> >> result of >> >> >> a >> >> >> clean forward thrust, and our present >> difficulties >> >> as >> >> >> signs of decline and decay. >> >> >> >> >> >> -- Eric Hoffer, Reflections on the Human >> >> Condition >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> > >> >> >> --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> >> > For additional commands, e-mail: dev-h...@maven.apache.org >> >> > >> >> >> >> Thanks, >> >> >> >> Jason >> >> >> >> >> ---------------------------------------------------------- >> >> Jason van Zyl >> >> Founder, Apache Maven >> >> http://twitter.com/jvanzyl >> >> >> --------------------------------------------------------- >> >> >> >> People develop abstractions by generalizing from >> concrete >> >> examples. >> >> Every attempt to determine the correct abstraction >> on paper >> >> without >> >> actually developing a running system is doomed to >> failure. >> >> No one >> >> is that smart. A framework is a resuable design, >> so you >> >> develop it by >> >> looking at the things it is supposed to be a >> design of. The >> >> more examples >> >> you look at, the more general your framework will >> be. >> >> >> >> -- Ralph Johnson & Don Roberts, Patterns >> for >> >> Evolving Frameworks >> >> >> >> >> >> >> >> >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> > For additional commands, e-mail: dev-h...@maven.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
