Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Install dependency to external p2 site

Thanks for the hint. I added a repository-reference to my category.xml file. It works when I export this locally using the deployable features export wizard. Tycho however does not pick up that entry and does not add those references to content.xml. Do you know how to do this or is this something for the tycho list?

thanks
Christian

Am 02.02.2016 um 10:54 schrieb Mickael Istria:
On 02/02/2016 10:39 AM, Christian Pontesegger wrote:
For EASE we have some optional features available on our p2 site which require Nebula components. So when a user selects such a feature without having the nebula update site configured, he will get an error message. What I want to do now is to configure my feature and define the remote nebula update site that is needed during installation. Is there a way to configure such a step? Eventually touchpoint actions could work. There exists an addRepository action. But from its documentation it seems it will only work for future updates.
Have you considered using repository references in your p2 metadata to link the Nebula site from the EASE one? See https://bugs.eclipse.org/bugs/show_bug.cgi?id=436318 .
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


Back to the top