Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330351

Summary: Acceleo as a Java Standalone Library
Product: [Modeling] Acceleo Reporter: Cedric Brun <cedric.brun>
Component: CoreAssignee: Project Inbox <acceleo-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: stephane.begaudeau
Version: 3.0.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Screenshot showing the Java classpath library wizard none

Description Cedric Brun CLA 2010-11-16 09:04:00 EST 
Right now I have two choices : either I'm writting an Eclipse plugin and then I add a plugin dependency in the Manifest.MF of my generator project, or I'm designing a standalone generator and then I have to copy the Acceleo jars into my project and refers to them through the classpath management.

Another way - less error prone - of writing down standalone generator could be to associate an "Acceleo" library with my project just like one can do with JUnit. Then the installed jars would be used directly.

I *assume* this can be done in Eclipse as JUnit provides such a library.
Comment 1 Cedric Brun CLA 2010-11-16 09:05:06 EST 
Created attachment 183219 [details]
Screenshot showing the Java classpath library wizard
Comment 2 Stephane Begaudeau CLA 2011-04-21 09:51:34 EDT 
>>> I *assume* this can be done in Eclipse as JUnit provides such a library.
Well, it can indeed be done: http://twitter.com/#!/sbegaudeau/status/61060617519366146

The fix has been contributed on HEAD, it will be available in Acceleo 3.1.0M7 next month.