Bug 109583 - [buildpath] classpathentry with wildcards
Summary: [buildpath] classpathentry with wildcards
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-15 05:47 EDT by Jilles van Gurp CLA
Modified: 2011-03-29 09:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jilles van Gurp CLA 2005-09-15 05:47:45 EDT
I've tried to use wildcards in the .classpath file like this:
<classpathentry kind="lib" path="web/WEB-INF/lib" including="*.jar"/>

IMHO this should work and it sort of half works in the sense that the project
does now seem to include the jars in the project (in a separate directory). It
doesn't actually put them in the classpath though because I get lots of type not
found errors if I do this.

The reason I want to do this is because I have a complicated project and we keep
the project files in subversion. Every time I add a jar file I need to edit the
.classpath file otherwise everybody who updates has a broken eclipse project. I
have multiple configurations of the project, each with their own eclipse project
files. It would therefore be very nice if the above entry would work as expected.
Comment 1 Olivier Thomann CLA 2006-10-10 11:37:58 EDT
Build path issue.
Comment 2 Philipe Mulet CLA 2008-07-09 10:01:05 EDT
Also see bug 166556