Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 88317 - [jars] problems when building against JARs
Summary: [jars] problems when building against JARs
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M6   Edit
Assignee: Platform-Help-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-17 07:32 EST by DJ Houghton CLA
Modified: 2005-03-18 03:10 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 DJ Houghton CLA 2005-03-17 07:32:22 EST 
Plug-ins which have a custom build.xml file will have to change when we ship
plug-ins as JARs since they have the old JAR names/formats hard-coded in the
build file.

Will add annotation explaining what needs to be done soon...
Comment 1 Pascal Rapicault CLA 2005-03-17 10:50:38 EST 
Where you had a line saying something like:
../org.eclipse.core.runtime/runtime.jar
the line should become
../org.eclipse.core.runtime/@dot

If there were reference to multiple jars, they are collapsed into one line with
@dot on it.

The general rule is
../<pluginNowJared>/<jarname>.jar
../<pluginNowJared>/<jarname2>.jar

becomes
../<pluginNowJared>/@dot
Comment 2 Konrad Kolosowski CLA 2005-03-18 03:10:27 EST 
Thanks.
In N0318, the help webapp compiled.
Following, I have simplified build.xml to 3 entries per jared plugin, for 
example:
../org.eclipse.help/@dot - when plug-in is jarred in a build
../org.eclipse.help - when jarred plug-in imported as binary in the workspace
../org.eclipse.help/bin - when source in the workspace.
I have also coverted to using MANIFEST.MF.