Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 254571 - Replace jdom.jar dependency inclusion by a dependency to org.jdom provided by Orbit
Summary: Replace jdom.jar dependency inclusion by a dependency to org.jdom provided by...
Status: RESOLVED DUPLICATE of bug 257569
Alias: None
Product: JWT
Classification: SOA
Component: WE (show other bugs)
Version: 0.6.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-07 04:34 EST by Mickael Istria CLA
Modified: 2008-12-05 03:37 EST (History)
1 user (show)

See Also:

Attachments
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 Mickael Istria CLA 2008-11-07 04:34:54 EST 
It would be nice (and improves the integration of JWT in Eclipse community & co) to replace the inclusion of the jdom jar file by a dependency to the org.jdom plugin provided by Orbit.

Those pages give clues about the steps to follow:
* http://wiki.eclipse.org/index.php/Orbit_Faq#How_do_I_work_with_a_bundle_in_Orbit.3F explains how to reference orbit org.jdom plugin at dev time (I tried it, and it's OK)
* http://wiki.eclipse.org/Easy_Bake_Builds_with_Orbit_Bundles : This page describes how to add the dependency to the orbit org.jdom when building JWT. Since I am note really familiar with Eclipse build system, I did not understand everything. It seems like the only thing to do is to add a file names "orbit.map" which only contains the line "plugin@org.jdom=GET,http://download.eclipse.org/tools/orbit/downloads/drops/R20080807152315/bundles/org.jdom_1.0.0.v200806100616.jar" . But I don't where to add it...
Comment 1 Marc Dutoo CLA 2008-11-07 04:58:38 EST 
According to your links and 
http://www.eclipse.org/articles/Article-PDE-Automation/automation.html , map files are specified in the customTargets.xml file when using automated PDE build to build plugins, which we don't use for now (correct me if I'm wrong).

It would however be very interesting to look into automating JWT build using automatedPDE build ("headless" build), to see whether it would help use streamline our builds for Galileo : would it be easier to launch a unified ant build rather than what we do today (package many plugins separately using the PDE packaging features I guess, Florian ?) ?
Comment 2 Mickael Istria CLA 2008-12-05 03:37:10 EST 

*** This bug has been marked as a duplicate of bug 257569 ***