Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330351 - Acceleo as a Java Standalone Library
Summary: Acceleo as a Java Standalone Library
Status: CLOSED FIXED
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:
 
Reported: 2010-11-16 09:04 EST by Cedric Brun CLA
Modified: 2011-04-21 09:51 EDT (History)
1 user (show)

See Also:

Attachments
Screenshot showing the Java classpath library wizard (118.09 KB, image/png)
2010-11-16 09:05 EST, Cedric Brun CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.