[JSR-354] Re: Streamlining of Spis
- From: Werner Keil <werner.keil@...>
- To: jcurrency_mail@...
- Subject: [JSR-354] Re: Streamlining of Spis
- Date: Tue, 9 Jul 2013 01:10:07 +0200
Thanks, that sounds like a good simplification of the structure. Given this
version of the JSR is likely to be Final before Java 9 has even been
branched out of OpenJDK, or at least long before it is even looking for
JEPs and features, the separation into SE and EE seemed odd.
I assume all 3 parts of the RI are genuine components of the Reference
Implementation and thus will get covered by the TCK over time?
Anything that should for whatever reason not be considered part of the RI
(there can be only one RI, but looking at e.g. Java EE it has multiple
"profiles", thus something similar here might not be an issue) should not
be there. Ideally moved into other repositories or projects of the Github
Which Maven modules do you mean, those under RI (there as mentioned,
profiling or targeting requires separation) or those under API?
There modularity could help using only a smaller portion (just see SE 8, it
also comes in different sizes and an Embedded SE on Raspberry Pi may have
some limitations or a headless version may not require the "format" bundle
at all[?]) but until Java 9 and "Jigsaw" become reality it may not be a
killer criteria to have multiple Maven artifacts.
For Embedded, not just ME, also SE it's worth a thought keeping it, but
it's up to you or other opinions if we keep all of them or at least merge a
Werner Keil | JCP Executive Committee Member | Eclipse UOMo Lead, Babel
Language Champion | Java Godfather | Mærsk DevOps Build Manager
Twitter @wernerkeil | @JSR354 | #EclipseUOMo | #Java_Social | #DevOps
Skype werner.keil | Google+ gplus.to/wernerkeil
* Eclipse DemoCamps Kepler 2013: June-August 2013, Germany, Denmark, Austria,
Norway. Werner Keil, UOMo Lead, Mærsk DevOps Build Manager will
DevOps with Hudson, Maven, Kokki, Multiconf & PyDev", "M4M 2 the Rescue of
On Tue, Jul 9, 2013 at 12:11 AM, Anatole Tresch <atsticks@...> wrote:
> Dear all
> I also moved some SPIs into the API part and backed up the accessor
> singletons with according singleton spis. The advantage is that mainly the
> singleton spis are the entry points for different environments such as SE
> using ServiceLoader only, SE with Inject (JSR 330/299) or EE.
> The MoneyLoader component therefore could be completely removed.
> So basically the main API/SPI updates should be through (despite I get
> further feedback, or ideas what might be useful furthermore).
> What I asked me, is if we should simplify also our maven build structure,
> since we currently are going for a standalone scope:
> *parent (root)*
> - *API *containing the whole API (code, conversion, format, ext)
> - *RI *containing the basic RI for all areas
> - - *se *containing the executable registrations for SE (depends on RI)
> - - *cdi *containing the executable parts for CDI SE container (using
> Weld SE)
> - - *ee *containing the extensions for using in a CDI container
> - *TCK*
> When reorganizing the project, similarly the build should be adapted to
> use Sonar, so any cycles introduced will popup instantly.
> Opinions? Is there a reason why we must stick on the several maven
> modules, which can also be modeled by packages?
> *Anatole Tresch*
> Java Lead Engineer, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/*
> *Google: atsticks
> Phone +41-44 334 40 87
> Mobile +41-76 344 62 79*
Description: GIF image