Hi

[paul turner <pa...@gmail.com>]

Hi,
I'm Paul Turner and I'd like to get involved with the etch project.

de.linkedin.com/pub/paul-turner/4/26b/394/

I am a core Java developer with more than 10 years experience, mainly in
banking and financial services.

I can see that a lot of the java binding code is using pre-Java 5 threading
idioms.
Is that something I could change to improve reliability/ performance/
standards adherence?
e.g. TodoManager and FreePool could use util.concurrent threadpools/
semaphores etc.
These a lot of good stuff in util.concurrent that could make the unit tests
more robust as well.
Normally I'd raise a Jira, but I don't have permissions to do that.

I do see that the Java bindings has not been changed in a few months, is it
still an active project?

Many thanks

Paul Turner

Re: Hi

[paul turner <pa...@gmail.com>]

Hi Martin,

Great, expect a patch soon!  Thanks for the guidance, I'll be careful with
the points you noted.

best regards

Paul


On Thu, Feb 14, 2013 at 2:32 PM, Martin Veith <Ma...@bmw-carit.de>wrote:

> Hi Paul,
>
> nice to meet you, welcome to the Etch developer community!
>
> paul turner wrote on 2013-02-14:
> > I can see that a lot of the java binding code is using pre-Java 5
> > threading idioms.
> > Is that something I could change to improve reliability/ performance/
> > standards adherence?
> > e.g. TodoManager and FreePool could use util.concurrent threadpools/
> > semaphores etc.
> > These a lot of good stuff in util.concurrent that could make the unit
> > tests more robust as well.
> Refactoring the threading parts and using the new concurrent API sounds
> good to me! If you need any help by building the source, just let us know!
> Short note: at the moment the Etch Java-Binding works without any changes
> on the Android platform which is used by some of our users. We should take
> care that this compability is not lost by using some fancy Java mechanisms
> which are not yet available on Android. But as far as I know all
> util.concurrent is available also on Android. So feel free to start!
>
> Another Java-related task popping up in my mind is the refactoring of the
> JUnit tests to become compatible with the newest JUnit version. At the
> moment we have a hard dependency to JUnit 4.3.1.
>
>
> > Normally I'd raise a Jira, but I don't have permissions to do that.
> According to the permission scheme every user in the jira-user group
> should have the permission to create an issue. Have you been logged in?
>
> >
> > I do see that the Java bindings has not been changed in a few months,
> > is it still an active project?
> The Java-Binding is active and widly used.  As the runtime is kind of
> stable there haven't been any activity in this area the last few months,
> but there is always room for improvement!
> Our main focus of development the last months has been the C++ binding in
> order to bring both the compiler and runtime to a stable status.
>
> I'm looking forward to see the first patch from you!
>
> Cheers,
> Martin
>
>
>

RE: Hi

[Martin Veith <Ma...@bmw-carit.de>]

Hi Paul,

nice to meet you, welcome to the Etch developer community!

paul turner wrote on 2013-02-14:
> I can see that a lot of the java binding code is using pre-Java 5
> threading idioms.
> Is that something I could change to improve reliability/ performance/
> standards adherence?
> e.g. TodoManager and FreePool could use util.concurrent threadpools/
> semaphores etc.
> These a lot of good stuff in util.concurrent that could make the unit
> tests more robust as well.
Refactoring the threading parts and using the new concurrent API sounds good to me! If you need any help by building the source, just let us know!
Short note: at the moment the Etch Java-Binding works without any changes on the Android platform which is used by some of our users. We should take care that this compability is not lost by using some fancy Java mechanisms which are not yet available on Android. But as far as I know all util.concurrent is available also on Android. So feel free to start!

Another Java-related task popping up in my mind is the refactoring of the JUnit tests to become compatible with the newest JUnit version. At the moment we have a hard dependency to JUnit 4.3.1.


> Normally I'd raise a Jira, but I don't have permissions to do that.
According to the permission scheme every user in the jira-user group should have the permission to create an issue. Have you been logged in?

> 
> I do see that the Java bindings has not been changed in a few months,
> is it still an active project?
The Java-Binding is active and widly used.  As the runtime is kind of stable there haven't been any activity in this area the last few months, but there is always room for improvement!
Our main focus of development the last months has been the C++ binding in order to bring both the compiler and runtime to a stable status.

I'm looking forward to see the first patch from you!

Cheers,
Martin