Targlets: How do I require everything found in the referenced repositories? [message #1761247] |
Tue, 09 May 2017 07:05  |
Eclipse User |
|
|
|
I'm trying to set up our current workflow with Oomph. For every project, we have a .target file that contains the dependencies needed for this project. Because these are frequently outdated (due to updates of internal features), we often have to edit the target platform to include the latest version of our features. I hope to fix this with targlets.
My goal is to specify the repositories and require all features that are available. I tried the following XML:
<?xml version="1.0" encoding="UTF-8"?>
<setup.targlets:TargletTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup.targlets="http://www.eclipse.org/oomph/setup/targlets/1.0"
xsi:schemaLocation="http://www.eclipse.org/oomph/setup/targlets/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/SetupTarglets.ecore">
<targlet name="MyTarglet"
activeRepositoryList="Default">
<requirement
name="*"/>
<repositoryList
name="Default">
<repository
url="http://packagedrone.local/p2/Feature_one"/>
<repository
url="http://packagedrone.local/p2/Feature_two"/>
</repositoryList>
</targlet>
</setup.targlets:TargletTask>
I've seen the * requirement in the Oomph.setup so I expected it to work. But the installed target platform is empty! When I edit the target definition, the content tab stays empty. What did I miss? How can I fix this?
Another question: Will the targlets only include the latest version? We need to import outdated versions, too.
Thanks!
|
|
|
|
|
Re: Targlets: How do I require everything found in the referenced repositories? [message #1761436 is a reply to message #1761348] |
Thu, 11 May 2017 02:59  |
Eclipse User |
|
|
|
The use case for including all features in an update site seems to me much more questionable than the use case for requiring all things in git repository. There are very few update sites I can think of where including everything in the update site in the target platform makes significant sense. A site either contains way too many things (e.g., a release train repository), or it contains a small number of root features (e.g., an SDK or an "all" feature), in which case you can include that. With the repository explorer you can easily inspect any update site and drag and drop requirements into targlets. Doing this unselectively seems not generally useful to me.
|
|
|
Powered by
FUDForum. Page generated in 0.04712 seconds