| Strange build path problem [message #72669] |
Thu, 03 July 2003 21:51 |
Eclipse User |
|
|
|
I'm currently evaluating Eclipse by attempting to convert our existing
CW projects and I've run
into a strange (well I think it's strange) problem with the Java Build
Path. This occurs with the
latest 2.1.1 build on Mac OS X with either 1.3.1 or 1.4.1.
The entire project consists of several jar files, including the main jar
with includes two
additional jar files. Typically we would expect that the jar file to be
placed in Library?java/
Extentions, which is where I placed mine once built. The problem is that
once placed there,
Eclipse seems intent on including it as part of the JRE and even though I
subsequently deleted my
jar file, Eclipse still insists that it's part of the JRE. In other words,
the target jar file has now
become a dependency for the project that creates it. Needless to say I
could no longer build
because Eclipse complained that a dependent library was missing, but worse
yet the JRE Edit
dialog on Mac OS X appears to be broken and will not allow editing of the
jars that constitute the
JRE. In fact the window is cut off at the bottom so that the OK and Cancel
buttons (I'm assuming
they should be present since they appear on the Windows version) are
chopped off.
I guess I have two questions. First, does anyone have any ideas why our
projects jar file would
become part of the JRE? Does simply placing it in the system classpath
make it part of the JRE?
Secondly, once there, is there an alternative way of removing it from the
JRE given that the JRE
Edit dialog is broken?
Bob
|
|
|
Powered by
FUDForum. Page generated in 0.02950 seconds
Home