|
Re: Targlets and p2 profiles [message #1797568 is a reply to message #1797468] |
Thu, 01 November 2018 20:23 |
|
Hi Lasse,
I can't resist to say that not increasing the version of an IU when new content is released is a no no. You should really talk to your vendor in the first place. Otherwise profile update just can't work; neither in the target platform of your IDE, nor in the installations of your application (i.e., self update). I mean, it's not just a problem of the pool and its artifacts.
You could try to mirror your vendor's p2 repository and post process it to fix their mess. But then you could lose your vendor's signatures.
You can configure Oomph to use a separate pool and/or agent for all targlet containers in all your workspaces. I haven't tried it, but if you want to take this approach I strongly recommend to use a separate agent as well (because of the profile problems I mentioned above). The steps are:
1) Create a new agent and pool. In your IDE have a look at Preferences | Oomph | Bundle Pools. The Eclipse Installer also provides "Manage Bundle Pools..." actions.
2. Add the following lines to the file {user.home}/.eclipse/org.eclipse.oomph.p2/defaults.info and replace {new.agent} with the new agent's location.
org.eclipse.oomph.targlets.core={new.agent}/pool
org.eclipse.oomph.targlets.core\:agent={new.agent}
I'm not quite sure how badly existing target platforms are impacted by this treatment.
Cheers
/Eike
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Re: Targlets and p2 profiles [message #1797592 is a reply to message #1797568] |
Fri, 02 November 2018 11:53 |
Lasse Knudsen Messages: 3 Registered: October 2018 |
Junior Member |
|
|
Hi Eike,
thx for your respose. I totally agree with your "no, no" :-) But that is not an option right now and might only work in the upcoming releases.
The option with the targlets pool and agent sounds interesting.
* Is it possible to define an agent and pool during the installation so that I don't have to set it manually?
* Is it possile to link targlet configurations via href in the projectCatalog? I would like to generate the targlet tasks on the build server with all URLs to the p2 repositories.
* Currently we are generating target platforms but I would like to use targlets instead.
Regards
Lasse
[Updated on: Fri, 02 November 2018 12:23] Report message to a moderator
|
|
|
Re: Targlets and p2 profiles [message #1797603 is a reply to message #1797592] |
Fri, 02 November 2018 14:50 |
|
The defaults.info file is a registry for machine-wide, per client, default agent locations. If you register a separate agent location for the Targlets Core client in that file then there's no need anymore to select anything else during an istallation or update. Note again, that you can't register per installation defaults. Of course you can try to change the defaults.info file through a setup task during the bootstrap trigger. ResourceCreationTask or TextModifyTask could do the trick.
Perhaps it's possible to use a containment proxy to factor a task in its own separate resource. At least SetupTaskContainer.getSetupTasks() is modeled with resolveProxies="true". But I haven't tried it out and am not sure how the complex setup machinery would react. I'll ask Ed to comment, too.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03753 seconds