Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » TargetDefinitionGenerator output missing features and extra locations
TargetDefinitionGenerator output missing features and extra locations [message #1742049] Wed, 17 August 2016 21:57 Go to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 325
Registered: December 2015
Senior Member
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

2. I expected the target file to contain exactly the locations defined
in the targlet, but there appear 2 additional locations:

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
Re: TargetDefinitionGenerator output missing features and extra locations [message #1742050 is a reply to message #1742049] Wed, 17 August 2016 21:59 Go to previous messageGo to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 325
Registered: December 2015
Senior Member
On 17-Aug-16 23:57, Felix Dorner wrote:
> I attached a screenshot of the targlet tree if you don't want to open
> the setup.
Now...
  • Attachment: targlets.png
    (Size: 62.67KB, Downloaded 59 times)
Re: TargetDefinitionGenerator output missing features and extra locations [message #1742051 is a reply to message #1742049] Thu, 18 August 2016 05:56 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6487
Registered: July 2009
Senior Member
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
>


Re: TargetDefinitionGenerator output missing features and extra locations [message #1742239 is a reply to message #1742049] Thu, 01 September 2016 05:21 Go to previous message
Felix Dorner is currently offline Felix DornerFriend
Messages: 325
Registered: December 2015
Senior Member
Ok thank you Eike.
Previous Topic:Feature Request: Import a "setup fragment"
Next Topic:How to import .epf file for SVN checkout
Goto Forum:
  


Current Time: Mon Apr 06 21:22:15 GMT 2020

Powered by FUDForum. Page generated in 0.07134 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top