|
Re: [Acceleo] store trace information [message #547359 is a reply to message #546785] |
Fri, 16 July 2010 13:00 |
|
Hi,
I don't think that it is possible (except if you want to build your own traceability engine, which you can if you link it to the engine with the org.eclipse.acceleo.engine.creator extension point).
But I'm not 100% sure on this, the developer who created this is on holiday, you will have to wait for his return to have more details (in two weeks)
Stéphane Bégaudeau, Obeo
|
|
|
Re: [Acceleo] store trace information [message #549429 is a reply to message #546785] |
Mon, 26 July 2010 15:27 |
|
This is a multi-part message in MIME format.
--------------090301070701020407050909
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Max,
What exactly do you mean by "trace information" ? Traceability from an
EObject to its generated text bits?
If yes, you could take a look at the class
org.eclipse.acceleo.internal.ide.ui.views.result.AcceleoResu ltContent
which is the listener in charge of feeding traceability information to
the result view. You might also want to take a look at
org.eclipse.acceleo.engine.event.IAcceleoTextGenerationListe ner which is
the interface of our generation listeners.
Laurent Goubet
Obeo
Max Bureck wrote:
> Hello,
>
> is it possible to get the trace information from an Acceleo generator
> run (started from Java in an Eclipse plug-in) and somehow store this
> information? And is it possible to feed this information to the Result
> View later on?
>
> Max
--------------090301070701020407050909
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------090301070701020407050909--
|
|
|
|
|
Re: [Acceleo] store trace information [message #550179 is a reply to message #549965] |
Thu, 29 July 2010 13:09 |
|
This is a multi-part message in MIME format.
--------------060006050504000106000008
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Max,
You shouldn't have to call that code for yourself; except in standalone.
How are you launching your generation? You need to tick the "contribute
traceability information to the result view" checkbox on the launch
config configuration page for now (until we find a more elegant way of
enabling traceability).
Laurent Goubet
Obeo
Max Bureck wrote:
> OK, I have another question:
> How do I make the engine create traceability information? I implemented
> the IAcceleoTextGenerationListener, but the method
> getTraceabilityInformation on
> org.eclipse.acceleo.engine.event.AcceleoTextGenerationEvent instances
> return null. In the Eclipse launcher code I found the following method:
> private void switchTraceability(boolean activate) {
> new
> InstanceScope().getNode(AcceleoEnginePlugin.PLUGIN_ID).putBo olean(
> "org.eclipse.acceleo.traceability.activation",
> activate); //$NON-NLS-1$
> }
> But that snip didn't help.
--------------060006050504000106000008
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------060006050504000106000008--
|
|
|
Powered by
FUDForum. Page generated in 0.03786 seconds