[osmosis-dev] bin/osmosis and $CLASSPATH

[Jochen Topf]

Fine with me. But maybe OSMOSIS_CLASSPATH ? MYAPP sounds very generic.

Jochen

On Tue, Feb 03, 2009 at 11:10:28PM +1100, Brett Henderson wrote:
> 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
>>   

-- 
Jochen Topf  jochen at remote.org  http://www.remote.org/jochen/  +49-721-388298