Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Composite targlets
Composite targlets [message #1724236] Mon, 22 February 2016 12:39 Go to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 353
Registered: December 2015
Senior Member
Hi,


I have an application which is based on the eclipse modeling package. So
I have defined a targlet which includes in the modeling package and the
main feature of the application. In addition i have the source locator
that is used to materialize the source code of the application into the
workspace from a git clone.

Now, there are several addon features, for which I would also like to
provide .setup files. Somebody who likes to work on an addon doesn't
necessarily need to work with the application sources. Ideally, these
..setup files would define a targlet that includes the targlet of the
main application + a source locator for the addon source code + an
update site location for the main application feature. (In the addon
case I want oomph to pull the addon sources of the git clone, and the
application from a p2 repo)

How can I reuse the application .setup targlet in such a case?

Felix
Re: Composite targlets [message #1724271 is a reply to message #1724236] Mon, 22 February 2016 16:48 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31243
Registered: July 2009
Senior Member
Felix,

Comments below.

On 22.02.2016 13:39, Felix Dorner wrote:
> Hi,
>
>
> I have an application which is based on the eclipse modeling package.
> So I have defined a targlet which includes in the modeling package and
> the main feature of the application. In addition i have the source
> locator that is used to materialize the source code of the application
> into the workspace from a git clone.
>
> Now, there are several addon features, for which I would also like to
> provide .setup files. Somebody who likes to work on an addon doesn't
> necessarily need to work with the application sources. Ideally, these
> .setup files would define a targlet that includes the targlet of the
> main application + a source locator for the addon source code + an
> update site location for the main application feature. (In the addon
> case I want oomph to pull the addon sources of the git clone, and the
> application from a p2 repo)
>
> How can I reuse the application .setup targlet in such a case?
Yes, I think so, if I understand correctly. In general, all the
targlets are composed and are resolved as a single "p2 resolution".
During that process, if any IU resolves to an IU locatable via a source
locator, the source project for that IU will be imported into the
workspace. Similarly, any IU that resolves to a "binary" IU in any p2
repository will be included in the PDE target platform. Note that this
implies that an IU may be resolved in both source and binary form, in
which case it's possible to close the source project so that the other
IUs that require it resole to the binary IU in the target platform.
>
> Felix
Re: Composite targlets [message #1724298 is a reply to message #1724271] Mon, 22 February 2016 21:38 Go to previous messageGo to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 353
Registered: December 2015
Senior Member
>> How can I reuse the application .setup targlet in such a case?
> Yes, I think so, if I understand correctly. In general, all the
> targlets are composed and are resolved as a single "p2 resolution".

Ok, but what are "all" the targlets? If I define an addon.setup, how do
I "include" the targlets from the application.setup in it?

Felix
Re: Composite targlets [message #1724478 is a reply to message #1724298] Wed, 24 February 2016 07:55 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6501
Registered: July 2009
Senior Member
Am 22.02.2016 um 22:38 schrieb Felix Dorner:
>>> How can I reuse the application .setup targlet in such a case?
>> Yes, I think so, if I understand correctly. In general, all the
>> targlets are composed and are resolved as a single "p2 resolution".
>
> Ok, but what are "all" the targlets?
The targlets defined in all applicable (i.e., reachable, enabled, and unrestricted) TargletsTasks defined in:

1) user.setup
2) installation.setup
3) the ProductVersion referenced from installation.setup
4) workspace.setup
5) all Streams referenced from workspace.setup
6) the parent scopes of all of the above


> If I define an addon.setup, how do I "include" the targlets from the application.setup in it?
There's no way for a setup file to include other setup files. Only the user can include the streams of project setup
files into his workspace.setup file. The "Projects into Workspace" import wizard is used for that.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: Composite targlets [message #1724644 is a reply to message #1724478] Thu, 25 February 2016 08:45 Go to previous messageGo to next message
Felix Dorner is currently offline Felix DornerFriend
Messages: 353
Registered: December 2015
Senior Member
On 24-Feb-16 08:55, Eike Stepper wrote:
> Am 22.02.2016 um 22:38 schrieb Felix Dorner:
>>>> How can I reuse the application .setup targlet in such a case?
>>> Yes, I think so, if I understand correctly. In general, all the
>>> targlets are composed and are resolved as a single "p2 resolution".
>>
>> Ok, but what are "all" the targlets?
> The targlets defined in all applicable (i.e., reachable, enabled, and
> unrestricted) TargletsTasks defined in:
>
> 1) user.setup
> 2) installation.setup
> 3) the ProductVersion referenced from installation.setup
> 4) workspace.setup
> 5) all Streams referenced from workspace.setup
> 6) the parent scopes of all of the above

Aha. Is there maybe an example in the oomph catalog where I can see how
such combined targlet tasks work together?
Re: Composite targlets [message #1724647 is a reply to message #1724644] Thu, 25 February 2016 09:10 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6501
Registered: July 2009
Senior Member
Am 25.02.2016 um 09:45 schrieb Felix Dorner:
> Aha. Is there maybe an example in the oomph catalog where I can see how such combined targlet tasks work together?
The Papyrus setup and its subprojects have quite some TargletsTasks.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


Re: Composite targlets [message #1724649 is a reply to message #1724647] Thu, 25 February 2016 09:23 Go to previous message
Felix Dorner is currently offline Felix DornerFriend
Messages: 353
Registered: December 2015
Senior Member
On 25-Feb-16 10:10, Eike Stepper wrote:
> Am 25.02.2016 um 09:45 schrieb Felix Dorner:
>> Aha. Is there maybe an example in the oomph catalog where I can see
>> how such combined targlet tasks work together?
> The Papyrus setup and its subprojects have quite some TargletsTasks.

Thank you, I will check them out.
Previous Topic:artificial_root not found
Next Topic:How to enforce ordering of Oomph steps?
Goto Forum:
  


Current Time: Thu Jul 09 19:10:05 GMT 2020

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

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

Back to the top