Managing platform specific classpath entries [message #146656] |
Mon, 20 October 2003 12:15  |
Eclipse User |
|
|
|
Hi,
Up till now I have been using XML includes in the .classpath xml file of
the Java projects, which includes an xml file ignored by CVS, in order
to manage platform specific classpath entries (eg. Linux-gtk users need
swt-pi.jar and Windows developers couldn't care less :).
The problem is, that Eclipse, at least version 2.1.1 seems to parse the
..classpath file and then substitute .classpath with the result of the
parsing, which seems odd to me. As a result, all the platform specific
classpath entries wind up in .classpath, hence in CVS, and Windows
developers have to care about an undeclared variable SWT_PI in their
projects :( ...
Is there some way to change this behaviour ? Should I file a bug ?
Or could you recommend to me other techniques to separate out these
platform specific classpath entries and leave them out of cvs ?
regards,
Vincent
|
|
|
|
Re: Managing platform specific classpath entries [message #148416 is a reply to message #147312] |
Thu, 23 October 2003 09:47  |
Eclipse User |
|
|
|
Rich Kulp wrote:
> Use Variables instead. You would then customize the variable in each
> workspace for that particular platform.
Hi,
We definitely use variables, as it is the way to go.
This does not work very well when you have an entry in a classpath which
*only* exists on one platform and not on the others. If you specify this
as a variable, the platforms not using this variable have to point it to
some kind of dummy jar, which works, but its not really nice in my book :)
Anyway, that's the way we are solving it now.
It would be cool if Eclipse would support xml includes in it's
..classpath file though, so we can remove these dummy variables on
platforms that don't have a need for these vars (eg. swt-pi.jar is
defined in SWT_PI, but its not needed on windows machines), but that
would be just icing on the cake I guess :)
thanks for the reply,
Vincent
|
|
|
Powered by
FUDForum. Page generated in 0.03359 seconds