Re: [Clirr-devel] project status?

[<lak...@t-...>]

Hi Brian,

good to hear a success story from the commercial world, and great that
you even started digging in the code. Contributions to Clirr are really,
really welcome, as all current commiters are quite short of time.

In general, you can contribute your changes in the sourceforge tracker.
Open a ticket in the sourceforge tracker for feature requests and attach
your changes to that ticket. I think this requires a sourceforge
account. If you don't have one you can also simply send your patch to
the devel list, but tracker entries are easier to manage than email.

Please note that I am about to change the license from LGPL to ASL2 (not
sure if that's already partially commited in the trunk), so please make
your contribution available under the ASL2 license.

The project does have a maintainer (me), but unfortunately my spare time
is rather limited lately (small kid, demanding day job, other open
source projects). However I hope to be able to spare some cycles during
the holiday season, so you probably will see some activity in CVS, and
maybe a beta release for the new byte code backend (ASM instead of
BCEL).

Cheers, and thanks in advance for your contribution,
Lars

-----Original Message-----
Date: Wed, 29 Nov 2006 23:10:53 +0100
Subject: [Clirr-devel] project status?
From: "Elliott, Brian"
To: <cli...@li...>

     Hello,
  
 We have started using Clirr at Orbitz with some success.  We are using
a snapshot of the trunk and ended up making a small change that adds
support for class files compiled by rmic.  How do we contribute this
back?  
  
 Also, does this project have any active maintainers?  I don’t think
there’s been any commits for 4 months and was wondering when the next
real version is scheduled for release.
  
 Thanks,
 Brian