|
|
|
|
Re: Two different behaviours for the same action [message #1101503 is a reply to message #1101470] |
Wed, 04 September 2013 14:45 |
Ed Merks Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
Mathieu,
Comments below.
On 04/09/2013 3:54 PM, Mathieu MONTIN wrote:
> Hi Ed,
> Thank's for your answer.
>
> You suggest that I put a breakpoint to see which URI is being
> processed. But as far as I know (correct me if I'm wrong) one can only
> set breakpoints when running the Eclipse Application at runtime from
> another platfort (the development one).
You can attach a debugger to a running process. I'm not done that
before, so I'm not exactly sure how...
>
> However, when I launch the transformation from this Eclipse,
> everythings works (too) perfectly. Is there any way to set a
> breakpoint when launching a simple Eclipse ? It seems weird.
> I've spent the last 2 hours trying to figure out what's wrong with a
> couple of collegues. This is what we tried :
> - re-generating the plugin .ui from acceleo (the one that provides the
> extension point for the generation)
> - checking each manifest.mf to see if there was any unexported useful
> data
> - trying to manually load the resource package URI in the java file
> generated by acceleo for the transformation (methods registerPackages
> and registerResourceFactory)
> - other simple manipulations.
>
> The point is, the error only occurs when the plugins are exported (via
> an update site) and installed in another platform, which made us
> wonder if it was a conf problem.
> Do you know any configuration adjustment that could differ between the
> runtime version of Eclipse and the deployment one ?
Not really.
> Thank you again for your answer.
Your line numbers for EModelElementImpl don't match up with the 2.9
source, so it's possibly fixed by
https://bugs.eclipse.org/bugs/show_bug.cgi?id=394099 in EMF 2.9...
>
> regards
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03703 seconds