Bug 17547 - [build path] Should be able to copy & paste external JARs
Summary: [build path] Should be able to copy & paste external JARs
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2002-05-23 20:26 EDT by Peter Burka CLA
Modified: 2013-02-01 07:16 EST (History)
2 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 Peter Burka CLA 2002-05-23 20:26:59 EDT 
F1

In the Packages view, I should be able to copy an external JAR (or variable) 
from one project and paste it into another.

As it is right now I have to add the same JAR to each project, which is a 
fairly involved process. The only thing that I can do to external JARs from 
the Packages view is delete them.
Comment 1 Erich Gamma CLA 2002-05-24 19:53:14 EDT 
manipulation of the build class path in the packages view by direct 
manipulation of JARs got deferred to after 2.0
Comment 2 Dirk Baeumer CLA 2003-04-28 06:03:04 EDT 
Chaning state from assigned later to resolved later. Assigned later got 
introduced by the last bug conversion and is not a supported Eclipse bug state.
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:36:46 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.
Comment 4 Juergen Weber CLA 2011-07-12 02:44:00 EDT 
This would be a useful feature, pity that it is wontfixed.
E.g. you have a project linking the external JBoss jars and would have these jars in the build path of another project, it would be natural to just copy them in the Libraries tab of one project and pasting them into the Libraries tab of the other project.
Comment 5 Markus Keller CLA 2011-08-03 10:51:28 EDT 
We currently don't plan to work on this, but we would accept a good quality patch.
Comment 6 Juergen Weber CLA 2013-02-01 07:16:45 EST 
An effective workaround is to close the corresponding projects and copy the <classpathentry> elements in .classpath