It makes sense (and it was my plan ;)).
A first thing that I wonder is: does it make sense to keep the Java5
compatibility (via the default-java5 parent pom) ?
Anyway, I will send the questions/discussions on the mailing list.
Regards
JB
On 01/22/2013 08:24 PM, Daniel Kulp wrote:
On Jan 22, 2013, at 1:37 PM, Jean-Baptiste Onofré <[email protected]> wrote:
Maybe it would be interesting to update some part of the Maven modules
structure, etc.
I have a couple of ideas about that, maybe I can prepare patches and submit it,
with a discussion on the mailing list.
Likely discuss any major ideas on list first. A lot of the current maven
structure is setup for support of the semantic versioning and individual module
release things and may be difficult to change. I'd suggest making proposals
on the dev list first before spending too much time revamping things that then
won't get accepted.
Dan
WDYT ?
Regards
JB
On 01/22/2013 07:25 PM, David Bosschaert wrote:
On 22 January 2013 18:21, Daniel Kulp <[email protected]> wrote:
On Jan 22, 2013, at 1:16 PM, David Bosschaert <[email protected]>
wrote:
Hi Dan,
Any chance of including SPI Fly [1]? Simple all the modules under the
spi-fly directory...
This would be the 1.0.0 release of SPI Fly which is the Reference
Implementation of the OSGi Service Loader mediator spec [2].
I'm not sure I'll have time with all the others. I'm mostly trying to
get all the stuff that Karaf needs so we're not holding up their releases.
If I don't get to it tomorrow with the others, I'll try and do a separate
release for spifly stuff later this week.
Dan
Either way is fine with me. Many thanks Dan!
Note to self: need to get up to speed on doing releases for Aries so I can
help out next time.
Cheers,
David
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
