Hi guys,
I agree with Andreas: mvn version:set on master to define 4.0.0-SNAPSHOT
is OK IMHO.
Regards
JB
On 03/25/2014 10:35 AM, Andreas Pieber wrote:
I don't see a problem with simply turning up the version number on the
master and branching off before Guillaumes commit and keeping the version
there.
Kind regards,
Andreas
On Mon, Mar 24, 2014 at 10:03 PM, Jamie G. <[email protected]> wrote:
Master currently is at 3.1.0-SNAPSHOT, we'd need to branch that checkin at
4.0.
--Jamie
On Mon, Mar 24, 2014 at 5:32 PM, Achim Nierbeck <[email protected]>
wrote:
Wow, now that's been a commit :D
As far as I can tell right now this would mean master is version 4.0, at
least that's what
we discussed before, would be the impact of those changes.
I think we have another possibility, we might create a branch based on
the
revision before this commit. This would give also give a lot more people
a
way of experimenting with the "impact" of
the new core design.
Regards, Achim
2014-03-24 17:52 GMT+01:00 Guillaume Nodet <[email protected]>:
I pushed quite a few commits to master a few minutes ago. FWIW, that
was
slightly not done on purpose, but I wanted to push the last fix to
master
and ... everything went with it ;-)
Anyway, those commits are related to making Karaf more lightweight and
switching out blueprint to pure OSGi. The code has been mostly
unchanged
(i.e. mainly switching the blueprint xml to a BundleActivator class with
eventually a few very minor changes to the service implementation
classes).
The end result is the following:
* features/framework is bare to the down minimum: pax-url-aether,
pax-url-wrap (we could actually remote it), pax-logging, configadmin,
fileinstall, region/core and features/core
* the default karaf distro is mostly unchanged, though everything is
installed through features, including the console
* the minimal distribution does not install aries-blueprint,
aries-proxy
and the shell compatibility (the previous shell console to support 2.x
or
3.0 commands), so it's much more lightweight, even though some services
could be removed at will
Actually, I just spotted that the aries jars are still included in the
minimal distro, even if not installed, so I'll try to align the
contained
bundles to those installed.
Again, that was not really intended, so if there's a push back, we can
git
revert or force update ...
Guillaume
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
&
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
