time 2015-04
It’s not only the spec-api stuff.
There are also many other things like xbean, geronimo-jta, javamail, etc. It’s
basically a commons-EE atm.
If you talk about a reboot then I wonder what you had in mind. There is TomEE
which takes the really lightweight approach. And having two
It’s not only the spec-api stuff.
There are also many other things like xbean, geronimo-jta, javamail, etc. It’s
basically a commons-EE atm.
If you talk about a reboot then I wonder what you had in mind. There is TomEE
which takes the really lightweight approach. And having two implementations
I agree, we should start moving our focus.
When you speak of #2, what bits do you speak of? The glue that assembles the
various JSR implementations of the JEE spec?
I wonder if we should start a total re-write. We’ve learned a thing or two
since this project started and the current Zeitgeist
Hi,
For 1, it will be nice to be able to build geronimo server with more
packaging/assembly options. For example, it will be very useful to be able
to have an assembly that supports tomcat war without ejb, rar, ear. Also,
it will be very useful as well to be able to customize assembly options
Txs Alan!
I think we should probably move our focus finally? The Geronimo project
basically consists of 2 different things.
1.) the Geronimo EE server
2.) all the rest ;)
2 is doing really fine. 1 is worrying. Or are there any significant people
interested in continueing with 1?
Should we
Here's my initial draft:
https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-04+-+April
https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-04+-+April
If I missed something please let me know or go ahead and update the
