You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@ace.apache.org by Cristiano Gavião <cv...@gmail.com> on 2015/12/10 13:58:19 UTC
Ace artifacts on maven central ?
Hi,
I read somewhere that Apache Ace follows the OSGi Deployment Admin spec,
so we decided to try it.
We are using Equinox and p2 as its repository in our environment and
building our bundles with tycho and maven-bundle-plugin.
So in order to have the deployment agent installed in our p2 we need to
have the required artifacts at least in a maven repository.
But in the maven central the latest apache ace artifacts is in version
0.8.1 and was delivered in 2011 !
Is Apache ace not being delivered to maven central anymore ? why?
thanks,
Cristiano
Re: Ace artifacts on maven central ?
Posted by Jan Willem Janssen <ja...@luminis.eu>.
> On 10 Dec 2015, at 15:46, Cristiano Gavião <cv...@gmail.com> wrote:
>
> I was able to download the binary distribution from here: http://ace.apache.org/downloads.html
>
> but I was not able to find the deployment agent bundle. where it is ? The target.jar was not recognized as a osgi bundle…
The target.jar is a standalone binary that wraps the `org.apache.ace.agent` bundle in an OSGi framework
and some other bundles to easily bootstrap your target. If you’re interested in the DA bundle, use the `org.apache.ace.agent` bundle.
> one doubt, suppose that I have some *.dp archives (as defined by the spec) in a local directory. it is possible to start up the container with the deployment agent installed and started and pass that location as system/app argument at command line?
Yes, this is certainly possible. If you happen to use the Gogo shell, then there’s a command named `idp` that
allows you to install deployment packages.
HtH,
--
Met vriendelijke groeten | Kind regards
Jan Willem Janssen | Software Architect
+31 631 765 814
My world is revolving around INAETICS and Amdatu
Luminis Technologies B.V.
Churchillplein 1
7314 BZ Apeldoorn
+31 88 586 46 00
http://www.luminis-technologies.com
http://www.luminis.eu
KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
Re: Ace artifacts on maven central ?
Posted by Cristiano Gavião <cv...@gmail.com>.
Hi again,
I was able to download the binary distribution from here:
http://ace.apache.org/downloads.html
but I was not able to find the deployment agent bundle. where it is ?
The target.jar was not recognized as a osgi bundle...
one doubt, suppose that I have some *.dp archives (as defined by the
spec) in a local directory. it is possible to start up the container
with the deployment agent installed and started and pass that location
as system/app argument at command line?
regards,
Cristiano
On 10-12-2015 10:10, Marcel Offermans wrote:
> Hello Cristiano,
> On 10 December 2015 at 14:01:01, Cristiano Gavião (cvgaviao@gmail.com) wrote:
>
> I read somewhere that Apache Ace follows the OSGi Deployment Admin spec,
> so we decided to try it.
> That is correct.
>
> We are using Equinox and p2 as its repository in our environment and
> building our bundles with tycho and maven-bundle-plugin.
> Ok.
>
> So in order to have the deployment agent installed in our p2 we need to
> have the required artifacts at least in a maven repository.
> The agent consists of only a single bundle.
>
> But in the maven central the latest apache ace artifacts is in version
> 0.8.1 and was delivered in 2011 !
> Yes. During that time we were still using Maven to build ACE, but we have since moved on to using Bndtools and an Ant based build that is automatically generated by Bndtools. That means we have also changed the way we do releases. Our source and binary convenience releases are stored in the official Apache release repository. We are not doing any convenience releases at the moment towards any other repositories.
>
> Is Apache ace not being delivered to maven central anymore ? why?
> We have been considering this, generating the Maven metadata from our build and using that to publish those artifacts but that process is not done yet. If you want to help us with it, please do.
>
> For now my advice would be to manually upload the single bundle with the agent to your own Maven repository and use that in your builds.
>
> Greetings, Marcel
>
>
>
>
Re: Ace artifacts on maven central ?
Posted by Cristiano Gavião <cv...@gmail.com>.
Hi Marcel,
On 10-12-2015 10:10, Marcel Offermans wrote:
> Our source and binary convenience releases are stored in the official Apache release repository.
Which repository would be that? it is a R5 OSGi repository ?
> We have been considering this, generating the Maven metadata from our build and using that to publish those artifacts but that process is not done yet. If you want to help us with it, please do.
well, I would, but I don't know anything about ant or gradle. Actually,
I didn't like grade and that is the reason I keep away from bndtools.
But indirectly I use bndlib with maven-bundle-plugin.
Re: Ace artifacts on maven central ?
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Cristiano,
On 10 December 2015 at 14:01:01, Cristiano Gavião (cvgaviao@gmail.com) wrote:
I read somewhere that Apache Ace follows the OSGi Deployment Admin spec,
so we decided to try it.
That is correct.
We are using Equinox and p2 as its repository in our environment and
building our bundles with tycho and maven-bundle-plugin.
Ok.
So in order to have the deployment agent installed in our p2 we need to
have the required artifacts at least in a maven repository.
The agent consists of only a single bundle.
But in the maven central the latest apache ace artifacts is in version
0.8.1 and was delivered in 2011 !
Yes. During that time we were still using Maven to build ACE, but we have since moved on to using Bndtools and an Ant based build that is automatically generated by Bndtools. That means we have also changed the way we do releases. Our source and binary convenience releases are stored in the official Apache release repository. We are not doing any convenience releases at the moment towards any other repositories.
Is Apache ace not being delivered to maven central anymore ? why?
We have been considering this, generating the Maven metadata from our build and using that to publish those artifacts but that process is not done yet. If you want to help us with it, please do.
For now my advice would be to manually upload the single bundle with the agent to your own Maven repository and use that in your builds.
Greetings, Marcel