You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Emmanuel Bourg <eb...@apache.org> on 2013/10/08 11:28:20 UTC
[jci] New release?
Hi all,
I'd like to push out a new release of [jci]. Despite the remaining
issues it's still an improvement compared to the previous release.
Any objection?
Emmanuel Bourg
Re: [jci] New release?
Posted by Benedikt Ritter <be...@gmail.com>.
Send from my mobile device
> Am 08.10.2013 um 20:34 schrieb sebb <se...@gmail.com>:
>
>> On 8 October 2013 18:19, Emmanuel Bourg <eb...@apache.org> wrote:
>> Le 08/10/2013 18:29, Benedikt Ritter a écrit :
>>
>>> there was this issue with the failing test related to the eclipse compiler.
>>> Can you comment on this? Is it fix? If it's broken, should we document it?
>>
>> As I understand it already exists in JCI 1.0, so nothing new on this side.
>
> See JCI-59
>
> The problem is that the Eclipse API requires code to decide which
> names are package names; this is not trivial, especially given the
> convoluted compiler API.
Thank you.
>
>> Emmanuel Bourg
>>
>>
>> ---------------------------------------------------------------------
>> 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] New release?
Posted by sebb <se...@gmail.com>.
On 8 October 2013 18:19, Emmanuel Bourg <eb...@apache.org> wrote:
> Le 08/10/2013 18:29, Benedikt Ritter a écrit :
>
>> there was this issue with the failing test related to the eclipse compiler.
>> Can you comment on this? Is it fix? If it's broken, should we document it?
>
> As I understand it already exists in JCI 1.0, so nothing new on this side.
See JCI-59
The problem is that the Eclipse API requires code to decide which
names are package names; this is not trivial, especially given the
convoluted compiler API.
> Emmanuel Bourg
>
>
> ---------------------------------------------------------------------
> 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] New release?
Posted by Emmanuel Bourg <eb...@apache.org>.
Le 08/10/2013 18:29, Benedikt Ritter a écrit :
> there was this issue with the failing test related to the eclipse compiler.
> Can you comment on this? Is it fix? If it's broken, should we document it?
As I understand it already exists in JCI 1.0, so nothing new on this side.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jci] New release?
Posted by Benedikt Ritter <br...@apache.org>.
Hi Emmanuel,
there was this issue with the failing test related to the eclipse compiler.
Can you comment on this? Is it fix? If it's broken, should we document it?
Thanks!
Benedikt
2013/10/8 Emmanuel Bourg <eb...@apache.org>
> Le 08/10/2013 12:02, Torsten Curdt a écrit :
> > Not sure what has changed since the last release but a release is
> certainly
> > overdue.
>
> Here is the list of user visible changes I compiled from JIRA and the
> SVN history. Let me know if I forgot something important.
>
> Fixed bugs:
>
> o Fixed a NPE in FilesystemAlterationMonitor when the directory is not
> readable (JCI-68)
> o Compiling classes with cross imports using Janino no longer causes a
> stack overflow (JCI-53)
> o FilesystemAlterationMonitor no longer throws a NPE when calling stop()
> before start() (JCI-62)
> o EclipseJavaCompiler properly closes the InputStreams (JCI-58)
> o Eclipse compiler settings are no longer ignored (JCI-50, JCI-51)
> o Fixed an issue preventing the Eclipse compiler from loading resources
> from the ResourceStore (JCI-56)
>
> Changes:
>
> o Updated the API to use generics
> o JaninoJavaCompiler is now compatible with Janino(2.6 (JCI-69)
> o EclipseJavaCompiler is now compatible with the Eclipse JDT compiler 4.2.2
> o Dropped the javac compiler since it only worked with Java 5 (JCI-73)
> o Improved the thread safety of FilesystemAlterationMonitor (JCI-74)
> o The FilesystemAlterationMonitor thread is now a daemon thread (JCI-65)
> o The Eclipse compiler now supports source/target 1.7
>
> Emmanuel Bourg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [jci] New release?
Posted by Emmanuel Bourg <eb...@apache.org>.
Le 08/10/2013 12:02, Torsten Curdt a écrit :
> Not sure what has changed since the last release but a release is certainly
> overdue.
Here is the list of user visible changes I compiled from JIRA and the
SVN history. Let me know if I forgot something important.
Fixed bugs:
o Fixed a NPE in FilesystemAlterationMonitor when the directory is not
readable (JCI-68)
o Compiling classes with cross imports using Janino no longer causes a
stack overflow (JCI-53)
o FilesystemAlterationMonitor no longer throws a NPE when calling stop()
before start() (JCI-62)
o EclipseJavaCompiler properly closes the InputStreams (JCI-58)
o Eclipse compiler settings are no longer ignored (JCI-50, JCI-51)
o Fixed an issue preventing the Eclipse compiler from loading resources
from the ResourceStore (JCI-56)
Changes:
o Updated the API to use generics
o JaninoJavaCompiler is now compatible with Janino(2.6 (JCI-69)
o EclipseJavaCompiler is now compatible with the Eclipse JDT compiler 4.2.2
o Dropped the javac compiler since it only worked with Java 5 (JCI-73)
o Improved the thread safety of FilesystemAlterationMonitor (JCI-74)
o The FilesystemAlterationMonitor thread is now a daemon thread (JCI-65)
o The Eclipse compiler now supports source/target 1.7
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jci] New release?
Posted by Gary Gregory <ga...@gmail.com>.
Go for it :)
Gary
On Oct 8, 2013, at 6:03, Torsten Curdt <tc...@vafer.org> wrote:
> Not sure what has changed since the last release but a release is certainly
> overdue.
> Release early - release often ;)
> Sure! Go ahead!
>
>
> On Tue, Oct 8, 2013 at 11:28 AM, Emmanuel Bourg <eb...@apache.org> wrote:
>
>> Hi all,
>>
>> I'd like to push out a new release of [jci]. Despite the remaining
>> issues it's still an improvement compared to the previous release.
>>
>> Any objection?
>>
>> Emmanuel Bourg
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jci] New release?
Posted by Torsten Curdt <tc...@vafer.org>.
Not sure what has changed since the last release but a release is certainly
overdue.
Release early - release often ;)
Sure! Go ahead!
On Tue, Oct 8, 2013 at 11:28 AM, Emmanuel Bourg <eb...@apache.org> wrote:
> Hi all,
>
> I'd like to push out a new release of [jci]. Despite the remaining
> issues it's still an improvement compared to the previous release.
>
> Any objection?
>
> Emmanuel Bourg
>
>