|
| Re: Composite targlets [message #1724271 is a reply to message #1724236] |
Mon, 22 February 2016 16:48   |
 Ed Merks
Messages: 33140
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
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
| Re: Composite targlets [message #1724478 is a reply to message #1724298] |
Wed, 24 February 2016 07:55 |
|
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
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03504 seconds
] 
Search
Help
Register
Login
Home
