The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/150
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/151
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
On Mon, May 26, 2014 at 9:12 AM, Michael Dürig mdue...@apache.org wrote:
Apart from that - and this is probably a separate discussion - I also think
we should split oak-run up as it is getting too heavy.
Too heavy in which way? If you refer to the size of the jar, I fail to
see how it's
On 27.5.14 3:33 , Jukka Zitting wrote:
Hi,
On Mon, May 26, 2014 at 9:12 AM, Michael Dürig mdue...@apache.org wrote:
Apart from that - and this is probably a separate discussion - I also think
we should split oak-run up as it is getting too heavy.
Too heavy in which way?
Functionality
For me more than size the problem is usage of Lucene To use full power
of Oak we need to include Lucene 4.x and thus would need to drop JR2.
So probably have two modules
1. oak-run - server, benchmarking, console, debugging, scalability, backup
2. oak-migration - upgrade, jr2 specific
On 27.5.14 4:26 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 9:47 AM, Michael Dürig mdue...@apache.org wrote:
On 27.5.14 3:33 , Jukka Zitting wrote:
Too heavy in which way?
Functionality wise. It is growing into a chief cook and bottle washer. It
already does backup, benchmarking,
Hi,
On Tue, May 27, 2014 at 10:36 AM, Michael Dürig mdue...@apache.org wrote:
This is not about different jars but about setting it up as a OSGi container
into which the respective bundles could get deployed.
We can turn the jar in to an OSGi container, but why not ship
everything everything
On 27.5.14 4:48 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 10:36 AM, Michael Dürig mdue...@apache.org wrote:
We can turn the jar in to an OSGi container, but why not ship
everything everything we can by default?
Because
increase flexibility, test and showcase OSGi readiness of
Hi,
On Tue, May 27, 2014 at 10:53 AM, Michael Dürig mdue...@apache.org wrote:
Because
increase flexibility, test and showcase OSGi readiness of Oak,
resolve version conflicts (e.g. Lucene), let others easily plug in
their own stuff (e.g scripting language through JSR-223).
Fair enough, but
fwiw I would (for a change :) ) would like to avoid OSGi here and keep
things as they are for following reasons
1. JR2 is not OSGi friendly and we use some of the internal classes
for upgrade which would be problematic in OSGI
2. For debug and console we rely on some non exported packages. Using
On 27.5.14 5:13 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 10:53 AM, Michael Dürig mdue...@apache.org wrote:
Because
increase flexibility, test and showcase OSGi readiness of Oak,
resolve version conflicts (e.g. Lucene), let others easily plug in
their own stuff (e.g scripting
The Buildbot has detected a build exception on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/157
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
On Tue, May 27, 2014 at 11:24 AM, Michael Dürig mdue...@apache.org wrote:
Users needn't be aware of the OSGi container inside if they just want to
quickly try something out. Running with e.g. the benchmark option would
still run the benchmark suite. The difference would be that in the
On 27.5.14 5:33 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 11:24 AM, Michael Dürig mdue...@apache.org wrote:
Users needn't be aware of the OSGi container inside if they just want to
quickly try something out. Running with e.g. the benchmark option would
still run the benchmark suite.
14 matches
Mail list logo
