Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322635 - Acceleo headless builder
Summary: Acceleo headless builder
Status: CLOSED WONTFIX
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: All All
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 343238 322345
  Show dependency tree
 
Reported: 2010-08-13 05:59 EDT by Nicolas Bros CLA
Modified: 2014-04-25 04:16 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bros CLA 2010-08-13 05:59:34 EDT
AcceleoBuilder is defined in a UI plug-in. To be usable in a headless context, it should be defined in a "core" plug-in (no UI dependencies), and installable from a "core"-only feature.
Comment 1 Stephane Begaudeau CLA 2010-08-13 06:12:13 EDT
(In reply to comment #0)
> AcceleoBuilder is defined in a UI plug-in. To be usable in a headless context,
> it should be defined in a "core" plug-in (no UI dependencies), and installable
> from a "core"-only feature.

Right now the builder is defined in the UI plug-in because all our core plug-ins are stand alone components and therefore have no dependencies with the Eclipse workspace or the Eclipse IResource system.

I don't know if we will move the builder to another place for this bug or not, or if we will do something else but we won't move it to one of our core plug-ins (org.eclipse.acceleo.parser, org.eclipse.acceleo.engine, org.eclipse.acceleo.common) because they would need a dependency with org.eclipse.core.resource and we won't accept to lose the stand alone advantage of our core plug-ins for that.
Comment 2 Laurent Goubet CLA 2010-08-13 06:41:22 EDT
I don't know whether it is even possible to get the builder to be run headless (even if we move it to a "non UI" plugin), but it is definitely worth a try.

However, I don't believe we'll have time to try and make this change before M2. If you need this done quickly, the gist of it : create a new plugin "org.eclipse.acceleo.ide" that will have no dependency on "ui" plugins, move the AcceleoBuilder class in this new plugin, move all dependencies of the AcceleoBuilder to o.e.a.ide, deprecate the old builder so that the headless one is used instead (as it is public API).

Let me know if this _is_ something you need done quick and you have trouble moving the builder to an headless plugin :).
Comment 3 Nicolas Bros CLA 2010-08-13 07:14:11 EDT
(In reply to comment #2)
> Let me know if this _is_ something you need done quick and you have trouble
> moving the builder to an headless plugin :).

This is not urgent, as we have a workaround, but it of course would be much better to be able to call the builder during the headless build.
Comment 4 Cedric Brun CLA 2014-04-25 04:16:47 EDT
Now that Acceleo provides a maven/tycho builder [1] I guess this is no more relevant.

Feel free to reopen if you have a specific use case which is not covered by this.

[1] https://wiki.eclipse.org/Acceleo/Maven