You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by Premek Brada <br...@kiv.zcu.cz> on 2011/02/02 15:35:55 UTC

updating bundle-target mapping

Hello everybody,

while working on an IDE for Apache ACE (see 
http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an 
interesting issue: We are able to build a bundle from its Eclipse PDE 
project, and store the resulting new bundle version into ACE repository 
(server started off Eclipse). Then we successfully update the 
bundle-feature-distibution mapping and distribution-target mapping by 
manipulating the corresponding xml config files, but are unable to find 
a way to programmatically update the bundle-target mapping config which 
is (strangely?) also needed. The new version of the bundle therefore 
cannot be automatically pushed to a configured target.

(In other words, we are able to modify these ...
http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX
http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX
... but don't know how to modify this
http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
)

Currently therefore we resorted to a "solution" to bring up a popup 
window in Eclipse, instructing the user to run the Web UI and click 
"retrieve" and "store" so as to update the bundle-target mapping.

Surely there must be a better way :) or at least so we think (a "hidden" 
API or at least a well-defined URL on the repo/server). Could someone 
enlighten us please?

Thanks,
Premek

PS: If you think an ACE IDE could be helpful to you, please feel free to 
try it; we need feedback and ideas for its further evolution.

-- 
Premek Brada (Ing et MSc, PhD)
   Lecturer in Software enginering, Webmaster
   Department of Computer Science and Engineering
   University of West Bohemia, Pilsen, CZ
   <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>


Re: Maven build problem

Posted by jb...@nanthrax.net.
Hi Geert,

Yeah, we know for the felix depencymanager. I've updated ace-pom to use apache pom 8 (which provides the snapshot repo) but the dependencymanager snapshot is not available. We 've discussed with Marcel to upload one.

For the maven poms, which ones are you talking about ? I made a big cleanup commit last week, maybe I forgot some ;)

Thanks
Regards
JB
-----Original Message-----
From: "Geert Schuring" <ge...@schuring.eu>
Date: Mon, 14 Feb 2011 23:06:24 
To: <ac...@incubator.apache.org>
Reply-To: ace-dev@incubator.apache.org
Subject: Maven build problem

Hey folks,

I run into a build problem building the trunk without using any profile. 
Dependency manager 3.0.0-SNAPSHOT cannot be found in any repo. Is this a 
known issue? Should I build depman locally first, or is there a problem with 
the apache snapshot repo?

Also, I've noticed some inconsistencies in the maven pom files so I get the 
impression the transition to maven is not fully done yet. I've got several 
years of experience with maven builds so if I can help out in that area let 
me know.

(Some context: I'm a servicemix developer and would like to use Ace to 
provision a Servicemix 4 Cloud.)

Greets,
Geert.

-----Original Message----- 
From: Premek Brada
Sent: Monday, February 14, 2011 1:24 PM
To: ace-dev@incubator.apache.org
Cc: Bc. Tomas PODSKALSKY
Subject: Re: updating bundle-target mapping


Hi Angelo,

thanks for replying, I serve only as a proxy to the developer :( so I
have forwarded your suggestions to him and will wait for a response.

Premek


On 3.2.2011 21:39, Angelo van der Sijpt wrote:
> Hi Premek,
>
> Hm, it should be enough programmatically create the links, let the 
> StatefulGatewayRepository generate the new deployment version (you could, 
> for instance, start logging events to see whether that actually happens), 
> and commit the RepositoryAdmin.
>
> You are using the API's provided for this, e.g. the GatewayRepository and 
> friends? Besides, did you remember to either approve the gateway, or to 
> turn on its AutoApprove property?
>
> Angelo
>
>
> On Feb 2, 2011, at 3:35 PM, Premek Brada wrote:
>
>> Hello everybody,
>>
>> while working on an IDE for Apache ACE (see 
>> http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an 
>> interesting issue: We are able to build a bundle from its Eclipse PDE 
>> project, and store the resulting new bundle version into ACE repository 
>> (server started off Eclipse). Then we successfully update the 
>> bundle-feature-distibution mapping and distribution-target mapping by 
>> manipulating the corresponding xml config files, but are unable to find a 
>> way to programmatically update the bundle-target mapping config which is 
>> (strangely?) also needed. The new version of the bundle therefore cannot 
>> be automatically pushed to a configured target.
>>
>> (In other words, we are able to modify these ...
>> http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX
>> http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX
>> ... but don't know how to modify this
>> http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
>> )
>>
>> Currently therefore we resorted to a "solution" to bring up a popup 
>> window in Eclipse, instructing the user to run the Web UI and click 
>> "retrieve" and "store" so as to update the bundle-target mapping.
>>
>> Surely there must be a better way :) or at least so we think (a "hidden" 
>> API or at least a well-defined URL on the repo/server). Could someone 
>> enlighten us please?
>>
>> Thanks,
>> Premek
>>
>> PS: If you think an ACE IDE could be helpful to you, please feel free to 
>> try it; we need feedback and ideas for its further evolution.
>>
>> -- 
>> Premek Brada (Ing et MSc, PhD)
>>   Lecturer in Software enginering, Webmaster
>>   Department of Computer Science and Engineering
>>   University of West Bohemia, Pilsen, CZ
>>   <<   brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>
>>


-- 
Premek Brada (Ing et MSc, PhD)
   Lecturer in Software enginering, Webmaster
   Department of Computer Science and Engineering
   University of West Bohemia, Pilsen, CZ
   <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>




Re: Maven build problem

Posted by Marcel Offermans <ma...@luminis.nl>.
You're right, I'll add that to the page! Thanks!

Greetings, Marcel

On 15 Feb 2011, at 23:30 , Geert Schuring wrote:

> Marcel,
> 
> The deploymentadmin depends on the latest metatype snapshot (which
> apparently isn't available in apache snapshots repo either), so you might
> want to add that to the list of projects mentioned on
> http://incubator.apache.org/ace/maven-build.html that need to be build
> before ace can be build.
> 
> Geert.
> 
> -----Original Message----- From: Marcel Offermans
> Sent: Monday, February 14, 2011 11:44 PM
> To: ace-dev@incubator.apache.org ; Geert Schuring
> Subject: Re: Maven build problem
> 
> Hello Geert,
> 
> On 14 Feb 2011, at 23:06 , Geert Schuring wrote:
> 
>> I run into a build problem building the trunk without using any profile.
>> Dependency manager 3.0.0-SNAPSHOT cannot be found in any repo. Is this a
>> known issue? Should I build depman locally first, or is there a problem
>> with the apache snapshot repo?
> 
> Yes it is a known issue, and you should build the dependency manager,
> deployment admin (and the included auto configuration) from source,
> installing snapshots into your local Maven repository. We've documented that
> here: http://incubator.apache.org/ace/maven-build.html
> 
>> Also, I've noticed some inconsistencies in the maven pom files so I get
>> the impression the transition to maven is not fully done yet. I've got
>> several years of experience with maven builds so if I can help out in that
>> area let me know.
> 
> Contributions in that area are always very welcome! Not all of us here are
> Maven Aces so to speak. ;)
> 
>> (Some context: I'm a servicemix developer and would like to use Ace to
>> provision a Servicemix 4 Cloud.)
> 
> You've come to the right list! :)
> 
> Greetings, Marcel
> 


Re: Maven build problem

Posted by Geert Schuring <ge...@schuring.eu>.
Marcel,

The deploymentadmin depends on the latest metatype snapshot (which
apparently isn't available in apache snapshots repo either), so you might
want to add that to the list of projects mentioned on
http://incubator.apache.org/ace/maven-build.html that need to be build
before ace can be build.

Geert.

-----Original Message----- 
From: Marcel Offermans
Sent: Monday, February 14, 2011 11:44 PM
To: ace-dev@incubator.apache.org ; Geert Schuring
Subject: Re: Maven build problem

Hello Geert,

On 14 Feb 2011, at 23:06 , Geert Schuring wrote:

> I run into a build problem building the trunk without using any profile.
> Dependency manager 3.0.0-SNAPSHOT cannot be found in any repo. Is this a
> known issue? Should I build depman locally first, or is there a problem
> with the apache snapshot repo?

Yes it is a known issue, and you should build the dependency manager,
deployment admin (and the included auto configuration) from source,
installing snapshots into your local Maven repository. We've documented that
here: http://incubator.apache.org/ace/maven-build.html

> Also, I've noticed some inconsistencies in the maven pom files so I get
> the impression the transition to maven is not fully done yet. I've got
> several years of experience with maven builds so if I can help out in that
> area let me know.

Contributions in that area are always very welcome! Not all of us here are
Maven Aces so to speak. ;)

> (Some context: I'm a servicemix developer and would like to use Ace to
> provision a Servicemix 4 Cloud.)

You've come to the right list! :)

Greetings, Marcel


Re: Maven build problem

Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Geert,

On 14 Feb 2011, at 23:06 , Geert Schuring wrote:

> I run into a build problem building the trunk without using any profile. Dependency manager 3.0.0-SNAPSHOT cannot be found in any repo. Is this a known issue? Should I build depman locally first, or is there a problem with the apache snapshot repo?

Yes it is a known issue, and you should build the dependency manager, deployment admin (and the included auto configuration) from source, installing snapshots into your local Maven repository. We've documented that here: http://incubator.apache.org/ace/maven-build.html

> Also, I've noticed some inconsistencies in the maven pom files so I get the impression the transition to maven is not fully done yet. I've got several years of experience with maven builds so if I can help out in that area let me know.

Contributions in that area are always very welcome! Not all of us here are Maven Aces so to speak. ;)

> (Some context: I'm a servicemix developer and would like to use Ace to provision a Servicemix 4 Cloud.)

You've come to the right list! :)

Greetings, Marcel


Maven build problem

Posted by Geert Schuring <ge...@schuring.eu>.
Hey folks,

I run into a build problem building the trunk without using any profile. 
Dependency manager 3.0.0-SNAPSHOT cannot be found in any repo. Is this a 
known issue? Should I build depman locally first, or is there a problem with 
the apache snapshot repo?

Also, I've noticed some inconsistencies in the maven pom files so I get the 
impression the transition to maven is not fully done yet. I've got several 
years of experience with maven builds so if I can help out in that area let 
me know.

(Some context: I'm a servicemix developer and would like to use Ace to 
provision a Servicemix 4 Cloud.)

Greets,
Geert.

-----Original Message----- 
From: Premek Brada
Sent: Monday, February 14, 2011 1:24 PM
To: ace-dev@incubator.apache.org
Cc: Bc. Tomas PODSKALSKY
Subject: Re: updating bundle-target mapping


Hi Angelo,

thanks for replying, I serve only as a proxy to the developer :( so I
have forwarded your suggestions to him and will wait for a response.

Premek


On 3.2.2011 21:39, Angelo van der Sijpt wrote:
> Hi Premek,
>
> Hm, it should be enough programmatically create the links, let the 
> StatefulGatewayRepository generate the new deployment version (you could, 
> for instance, start logging events to see whether that actually happens), 
> and commit the RepositoryAdmin.
>
> You are using the API's provided for this, e.g. the GatewayRepository and 
> friends? Besides, did you remember to either approve the gateway, or to 
> turn on its AutoApprove property?
>
> Angelo
>
>
> On Feb 2, 2011, at 3:35 PM, Premek Brada wrote:
>
>> Hello everybody,
>>
>> while working on an IDE for Apache ACE (see 
>> http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an 
>> interesting issue: We are able to build a bundle from its Eclipse PDE 
>> project, and store the resulting new bundle version into ACE repository 
>> (server started off Eclipse). Then we successfully update the 
>> bundle-feature-distibution mapping and distribution-target mapping by 
>> manipulating the corresponding xml config files, but are unable to find a 
>> way to programmatically update the bundle-target mapping config which is 
>> (strangely?) also needed. The new version of the bundle therefore cannot 
>> be automatically pushed to a configured target.
>>
>> (In other words, we are able to modify these ...
>> http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX
>> http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX
>> ... but don't know how to modify this
>> http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
>> )
>>
>> Currently therefore we resorted to a "solution" to bring up a popup 
>> window in Eclipse, instructing the user to run the Web UI and click 
>> "retrieve" and "store" so as to update the bundle-target mapping.
>>
>> Surely there must be a better way :) or at least so we think (a "hidden" 
>> API or at least a well-defined URL on the repo/server). Could someone 
>> enlighten us please?
>>
>> Thanks,
>> Premek
>>
>> PS: If you think an ACE IDE could be helpful to you, please feel free to 
>> try it; we need feedback and ideas for its further evolution.
>>
>> -- 
>> Premek Brada (Ing et MSc, PhD)
>>   Lecturer in Software enginering, Webmaster
>>   Department of Computer Science and Engineering
>>   University of West Bohemia, Pilsen, CZ
>>   <<   brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>
>>


-- 
Premek Brada (Ing et MSc, PhD)
   Lecturer in Software enginering, Webmaster
   Department of Computer Science and Engineering
   University of West Bohemia, Pilsen, CZ
   <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>




Re: updating bundle-target mapping

Posted by Premek Brada <br...@kiv.zcu.cz>.
On 14.2.2011 13:24, Premek Brada wrote:
> Hi Angelo,
>
> thanks for replying, I serve only as a proxy to the developer :( so I 
> have forwarded your suggestions to him and will wait for a response.

OK, after a longish pause... a little correction of the original 
question, to clarify things up a bit.

The key puzzling thing for us is this: We know how to change the 
Artifact-Gateway mapping at:
 > 
http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
but we don’t know why it isn´t changed automatically when we change 
Artifact-Feature mapping at:
 > 
http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX

Could you enlighten us on that?

> On 3.2.2011 21:39, Angelo van der Sijpt wrote:
>> Hi Premek,
>>
>> Hm, it should be enough programmatically create the links, let the 

That's probably what we do - we access the ACE repository from within 
our code via its URL interface similarly to the legacy 
o.a.ace.test.tools.RepositoryTool (checkout and commit command) as 
described at http://incubator.apache.org/ace/software-development-tools.html

We modify the mappings repository in three steps:
1) download the mapping as XML
2) Parse and modify the XML by DOM
3) Upload the modified mapping to ACE Server

>> StatefulGatewayRepository generate the new deployment version (you 
>> could, for instance, start logging events to see whether that 
>> actually happens), and commit the RepositoryAdmin.
>>
>> You are using the API's provided for this, e.g. the GatewayRepository 
>> and friends? Besides, did you remember to either approve the gateway, 
>> or to turn on its AutoApprove property?

StatefulGatewayRepository and RepositoryAdmin aren't used because, erm, 
we don’t know how to use them. Would it be possible to give or point us 
to some simple example code (like that in RepositoryTool class)?

Thanks,
Premek and Tomas




>>
>> On Feb 2, 2011, at 3:35 PM, Premek Brada wrote:
>>
>>> Hello everybody,
>>>
>>> while working on an IDE for Apache ACE (see 
>>> http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an 
>>> interesting issue: We are able to build a bundle from its Eclipse 
>>> PDE project, and store the resulting new bundle version into ACE 
>>> repository (server started off Eclipse). Then we successfully update 
>>> the bundle-feature-distibution mapping and distribution-target 
>>> mapping by manipulating the corresponding xml config files, but are 
>>> unable to find a way to programmatically update the bundle-target 
>>> mapping config which is (strangely?) also needed. The new version of 
>>> the bundle therefore cannot be automatically pushed to a configured 
>>> target.
>>>
>>> (In other words, we are able to modify these ...
>>> http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX 
>>>
>>> http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX 
>>>
>>> ... but don't know how to modify this
>>> http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX 
>>>
>>> )
>>>
>>> Currently therefore we resorted to a "solution" to bring up a popup 
>>> window in Eclipse, instructing the user to run the Web UI and click 
>>> "retrieve" and "store" so as to update the bundle-target mapping.
>>>
>>> Surely there must be a better way :) or at least so we think (a 
>>> "hidden" API or at least a well-defined URL on the repo/server). 
>>> Could someone enlighten us please?
>>>
>>> Thanks,
>>> Premek
>>>
>>> PS: If you think an ACE IDE could be helpful to you, please feel 
>>> free to try it; we need feedback and ideas for its further evolution.
>>>
>>> -- 
>>> Premek Brada (Ing et MSc, PhD)
>>> Lecturer in Software enginering, Webmaster
>>> Department of Computer Science and Engineering
>>> University of West Bohemia, Pilsen, CZ
>>> << brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>
>>>
>
>


-- 
Premek Brada (Ing et MSc, PhD)
   Lecturer in Software enginering, Webmaster
   Department of Computer Science and Engineering
   University of West Bohemia, Pilsen, CZ
   <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>


Re: updating bundle-target mapping

Posted by Premek Brada <br...@kiv.zcu.cz>.
Hi Angelo,

thanks for replying, I serve only as a proxy to the developer :( so I 
have forwarded your suggestions to him and will wait for a response.

Premek


On 3.2.2011 21:39, Angelo van der Sijpt wrote:
> Hi Premek,
>
> Hm, it should be enough programmatically create the links, let the StatefulGatewayRepository generate the new deployment version (you could, for instance, start logging events to see whether that actually happens), and commit the RepositoryAdmin.
>
> You are using the API's provided for this, e.g. the GatewayRepository and friends? Besides, did you remember to either approve the gateway, or to turn on its AutoApprove property?
>
> Angelo
>
>
> On Feb 2, 2011, at 3:35 PM, Premek Brada wrote:
>
>> Hello everybody,
>>
>> while working on an IDE for Apache ACE (see http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an interesting issue: We are able to build a bundle from its Eclipse PDE project, and store the resulting new bundle version into ACE repository (server started off Eclipse). Then we successfully update the bundle-feature-distibution mapping and distribution-target mapping by manipulating the corresponding xml config files, but are unable to find a way to programmatically update the bundle-target mapping config which is (strangely?) also needed. The new version of the bundle therefore cannot be automatically pushed to a configured target.
>>
>> (In other words, we are able to modify these ...
>> http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX
>> http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX
>> ... but don't know how to modify this
>> http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
>> )
>>
>> Currently therefore we resorted to a "solution" to bring up a popup window in Eclipse, instructing the user to run the Web UI and click "retrieve" and "store" so as to update the bundle-target mapping.
>>
>> Surely there must be a better way :) or at least so we think (a "hidden" API or at least a well-defined URL on the repo/server). Could someone enlighten us please?
>>
>> Thanks,
>> Premek
>>
>> PS: If you think an ACE IDE could be helpful to you, please feel free to try it; we need feedback and ideas for its further evolution.
>>
>> -- 
>> Premek Brada (Ing et MSc, PhD)
>>   Lecturer in Software enginering, Webmaster
>>   Department of Computer Science and Engineering
>>   University of West Bohemia, Pilsen, CZ
>>   <<   brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>
>>


-- 
Premek Brada (Ing et MSc, PhD)
   Lecturer in Software enginering, Webmaster
   Department of Computer Science and Engineering
   University of West Bohemia, Pilsen, CZ
   <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>


Re: updating bundle-target mapping

Posted by Angelo van der Sijpt <an...@luminis.eu>.
Hi Premek,

Hm, it should be enough programmatically create the links, let the StatefulGatewayRepository generate the new deployment version (you could, for instance, start logging events to see whether that actually happens), and commit the RepositoryAdmin.

You are using the API's provided for this, e.g. the GatewayRepository and friends? Besides, did you remember to either approve the gateway, or to turn on its AutoApprove property?

Angelo


On Feb 2, 2011, at 3:35 PM, Premek Brada wrote:

> Hello everybody,
> 
> while working on an IDE for Apache ACE (see http://www.assembla.com/wiki/show/eclipse-ace/), we ran into an interesting issue: We are able to build a bundle from its Eclipse PDE project, and store the resulting new bundle version into ACE repository (server started off Eclipse). Then we successfully update the bundle-feature-distibution mapping and distribution-target mapping by manipulating the corresponding xml config files, but are unable to find a way to programmatically update the bundle-target mapping config which is (strangely?) also needed. The new version of the bundle therefore cannot be automatically pushed to a configured target.
> 
> (In other words, we are able to modify these ...
> http://localhost:8080/repository/checkout?customer=apache&name=shop&version=XX
> http://localhost:8080/repository/checkout?customer=apache&name=gateway&version=XX
> ... but don't know how to modify this
> http://localhost:8080/repository/checkout?customer=apache&name=deployment&version=XX
> )
> 
> Currently therefore we resorted to a "solution" to bring up a popup window in Eclipse, instructing the user to run the Web UI and click "retrieve" and "store" so as to update the bundle-target mapping.
> 
> Surely there must be a better way :) or at least so we think (a "hidden" API or at least a well-defined URL on the repo/server). Could someone enlighten us please?
> 
> Thanks,
> Premek
> 
> PS: If you think an ACE IDE could be helpful to you, please feel free to try it; we need feedback and ideas for its further evolution.
> 
> -- 
> Premek Brada (Ing et MSc, PhD)
>  Lecturer in Software enginering, Webmaster
>  Department of Computer Science and Engineering
>  University of West Bohemia, Pilsen, CZ
>  <<  brada at kiv.zcu.cz | www.kiv.zcu.cz/~brada/ | +420-377-63-2435>>
>