|
| Re: [XCore] XCore generates/adds .org.eclipse.jdt.core.external.folders in MANIFEST.MF [message #1729590 is a reply to message #1729571] |
Fri, 15 April 2016 12:38   |
Eclipse User |
|
|
|
Regent,
Comments below.
On 15.04.2016 16:55, Regent LArcheveque wrote:
> Hi,
> I have a strange situation and I am really stuck. We have a series of
> APP_CORE bundles with XCore meta-models. I created a EXTRA bundle
> with a new XCore model that makes use of the APP_CORE XCore
> meta-models. Everything works fine if we are in the same workspace.
> However, If we build APP_CORE bundles P2 repository and if we have a
> workspace with the EXTRA bundle only, I got a strange behaviour when
> the EXTRA meta-model is re-generated by XCore / EMF.
So the dependencies are in the target platform in this case, not in the
workspace. There's no self hosting involved? How is the target
platform populated?
> Indeed, the EXTRA bundle MANIFEST.MF gets an additional dependency in
> the Require-Bundle section:
> org.eclipse.jdt.core.external.folders;visibility:=reexport,
That sounds like the IDE of the special invisible project that JDT
creates to link in external jars and folders such that they are
logically part of the workspace. But it's hard to imagine how that
project dependencies is something that EMF uses in this case.
>
> A little note, some APP_CORE bundles contain JET templates and use the
> following "Eclipse-BundleShape: dir" directive in their MANIFEST.MF
I'm not sure what that means and I've never tried it. I'm not sure why
that's needed... Is the problem only reproducible in that case?
In the worst case, you can change the Update Classpath property of the
GenModel (via an annotation of course) to false, and then the
MANIFEST.MF won't be touched during regeneration.
Otherwise, I'll need all the steps/samples to reproduce the problem...
>
> Any idea?
>
> Thanks ;)
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03070 seconds