|
|
Re: TargetDefinitionGenerator output missing features and extra locations [message #1742051 is a reply to message #1742049] |
Thu, 18 August 2016 05:56 |
|
Hi Felix,
Comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 17.08.2016 um 23:57 schrieb Felix Dorner:
> Hi,
>
> I am testing the target file generator annotation on the Capella systems modeling setup which you can find here:
>
> https://git.polarsys.org/c/capella/capella.git/tree/releng/plugins/org.polarsys.capella.core.releng/oomph/Capella.setup
>
> I attached a screenshot of the targlet tree if you don't want to open the setup.
>
> In the setup model there is a Targlet named "Capella Dependencies" for which I'd like to generate a .target definition
> file. When I add the generator annotation to this targlet (haven't committed yet so you won't see it in git), the
> attached .target file is generated when the setup is performed.
>
> Now when I compare the targlet and the .target file, I see two things that I don't understand:
>
> 1. The target file contains not all features mentioned in the targlet, e.g. the targlet includes
> org.eclipse.emf.transaction but it is missing in the .target
Unless you specify "generateImplicitUnits=true" on the annotation the generator creates a minimal set of requirements. I
assume that the org.eclipse.emf.transaction feature is included transitively (aka "implicitely") through some other
feature. You can verify this assumption by activating the resulting .target file and inspect the respective target
definition content.
>
> 2. I expected the target file to contain exactly the locations defined in the targlet, but there appear 2 additional
> locations:
The target definition generator uses the actual resolution of all merged targlet *tasks* with all their targlets as a
basis to approximate a good .target file for the annotated targlet. Sometimes a low-level dependency (often some Orbit
stuff) are present in multiple repositories and then it's up to the generator to pick a random repository. You can
optimize the .target file in this regard by specifying "preferredRepositories=url1,url2,..." on the annotation.
>
> a)
> https://hudson.polarsys.org/capella/view/Capella-master/job/capella-master/lastSuccessfulBuild/artifact/result/publish/org.polarsys.capella/site.p2
>
>
> is not set in the "Capella Dependencies" targlet, but in one of its siblings.
>
> b)
> http://download.eclipse.org/eclipse/updates/4.5
>
> Which comes from the "Eclipse Platform" targlet which isn't even defined in my .setup but somewhere up.
>
>
> Anyone knows what's going on here?
>
> Thanks,
> Felix
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
Powered by
FUDForum. Page generated in 0.04655 seconds