ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Offermans <>
Subject Re: Minimising ACE's file size
Date Tue, 10 Sep 2013 14:11:53 GMT
Hello Ryan,

I think I might have answered that in my previous mail. :)

There are some differences between Karaf and ACE features, but nothing that's impossible to
overcome or convert. A code contribution in that area would definitely be interesting!

I think in short there are two options:

1) when you import a feature, if it depends on other features you simply recursively collect
all of them until you end up with one big feature containing all the bundles;
2) when you import a feature that depends on another feature, you import that other feature
separately and keep recursively doing that until you've got all the features and subsequently
you create a single distribution that groups all those features.

I also remember that Karaf features could contain configuration data. You could convert that
into autoconf files and add such artifacts to the OBR (and link them with the feature).

All from memory, so I might have missed some finer points. Definitely re-read the Karaf feature
documentation before you start (and maybe share your design with us upfront so we can provide
more feedback).

Greetings, Marcel

On Sep 5, 2013, at 2:06 , Ryan Moquin <> wrote:

> For some reason, I thought that Marcel (I think that's the right person),
> said that there are some issues that would need to be overcome in regards
> to the mapping of the feature.xml schema to the way ACE sets things up...
> maybe I misread his comments.  I'll see if I can write some code to do it
> that I can contribute, I think that would be helpful for a lot of people.
> Thanks!
> Ryan
> On Wed, Sep 4, 2013 at 5:20 AM, Sibla Wilfried
> <>wrote:
>> Hi Ryan,
>> I used the open source Nexus extended with the nexus-obr-plugin.
>> It must be clarified, if this combination could be used in a production
>> environment (internally I will delegate this to some legal staff....).
>> Implementing a interpreter to derive ACE features from Karaf features
>> would not be a big deal. Afaik there isn't a implementations available yet.
>> Danke und Grüße
>> Wilfried
>> -----Ursprüngliche Nachricht-----
>> Von: Ryan Moquin []
>> Gesendet: Mittwoch, 4. September 2013 06:34
>> An:
>> Betreff: Re: Minimising ACE's file size
>> Awesome, that is helpful information and helps point me in the right
>> direction.  I haven't sold my company on Nexus Pro yet, but my intention
>> was to do that and use the OBR functionality.  It's interesting that
>> other's are doing things this way, since it makes me wonder about using
>> Apache Karaf Cave (which understands the Karaf features.xml) and see if
>> somehow that would result in simplifying things.. though I don't know a
>> whole lot about either yet to really have any clue at this point. :)  I'm
>> glad process is being made in this area, maybe I'll end up being able to
>> contribute something else instead if this process is being taken care of
>> already.
>> Ryan
>> On Mon, Sep 2, 2013 at 3:30 AM, Sibla Wilfried
>> <>wrote:
>>> Hi Ryan
>>> Regarding the aspect of maven plugin: I'm using a shell script with
>>> commands like this:
>>> mvn deploy:deploy-file -DgroupId=org.apache.ace
>>> -DartifactId=$artifactID -Dversion=$version
>>> -Dfile=../org.apache.ace.authentication/generated/org.apache.ace.authe
>>> ntication.impl.jar
>>> -Dpackaging=jar
>>>        -DrepositoryId=$repoID -Durl=$repoURL -DgeneratePom=true
>>> These command are generated with another shell script and written into
>>> a shell script file. So I could execute single commands or deploy all
>>> artifacts together to my repo (I'm using Nexus).
>>> Btw.: I'm currently using this Nexus Repo directly as OBR (or even
>>> more the maven repo directly) for ACE. I don't use the ACE OBR.
>>> As artifact ID I'm using the file name of the artifact without the
>>> extension.
>>> The repo ID must correspond to the corresponding server ID in your
>>> maven settings.xml.
>>> The version is extracted from the corresponding bnd file.
>>> Additionally I created a maven project using the maven-assembly-plugin
>>> to assemble my runtime zips containing all required artifacts and
>>> configuration.
>>> With this setup I'm able to integrate the ACE bnd/ANT world with my
>>> maven centric dev and build environment.
>>> I'm possibly able to contribute this setup and my extensions to ACE
>>> within the next 2 month.
>>> Greetings
>>> Wilfried
>>> -----Ursprüngliche Nachricht-----
>>> Von: Ryan Moquin []
>>> Gesendet: Donnerstag, 29. August 2013 15:14
>>> An:
>>> Betreff: Re: Minimising ACE's file size
>>> Speaking of trunk... I noticed that you had acknowledged an issue
>>> where updates stop being deployed to targets in 1.0 0 and to use
>>> trunk.  Since then I have been building Ace from trunk periodically.
>>> I want to use Ace in a demo I'm putting together to try to get full
>>> adoption in our organization.  Should I be able to reasonably expect
>>> trunk is in a reasonble state?  Or could you maybe release Milestone
>>> versions for an upcoming release that you believe are most likely
>>> stable enough for the daring?  Just don't want to push it and end up
>>> breaking my demo. Part of issue is since the build isn't using maven,
>>> there aren't snapshot builds to grab.  Otherwise each tine I build
>>> they each have the same version as the one being worked towards.
>>> One last question.  Is there anywhere I can look to give me a more
>>> current view on how to interact with the Ace OBR in relation to using
>>> the maven-bundle-plugin to pushing artifacts to it?  I also was
>>> curious how release promotion works.. I don't have a huge amount of
>>> time (a week) and struggling figuring out how to move to ACE from using
>> Karaf Features...
>>> Thanks for any insight.  Ace looks like it's coming along and promising.
>>> As soon as this current demo is over I'd like to see how I can
>>> contribute if there are any nice to haves I can build and contribute,
>> let me know.
>>> Ryan
>>> On Aug 29, 2013 4:06 AM, "Marcel Offermans"
>>> <>
>>> wrote:
>>>> Hello Dan,
>>>> On Aug 28, 2013, at 17:57 PM, Daniel McGreal <>
>> wrote:
>>>>> I'm developing an application within the confines of 5.4 megabytes
>>>>> of
>>>> storage space.
>>>>> I'd like to use the ACE management agent within this application,
>>>>> but
>>>> the storage requirements are prohibitive. Can anyone offer any
>>>> suggestions through which I could repackage the agent to minimise
>>>> the
>>> jar's disk usage?
>>>> We are currently working on a full redesign of the management agent,
>>>> where one of the focus points is to make it a lot smaller. That work
>>>> is currently being done in org.apache.ace.agent in trunk, so you
>>>> might want to check that out. It's not done yet, we still have to
>>>> eliminate some dependencies to get the size down, but the basis we
>>>> have there now lends itself better to doing that.
>>>> All in all, this is coming, and I hope it makes the next release. In
>>>> the mean time, feel free to give us some feedback on this new version!
>>>> Greetings, Marcel

View raw message