Hi, Céline,
This is exactly the problem with having nested projects in the Git repository. I have “org.eclipse.papyrusrt.targetplatform” imported into my workspace as a project in its own stead, as will anyone else that uses the Oomph Setup model to provision their workspaces. The URI that you quote will only work for you in your workspace.
We really need everybody on the team to work with a consistent configuration of workspace projects. Please import the org.eclipse.papyrusrt.targetplatform project as a top-level project in your workspace and don’t change the include URI in the TPD file (or, change it to a relative URI based on this correct project path).
On 29 June, 2016 at 09:23:34, Céline JANSSENS (celine.janssens@xxxxxxxxxxx) wrote:
Hi Christian,
Thank for the hint.
Actually the
"platform:/resource/org.eclipse.papyrusrt.targetplatform/... "
didn't work because my workspace needs the full path from the root
project. So the following path works:
"platform:/resource/org.eclipse.papyrus-rt/org.eclipse.papyrusrt.targetplatform/..."
Nevertherless, I modified the targetplatform name folder into
project folder and keep the relative path as you suggested to
remain align with the other projects.
Note: This will be available in the build_process branch
(for the moment)
Thanks
Céline
Le 29/06/2016 à 14:38, Christian Damus
a écrit :
Hi, Céline,
This editor looks to me like it is Xtext-based, so references are
ultimately implemented in EMF as relative URIs, and
platform:/resource scheme would be most appropriate in the
workspace context. And usually, in EMF, whenever relative
URIs can be used, they are preferred for portability.
However,
the example that you provide of a relative URI looks quite wrong to
me: the “targetplatform” segment is the name of the folder in
the Git repository that stores the
“org.eclipse.papyrusrt.targetplatform” project. It is
unfortunate to begin with that the folder name differs from the
project name. Moreover, Eclipse is content with the project
name in any given workspace actually being different to the project
name written in the .project file. So, as the absolute URI in
the second snippet doesn’t resolve for you, I suspect that this
project in your workspace is not named
“org.eclipse.papyrusrt.targetplatform" but rather simply
“targetplatform”. Is that correct? If so, it would be
better that you rename the project in your workspace to use the
same name as everyone else (the name in the .project file).
In the longer term, it would be nice to revert these references to
the relative form but, of course, using the canonical
“org.eclipse.papyrusrt.targetplatform” project name.
HTH,
Christian
On 29 June, 2016 at 05:37:35, Céline JANSSENS
(celine.janssens@xxxxxxxxxxx)
wrote:
Hello everyone,
Using the Target Platform definition plugin from Obeo, I
created some .tpd to define the Target Platform definition, and
then generate the target platform through the
menu:
In those .tpd you can include other .tpd using the key word
"include". (see more [1] )
In Codegen, I see that the relative path:
has been modified the 2016-06-03 into:
But in this case when I generate the Target Platform, it doesnt
include this pointed tpd. And I have missing dependencies
around the plugin from the target included.
What is the benefit of this pattern then ?
Thank you
Céline
[1] - https://github.com/mbarbero/fr.obeo.releng.targetplatform
--
| |
Céline
JANSSENS
Software
Engineer
+33 (0)2 44 47 23 23
|
| |
Mail : cej@xxxxxxxxxxx
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
--
| |
Céline JANSSENS
Software Engineer
+33 (0)2 44 47 23 23
|
| |
Mail : cej@xxxxxxxxxxx
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
