The license change was at rev 1384 and the 3.2.3 release was at 1235 so we
may want to also grab 1383 and review the change history in between.  It
looks like there are quite a few changes in there so some of them may be
worth having.

Chris

On Sun, Apr 13, 2008 at 2:19 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:

> Ok, so I won't bother trying to find the exact point at which the license
> changed and take the tag for the 3.2.3.
>
> I'll just create a project at Codehaus unless someone wants to put it
> somewhere else.
>
>
> On 13-Apr-08, at 1:11 PM, Chris Custine wrote:
>
> > I have been irritated about this and thinking the same thing for the
> > past
> > week, so if a fork occurs I am willing to help maintain it and tweak it.
> > Honestly there isn't too much wrong with the current 3.2.3 version that
> > I am
> > aware of, but I think we can improve on it none the less.
> >
> > Thanks,
> > Chris
> >
> > On Sun, Apr 13, 2008 at 12:26 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >
> >
> > > On 13-Apr-08, at 10:34 AM, Alan D. Cabrera wrote:
> > >
> > >
> > > > On Apr 13, 2008, at 7:20 AM, Jason van Zyl wrote:
> > > >
> > > > Hi,
> > > >
> > > > >
> > > > > I have contact Leif of JSW but have yet to get a response about
> > > > > the
> > > > > license change.
> > > > >
> > > > > Project that start using a commercially liberal license and then
> > > > > switching long into the life of a project is wrong. If you want to
> > > > > do the
> > > > > GPL/commercial thing then say so from the start. I have nothing
> > > > > wrong with
> > > > > this model, but for libraries and tools using a commercially
> > > > > liberal license
> > > > > is the best way to get community adoption and then to flip the
> > > > > license I
> > > > > find a little unsavory.
> > > > >
> > > > > Anyone interested in forking it and maintaining the version that
> > > > > was
> > > > > not GPL?
> > > > >
> > > > >
> > > > I agree.  That's pretty bad.
> > > >
> > > > I don't have a lot of time but am wiling to help where I can.  I am
> > > > not
> > > > familiar with building C artifacts with Maven but am dying to learn.
> > > >
> > > >
> > > >  The NAR plugin will easily do it, so it would be interesting from a
> > > build
> > > perspective but we could continue to work on it. I'd hire a C
> > > developer to
> > > work on it before I would support a project that does the BSDish ->
> > > GPL
> > > switch-a-roo years into a project.
> > >
> > >
> > >  Regards,
> > > > Alan
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >  Thanks,
> > >
> > > Jason
> > >
> > > ----------------------------------------------------------
> > > Jason van Zyl
> > > Founder,  Apache Maven
> > > jason at sonatype dot com
> > > ----------------------------------------------------------
> > >
> > > 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: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> the course of true love never did run smooth ...
>
> -- Shakespeare
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to