RE: LGPL verbiage in cvs

> BTW, you made Arno the copyright holder on JivanDOMFactory.java.  It was
> actually me that wrote it so I changed it.  If I shouldn't have
> done that, you can change it back.

Great. That was the right thing to do. Please let me know if there is
anything else for which you are the initial author (I know you've touched
code all over the place, but I don't recall which classes you specifically
created).

Thanks for applying Arno's new version of Jivan. I will try to do a complete
build and push it up to barracudamvc tonight...

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"


> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Jacob Kjome
> Sent: Sunday, February 01, 2004 2:21 AM
> To: [email protected]
> Subject: Re: [Barracuda] LGPL verbiage in cvs
>
>
> Hi Christian (and all),
>
> I added jivan-1.0rc2.jar and made all updates necessary.  I deleted the
> Barracuda_1_2_6 tag on jivan-1.0rc1.jar and moved them on the
> other files I
> added/updated which include jivan-1.0rc2.jar, version.properties,
> JivanDOMFactory.java (which I updated in a very minor way to take
> advantage
> of a new Jivan api method that I had suggested to Arno; to take an
> InputStream rather than force one to create an Apache InputSource
> and pass
> that in).
>
> BTW, you made Arno the copyright holder on JivanDOMFactory.java.  It was
> actually me that wrote it so I changed it.  If I shouldn't have
> done that,
> you can change it back.
>
> I'm not going to regenerate the jars.  I'll leave that to you
> right before
> the release is made.  Just make sure to move the tags on all jars you
> update.  Should only need to be the core jar, at least for the change I
> made.  They should all be compiled with the same VM.  Might want to do it
> with the latest 1.3.1 VM to make sure the release is binary
> compatible with
> 1.3.1.  I've seen issues where code compiled for 1.4.x has issues running
> under 1.3.1 but never the other way around.  XMLC was compiled with
> JDK1.3.1_10.
>
> Oh, you should also probably copy barracuda jars into BarracudaDiscRack
> *after* the Barracuda release is made, just to make sure the
> actually 1.2.6
> jars are in there.  Then make that release.
>
> later,
>
> Jake
>
> At 11:35 PM 1/31/2004 -0500, you wrote:
> >Ok folks, we're just about ready to roll the new 1.2.6 release...
> >-----------------
> ><p><b>csc_013104_2</b> - Changed all the license verbiage to
> LGPL. Rebuilt
> >all the jars. Got BarracudaDiscRack upgraded to the latest
> version. Started
> >working on updating all the docs for the new 1.2.6 release. At
> this point,
> >we are very close to being ready to roll a build (still waiting for a new
> >Jivan binary licensed under LGPL).
> >-----------------
> >
> >Please note that I when I went through updating all the source
> files to use
> >the LGPL verbiage, I have attempted to correctly identify the copyright
> >holder (the original author) for all the files. In most cases this is me,
> >but there are obviously a number of classes that other people
> have written.
> >If you were the original author for a class, please check the
> tree to make
> >sure that I correctly acknowledge you as copyright holder...in
> the process
> >of doing massive search and replace, its possible I may have
> misidentified
> >the original owner. Note that wherever possible, I have tried to
> retain the
> >javadoc contributor comments, which identify all major contributors, not
> >just the original copyright owner.
> >
> >Should be ready sometime tomorrow to finish everything up...
> >
> >Christian
> >----------------------------------------------
> >Christian Cryder
> >Internet Architect, ATMReports.com
> >Project Chair, BarracudaMVC - http://barracudamvc.org
> >----------------------------------------------
> >"Coffee? I could quit anytime, just not today"
> >
> >_______________________________________________
> >Barracuda mailing list
> >[email protected]
> >http://barracudamvc.org/lists/listinfo/barracuda
>
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda