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

Bug 371032

Summary: Remove com.springsource.* jar and dependencies
Product: [RT] Virgo Reporter: Miles Parker <milesparker>
Component: toolingAssignee: Project Inbox <virgo-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: eclipse, leo.dos.santos, mlippert
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Bug Depends on: 371434    
Bug Blocks: 341910    

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?