Home » Modeling » M2T (model-to-text transformation) » [Acceleo] Launch as Acceleo Plugin does not work but Java Runner works
|
Re: [Acceleo] Launch as Acceleo Plugin does not work but Java Runner works [message #694096 is a reply to message #694088] |
Thu, 07 July 2011 19:27 |
Ed Willink Messages: 7680 Registered: July 2009 |
Senior Member |
|
|
Hi Matt
You might have a case of meta-model schizophrenia; the same meta-model
loaded twice, so the transformation fails to match EClasses.
If you have any of your meta-models installed as plugins and loaded as
projects, try closing the projects.
Regards
Ed Willink
On 07/07/2011 20:15, Matt Biehl wrote:
> I need to lauch an Acceleo transformation from my own Plugin in
> Eclipse, but this does not work, it fails to produce output. There are
> no error messages on the console.
>
> Interestingly the same transformation works in other setups, which I
> describe in the following:
>
> When I launch Acceleo from the UI, it runs perfectly as Java
> Application, but not as Acceleo Plugin (fails to produce output, no
> message in the Console).
> When I launch Acceleo programmatically from a POJO Java Application it
> works. When I launch Acceleo programmatically from my own Plugin in
> Eclipse it does not work (fails to produce output, no message in the
> Console).
> How do I get it to work? Where could be the problem?
>
> Thanks,
> Matt
|
|
| | | | | | | |
Re: [Acceleo] Launch as Acceleo Plugin does not work but Java Runner works [message #695013 is a reply to message #694909] |
Sun, 10 July 2011 17:38 |
Ed Willink Messages: 7680 Registered: July 2009 |
Senior Member |
|
|
Hi Matt
335764 was about finding too much, so I don;t think it's your problem,
but you could try both binary and ASCII EMTL to see if it helps.
You may think "The registered package has the same URI as the unresolved
proxy" but even when no magic typos are involved that is still only part
of the story. If there is indeed an unresolved proxy, there is no
substitute for single stepping the EcoreUtil.resolveProxy failure to get
an insight into what actually failed.
URI bugs, although usually user errors, are too common and too difficult
to improve. Acceleo 3.1 has significantly improved but as Bug 335764
indicates a Microsoft-style help 90% of the time but hinder 10% of the
time is no substitute for a sound documrnted resolution algorithm with
assoiciated diagnosis capabilities.
Today, you have to be an expert on debugging EcoreUtil.resolveProxy to
make progress on these issues. The Indigo implementation is slightly
restructured to eliminate a redundant recursion and facilitate debugging.
Regards
Ed Willink
On 10/07/2011 08:47, Matt Biehl wrote:
> Hi,
>
> I tried that. I register the package in Generate.registerPackages().
> The registered package has the same URI as the unresolved proxy.
>
> Maybe this issue is related to Bug 335764
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=335764)?
>
>
> Best Regards,
> Matt
|
|
| | | |
Goto Forum:
Current Time: Wed Dec 04 13:48:05 GMT 2024
Powered by FUDForum. Page generated in 0.27765 seconds
|