You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Christian T Trimble <ch...@meltmedia.com> on 2011/05/11 18:13:16 UTC

[jci] preparing for jci 1.1 release

Torsten,

  I have moved my code base from my old version of jci 1.1 to the trunk and everything looks good.  I did have trouble building the trunk, because the fam module is not included in the module list.  I have opened JCI-66 to address that.  I will take a look at 1.0/1.1 compatibility later this week.

-Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Jörg Schaible <jo...@scalaris.com>.
Torsten Curdt wrote:

> Thanks for checking, Christian.
> 
>> I have moved my code base from my old version of jci 1.1 to the trunk and
>> everything looks good.  I did have trouble building the trunk, because
>> the fam module is not included in the module list.  I have opened JCI-66
>> to address that.  I will take a look at 1.0/1.1 compatibility later this
>> week.
> 
> Just wondering - do you require 1.4 compatibility? I would like to
> move to 1.5. Not sure this is the right time for that though.

+ 1.5 :)

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Christian T Trimble <ch...@meltmedia.com>.
Torsten,

  Can improvements to the current code base be rescheduled to 1.2?  This project has
been without a release for some time and those projects that depend on JCI 1.1
need a release of the current functionality for their own releases.

  If that is not an option, can we at least get SNAPSHOTs out on a Maven repository?  That would
allow dependent projects to build while this work is being finished.

-Christian

On May 13, 2011, at 4:01 AM, Torsten Curdt wrote:

>>> It is - that is the jsr199 compiler that needs to be finished.
>>> It would be great to finish that and not look back.
>>> Although I made some progress I don't think I have the time.
>> 
>> AFAICT, JSR199 also requires Java 1.6?
> 
> Indeed. But I am quite positive very few people (if any) use the javac
> hack anyway.
> 
>> I'd overlooked the in-memory part - is there any point in releasing it
>> with javac support for files only?
>> I.e. just dropping the in-memory support for javac until jsr199 is implemented.
> 
> Na - don't think that would really work. You could try to check the
> store implementation and throw an exception ...but in the end it is an
> interface and you can never know what the impl is doing. Which is why
> I think 2.0 is the only real option. That said releasing 2.0 without
> the JSR199 in place feels a little silly.
> 
> cheers,
> Torsten
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Torsten Curdt <tc...@vafer.org>.
>> It is - that is the jsr199 compiler that needs to be finished.
>> It would be great to finish that and not look back.
>> Although I made some progress I don't think I have the time.
>
> AFAICT, JSR199 also requires Java 1.6?

Indeed. But I am quite positive very few people (if any) use the javac
hack anyway.

> I'd overlooked the in-memory part - is there any point in releasing it
> with javac support for files only?
> I.e. just dropping the in-memory support for javac until jsr199 is implemented.

Na - don't think that would really work. You could try to check the
store implementation and throw an exception ...but in the end it is an
interface and you can never know what the impl is doing. Which is why
I think 2.0 is the only real option. That said releasing 2.0 without
the JSR199 in place feels a little silly.

cheers,
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by sebb <se...@gmail.com>.
On 13 May 2011 11:09, Torsten Curdt <tc...@vafer.org> wrote:
>>> We really need to drop the javac support. It was a hack. But releasing
>>> it as is will be a bit of a pain as it depends on an old jvm to just
>>> pass the tests.
>>
>> Is it really not possible to implement javac support with a more recent JVM?
>
> It is - that is the jsr199 compiler that needs to be finished.
> It would be great to finish that and not look back.
> Although I made some progress I don't think I have the time.

AFAICT, JSR199 also requires Java 1.6?

>> Doesn't Ant have code to invoke the javac compiler?
>
> The usual command line calling of javac that other tools did before is
> not really an option for jci. There is no way of doing in-memory
> compilation.

I'd overlooked the in-memory part - is there any point in releasing it
with javac support for files only?
I.e. just dropping the in-memory support for javac until jsr199 is implemented.

> Except for the javac hack in jci I wish hadn't released
> :)
>
> cheers,
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Torsten Curdt <tc...@vafer.org>.
>> We really need to drop the javac support. It was a hack. But releasing
>> it as is will be a bit of a pain as it depends on an old jvm to just
>> pass the tests.
>
> Is it really not possible to implement javac support with a more recent JVM?

It is - that is the jsr199 compiler that needs to be finished.
It would be great to finish that and not look back.
Although I made some progress I don't think I have the time.

> Doesn't Ant have code to invoke the javac compiler?

The usual command line calling of javac that other tools did before is
not really an option for jci. There is no way of doing in-memory
compilation. Except for the javac hack in jci I wish hadn't released
:)

cheers,
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by sebb <se...@gmail.com>.
On 13 May 2011 08:47, Torsten Curdt <tc...@vafer.org> wrote:
> Hm ... going through the issues.
>
> We really need to drop the javac support. It was a hack. But releasing
> it as is will be a bit of a pain as it depends on an old jvm to just
> pass the tests.

Is it really not possible to implement javac support with a more recent JVM?
Doesn't Ant have code to invoke the javac compiler?
I've not looked at the code, so I've no idea what it might involve.

> Maybe we should shoot for a 2.0 after all and clean things up. *sigh*
>
> On Fri, May 13, 2011 at 09:06, Torsten Curdt <tc...@vafer.org> wrote:
>> Thanks for checking, Christian.
>>
>>>  I have moved my code base from my old version of jci 1.1 to the trunk and everything looks good.  I did have trouble building the trunk, because the fam module is not included in the module list.  I have opened JCI-66 to address that.  I will take a look at 1.0/1.1 compatibility later this week.
>>
>> Just wondering - do you require 1.4 compatibility? I would like to
>> move to 1.5. Not sure this is the right time for that though.
>>
>> cheers,
>> Torsten
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Torsten Curdt <tc...@vafer.org>.
Hm ... going through the issues.

We really need to drop the javac support. It was a hack. But releasing
it as is will be a bit of a pain as it depends on an old jvm to just
pass the tests.
Maybe we should shoot for a 2.0 after all and clean things up. *sigh*

On Fri, May 13, 2011 at 09:06, Torsten Curdt <tc...@vafer.org> wrote:
> Thanks for checking, Christian.
>
>>  I have moved my code base from my old version of jci 1.1 to the trunk and everything looks good.  I did have trouble building the trunk, because the fam module is not included in the module list.  I have opened JCI-66 to address that.  I will take a look at 1.0/1.1 compatibility later this week.
>
> Just wondering - do you require 1.4 compatibility? I would like to
> move to 1.5. Not sure this is the right time for that though.
>
> cheers,
> Torsten
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Christian T Trimble <ch...@meltmedia.com>.
Torsten,

  I do not need 1.4 compatibility.

-Christian

On May 13, 2011, at 12:06 AM, Torsten Curdt wrote:

> Thanks for checking, Christian.
> 
>>  I have moved my code base from my old version of jci 1.1 to the trunk and everything looks good.  I did have trouble building the trunk, because the fam module is not included in the module list.  I have opened JCI-66 to address that.  I will take a look at 1.0/1.1 compatibility later this week.
> 
> Just wondering - do you require 1.4 compatibility? I would like to
> move to 1.5. Not sure this is the right time for that though.
> 
> cheers,
> Torsten
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Torsten Curdt <tc...@vafer.org>.
> I do not see why this entire project would need to go to 1.5 or 1.6, unless Generics are
> added to the core interface.  The maven.compile.target property could be set on the different
> modules, so that the core interface is compiled for 1.4.2 and the JSR199 code is compiled for 1.6.

The java version of the core is less of an issue.

But I would like to drop javac support - yesterday. Which requires a
JCI 2.0. But a JCI 2.0 without javac and JSR199 not finished feels a
bit silly.

I might be biased. Not sure how other people feel about this.

cheers,
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Christian T Trimble <ch...@meltmedia.com>.
I do not see why this entire project would need to go to 1.5 or 1.6, unless Generics are
added to the core interface.  The maven.compile.target property could be set on the different
modules, so that the core interface is compiled for 1.4.2 and the JSR199 code is compiled for 1.6.

On May 17, 2011, at 10:37 AM, Gary Gregory wrote:

> On May 17, 2011, at 12:17, "Jörg Schaible" <jo...@scalaris.com> wrote:
> 
>> Torsten Curdt wrote:
>> 
>>> Thanks for checking, Christian.
>>> 
>>>> I have moved my code base from my old version of jci 1.1 to the trunk and
>>>> everything looks good.  I did have trouble building the trunk, because
>>>> the fam module is not included in the module list.  I have opened JCI-66
>>>> to address that.  I will take a look at 1.0/1.1 compatibility later this
>>>> week.
>>> 
>>> Just wondering - do you require 1.4 compatibility? I would like to
>>> move to 1.5. Not sure this is the right time for that though.
>> 
>> + 1.5 :)
> 
> Make it 1.6! ;)
> 
> Gary
>> 
>> - Jörg
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Gary Gregory <ga...@gmail.com>.
On May 17, 2011, at 12:17, "Jörg Schaible" <jo...@scalaris.com> wrote:

> Torsten Curdt wrote:
>
>> Thanks for checking, Christian.
>>
>>> I have moved my code base from my old version of jci 1.1 to the trunk and
>>> everything looks good.  I did have trouble building the trunk, because
>>> the fam module is not included in the module list.  I have opened JCI-66
>>> to address that.  I will take a look at 1.0/1.1 compatibility later this
>>> week.
>>
>> Just wondering - do you require 1.4 compatibility? I would like to
>> move to 1.5. Not sure this is the right time for that though.
>
> + 1.5 :)

Make it 1.6! ;)

Gary
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Re: [jci] preparing for jci 1.1 release

Posted by Torsten Curdt <tc...@vafer.org>.
Thanks for checking, Christian.

>  I have moved my code base from my old version of jci 1.1 to the trunk and everything looks good.  I did have trouble building the trunk, because the fam module is not included in the module list.  I have opened JCI-66 to address that.  I will take a look at 1.0/1.1 compatibility later this week.

Just wondering - do you require 1.4 compatibility? I would like to
move to 1.5. Not sure this is the right time for that though.

cheers,
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org