Agree Hadrian,
We discussed about that with Marcel.
We are all agree that ACE MUST run in any OSGi container.
But, my purpose is really to increase the ACE adoption by give a
ready-to-use runtime. I think it's very difficult right now for newbie
to simply understand and begin to use ACE.
With a ACE runtime, they can begin to use it.
After, they become "power" users and are able to bootstrap ACE by them self.
Regards
JB
On 02/23/2011 03:28 PM, Hadrian Zbarcea wrote:
ACE must run in any OSGi container. Karaf is actually not an OSGi container per
se, it sits atop Equinox or Felix (you can change that with one property) and
it adds some useful features to a standard OSGi container. From what I saw
there are no dependencies from ACE on Karaf, and there shouldn't be.
That said, if the default ACE distro will come with a Karaf container out of
the box, I suspect many of the users will just use that. I don't know if that
would be a bad thing (probably not). Running ACE in other containers or without
Karaf could be covered by documentation (for now at least).
Marcel, +1 on provisioning ACE with ACE.
My $0.02,
Hadrian
On Feb 23, 2011, at 8:38 AM, Marcel Offermans wrote:
I would prefer a distribution that can also run on just any OSGi container. I
don't mind also providing a feature so one can easily run it in Karaf, but I'm
hesitant about making ACE somehow dependent on more than just the OSGi
framework itself.
I know we currently use Pax Runner to bootstrap, which (especially when
developing) is a very flexible way of launching frameworks, but with the new
launcher API we should be able to write a very small piece of bootstrap code
that launches ACE.
By the way, I completely agree with your end goals JB, run the server with a
simple script and run the target by deploying an agent in an OSGi instance
(and/or provide an OSGi instance with an agent).
Looking ahead a bit (not for now) we should be able to eat our own dogfood and
be able to provision an ACE server with ACE. Of course the first ACE server
would have to be bootstrapped with a script anyway. ;)
Greetings, Marcel
On Feb 23, 2011, at 12:50 ,<[email protected]> <[email protected]> wrote:
I would prefer to create a custom karaf distribution. I can do it very quickly.
Regards
JB
-----Original Message-----
From: "Geert Schuring"<[email protected]>
Date: Wed, 23 Feb 2011 12:49:21
To:<[email protected]>
Reply-To: [email protected]
Cc:<[email protected]>
Subject: Re: [PROPOSAL] ACE 0.8.0 ReleaseCandidate
I was thinking exactly the same. We can re-use the servicemix
configuration for creating a Karaf based Ace distribution.
Geert.
About the same topic, what do you think about provide a runtime
distribution based on Karaf ?
We can create a distribution kit based on Karaf + ACE feature.
I heavily think that it should be the target.
The end-user only need to launch bin/ace to have the console and all
runtime bundles up and running. He just has to deploy the ACE agent into
the target instances.
Regards
JB
On 02/23/2011 10:37 AM, Jean-Baptiste Onofré wrote:
Hi again,
FYI, I propose to add an assembly in 0.8.0 release. The assembly should
provide the following artifacts:
- ACE sources archive (zip/tar.gz)
- ACE agent runtime (zip/tar.gz)
- ACE consoles (zip/tar.gz)
The purpose to give the user the possibility to quickly start with ACE.
WDYT ?
Regards
JB
On 02/23/2011 09:08 AM, Jean-Baptiste Onofré wrote:
Hi all,
Geert and I are working on fully support of Maven 3 in ACE (properties,
cleanups, etc).
I hope to complete it end of this morning.
In the mean time, I deployed Felix Metatype, Dependency Manager and
Deployment Admin into the ACE m2 repo:
http://svn.apache.org/repos/asf/incubator/ace/repo/org/apache/felix/
and defined this repo in the ACE pom.
It allows users to be able to build ACE directly without building
previous dependencies.
I think that we are not so far from a release now.
I propose:
1/ to release ACE 0.8.0 asap (I can do it tomorrow). It's a
ReleaseCandidate version. The purpose is to check the release process
(identify if there are some particular points) and document this
release
process.
2/ The 0.8.0 will allow us to prepare demo/tests and identify what's
the
pending points. My purpose is to be able to prepare a ACE 1.0 release
for end of march, and allow Marcel and Karl to announce ACE 1.0 at
OSGiCon/EclipseCon during the ACE talk.
WDYT ?
Regards
JB
