Bug 172118

Summary:

[classpath] Extension point for plugin to contribute libraries used in class path.

Product:

[Eclipse Project] JDT

Reporter:

John Willson <johnwillsons>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

NEW ---

QA Contact:

Severity:

enhancement

Priority:

Version:

3.3

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
plugin providing pluggable library extension support	none
An example of plugin providing library	none

Description John Willson

2007-01-30 03:27:32 EST

There is extension point for plugin to contribute classpath container. But in many cases, plugin just want to provide set of jars for use as a library. JUnit can be a best example.
So we need a extension point for plugin to contribute libraries using just description.

Comment 1 John Willson

2007-01-30 03:32:22 EST

Created attachment 57774 [details]
plugin providing pluggable library extension support

This contains an annotation based configuration to objects library.
Anyway, the ideas are there.

Comment 2 John Willson

2007-01-30 03:37:27 EST

Created attachment 57775 [details]
An example of plugin providing library

This is an example of plugin providing tapestry libraries.

Comment 3 John Willson

2007-01-30 03:41:26 EST

The attachment plugin only support library classpath container, but it's easy to add UI support to select a provided library. 
Anyway you need to add following in .classpath file to see it acting.
<classpathentry kind="con" path="org.eclipse.jdt.library.pluggable.classpathContainerInitializer/org.apache.tapestry/tapestry5"/>