ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sibla Wilfried <>
Subject AW: Minimising ACE's file size
Date Mon, 02 Sep 2013 07:30:02 GMT
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
	-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
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.


-----Urspr√ľngliche Nachricht-----
Von: Ryan Moquin [] 
Gesendet: Donnerstag, 29. August 2013 15:14
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

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.

On Aug 29, 2013 4:06 AM, "Marcel Offermans" <>

> 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