[osmosis-dev] bin/osmosis and $CLASSPATH

[Brett Henderson]

 From what I can tell most java apps don't use a system CLASSPATH so it 
might be wise to avoid it if possible.

Would it be cleaner to create a new variable (eg. 
MYAPP_CLASSPATH_EXTERNAL) or something (I'm not fussed what it's called) 
that can be set externally (such as in your .osmosis file) and then 
appended to the MYAPP_CLASSPATH if it exists?  That would allow you to 
register your own jars on the classpath if you want to, but would keep 
osmosis independent of the system classpath which might be cluttered 
with all sorts of junk.

Jochen Topf wrote:
> bin/osmosis calls "java -cp ...". Java then ignores whats in $CLASSPATH.
> Anybody against adding $CLASSPATH to the paths osmosis comes up with?
>
> So in bin/osmosis change
> MYAPP_CLASSPATH=$MYAPP_CLASSPATH:$MYAPP_HOME/lib/default/$FILE
> to
> MYAPP_CLASSPATH=$MYAPP_CLASSPATH:$MYAPP_HOME/lib/default/$FILE:$CLASSPATH
>
> Jochen
>