Bugzilla – Full Text Bug Listing
| Summary: | Acceleo headless builder | ||
|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Nicolas Bros <nicolas.bros> |
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cedric.brun, laurent.goubet, stephane.begaudeau, thomas |
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 343238, 322345 | ||
|
Description
Nicolas Bros
(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. 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 :). (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. 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 |