Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371032 - Remove com.springsource.* jar and dependencies
Summary: Remove com.springsource.* jar and dependencies
Status: RESOLVED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 371434
Blocks: 341910
  Show dependency tree
 
Reported: 2012-02-08 20:57 EST by Miles Parker CLA
Modified: 2012-02-16 18:45 EST (History)
3 users (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 Miles Parker CLA 2012-02-08 20:57:14 EST 
There are a numbr of dependencies on jars that are actually included in the projects themselves. We have to determine how to replace these.

1. Is there a reason that we can't consumer these as their regular orbit counterparts, e.g.

replacing this classpath depedency

	<classpathentry exported="true" kind="lib" path="lib/com.springsource.json-1.0.1.RELEASE.jar"/>

with:

Required-bundle:
org.json

?

And these:

Bundle-ClassPath: .,
 lib/com.springsource.json-1.0.1.RELEASE.jar,
 lib/com.springsource.org.antlr.jar,
 lib/org.eclipse.virgo.kernel.artifact-2.1.0.RELEASE.jar,
 lib/org.eclipse.virgo.kernel.tools.jar

With whatever dependencies are appropriate?

Or is something non-obvious being accomplished here?

2. Is this:

	<classpathentry kind="con" path="com.springsource.server.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER"/>
	
Serving any purpose?