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

Bug 360233

Summary:	WikiText Ant tasks should be placed in separate bundles
Product:	z_Archived	Reporter:	Torkild Resheim <torkildr>
Component:	Mylyn	Assignee:	Torkild Resheim <torkildr>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	greensopinion, steffen.pingel
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Torkild Resheim

2011-10-07 09:44:59 EDT

This way it would be possible to use the tasks from within Eclipse and run the Ant scripts using the Worbench JRE. As the PDE developer guide states:

bq..  

Ant tasks and types must be loaded by an Ant classloader instead of a plug-in classloader. This can cause problems when developing and testing new tasks and types to be run in the same VM as Eclipse. To avoid these issues, it is necessary to store the tasks and types in a location that is not visible to any plug-in classloader.
 
* Contributed Ant tasks or types should be defined in their own source folder within a plug-in (i.e. separate from the source folders containing regular plug-in classes)
* Each source folder containing the Ant tasks and types should have its own output location that does not overlap with the output location of the regular plug-in classes.

Comment 1 Steffen Pingel

2011-10-07 09:50:50 EDT

We have had quite a bit of discussion around that on bug 273325 and related bugs. I believe in the end we weren't able to make it work reliable so ant tasks could be invoked from Eclipse and standalone builds and dropped support for contributing ant tasks to Eclipse.

Comment 2 Torkild Resheim

2011-10-07 10:07:00 EDT

Thanks Steffen. I thought I read something about this earlier but I could not find it when searching. Maybe something has changed as I'm quite able to run the EPUB Ant task from within Eclipse. However I've made sure that a different classloader is used - by placing the Ant code in a different bundle than the related plug-in code.

Comment 3 Steffen Pingel

2011-10-07 11:38:41 EDT

Interesting. Maybe that's a feasible solution for WikiText as well.

Comment 4 David Green

2011-10-07 12:27:01 EDT

A motivator for keeping these classes in a single bundle was to maintain backward compatibility with existing stand-alone applications (ie: not modifying the classpath by adding additional jars).  It's possible that this motivator is no longer relevant.

Comment 5 Torkild Resheim

2011-10-24 16:12:04 EDT

I guess for some it's still relevant. So the issue should be inspected further. Nevertheless I think it would be quite useful being able to run this tasks with an Eclipse environment. I'll have a look.

Comment 6 David Green

2013-08-02 12:43:09 EDT

Closed as part of backlog clean-up.  Please re-open if you'd like to see this revisited, perhaps with a contribution.