[Swift-devel] CLASSPATH construction order
Ben Clifford
benc at hawaga.org.uk
Sun Apr 20 12:05:45 CDT 2008
The bin/swift wrapper currently constructs a classpath for swift
automatically, as whatever is already on the classpath in the current
environment followed by all of the swift classes.
This order seems to cause more problems than it solves - specifically,
when there are overlapping classes specified in the environment (which I
have seen with falkon and pegasus users, and potentially is also a problem
for people with the Globus Toolkit installed).
I think it would be better to construct the classpath the other way round.
This would remove the ability for people to override internal Swift
classes by presetting classpath, which, in the above cases, happens
accidentally and produces obscure errors.
If there is a desire to still be able to override swift classes from the
environment, which I think there is not, then another Swift specific
environment variable should be used for the prefix.
--
More information about the Swift-devel
mailing list