[osmosis-dev] use classworlds-Loader fort start script?
brett at bretth.com
Thu Dec 3 22:15:05 GMT 2009
If it isn't too invasive it should be fine. I guess the best way is to try
it out and see if any problems crop up.
Um, I don't tend to use the options file myself because I don't need it ...
It's typically used to adjust default VM memory size or register a plugin
class, neither of which I need.
Does anybody else have an options file handy? I guess we'll need one for
Windows and Linux.
We don't *have* to maintain compatibility with the existing option files
although it would be preferable. The main thing is to make sure they're
still easy to use.
On Fri, Dec 4, 2009 at 8:54 AM, Hakan Tandogan <hakan at gurkensalat.com>wrote:
> Brett Henderson wrote:
>> Sounds awesome. I assume no code changes are required? One thing to
>> check is whether it will still allow osmosis options to be loaded from
>> the existing config files.
> You basically have a wrapper (org.classworlds.something) that reads the
> name of your class with the main() method from a config file and calls that.
> If you want, you can always create your classpath manually (as it is now)
> and call the main method yourself.
> Good point with the osmosis options file though, I'll have to test that. Do
> you have an options file somewhere so I can create an unit test for correct
> parsing of parameters?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osmosis-dev