Sender: |
|
Date: |
Wed, 21 Mar 2007 10:58:17 -0400 |
MIME-version: |
1.0 (Apple Message framework v752.3) |
Reply-To: |
|
Content-type: |
text/plain; charset=ISO-8859-1; delsp=yes; format=flowed |
Subject: |
|
From: |
|
In-Reply-To: |
|
Content-Transfer-Encoding: |
8bit |
Comments: |
|
Parts/Attachments: |
|
|
Yes! I in fact I was thinking of ending my previous email message
with "Alberto, I'm looking at _you_" :-)
There are a couple of other folks I've talked with who have
extensions to ECJ I'd like to see on the web page.
There are three ways we can do this:
- Add the code to the ECJ base. We want to keep ECJ consistent, so
the code must:
- compile and run in Java 1.3 (at present)
- have no external dependencies in order to compile (like Teambots
had)
- compile to the same arrangement that ECJ has in general (no jar
file requirements, etc.)
- conform to ECJ's, erm, unusual approach to doing things (setup,
prototypes, parameter database,
- Add the project to the contrib directory in CVS and use it as the
project's primary repository. You can have whatever format you'd
like there, it'd be your area.
- Have *me* put occasional project snapshots into the contrib
section of the CVS repository and out on the main web page.
There's one more option:
- Host the module elsewhere, but give me occasional snapshots. I'd
put a link to your project on the website -- that's the main way
people would get your modules from the ECJ website -- but I'd also
store the snapshots here in case your link goes down.
That goes for everyone else too. I'd love to see the contrib section
used more widely by large external ECJ modules.
Sean
On Mar 21, 2007, at 4:11 AM, Alberto Cuesta wrote:
> Sean Luke escribió:
>> I've put the current CVS repository out as ECJ 16. It's been
>> almost a year!
>>
>> I'll make an official announcement in a bit, when I get MASON out
>> the door too. In the meantime, if you have something like you'd
>> like to put on contrib (for the time being), let me know and I'll
>> stick it on the website. I'd like some pointers to modules people
>> have done extending ECJ in one way or another.
>>
>> Sean
> Hi Sean, congratulations for the new version!
>
> Maybe you remember I was working in an island-over-P2P version for
> ECJ. It works right now although it could benefit of some testing.
> I'm working right now to develop also a master/slave version of ECJ
> over the same platform. Do you think I could use the ECJ CVS for
> these projects?
>
> Alberto Cuesta
|
|
|