Bug 219879 - A project-scoped runtime-only classpath entries for Run/Debug config
Summary: A project-scoped runtime-only classpath entries for Run/Debug config
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-21 17:53 EST by Raja CLA
Modified: 2008-05-02 12:24 EDT (History)
0 users

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 Raja CLA 2008-02-21 17:53:18 EST 
Currently, Eclipse JDT would create a launch profile for a class when it is run for the first time. The profile adds the project binary artifacts as the classpath of the profile.

It would be nice to be able to be able to specify jars/folders for a project that are purely required for runtime, so it is included whenever a new launch profile is created, but is not used at compile time.

The less desirable alternative is to add these runtime-only jars as a dependency in the project, but every time they change, Eclipse insists on doing a full rebuild. The reason these jars/dirs change is because there are ant targets that (re)generate these glue classes as part of build.
Comment 1 Darin Wright CLA 2008-05-02 12:24:52 EDT 
Marking assigned for consideration post 3.4