| Composite targlets [message #1724236] |
Mon, 22 February 2016 07:39  |
Eclipse User |
|
|
|
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 11:48  |
| Eclipse User |
|
|
|
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 #1724649 is a reply to message #1724647] |
Thu, 25 February 2016 04:23 |
| Eclipse User |
|
|
|
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.
|
|
|
Powered by
FUDForum. Page generated in 0.26370 seconds
Home