On 06-03-2009 11:26, feng.qian wrote:
> If you use External Tools launch configurations you don't even need a
> custom launch configuration type I would think.
> ...and if you used External Tools launch configurations for this
> users would be able to adjust this launch if really needed.
I am not familiar with external tools. I will take a look on it. But
if use it, when we call
wsprovider -c 'a.jar:b.jar:c.jar.............xxx.jar' -w -k
............. thejavaclass
where should I set the 'a.jar:b.jar:c.jar.............xxx.jar'? if
still in the command, I think it can't resolve my issue because I study
the launch configuration, at last, all of launches will call
DebugPlugin.exec(command), the command is still long.
You can launch External tools
or use a java launch - i'm pretty sure
java launch is not limited in the classpath length..i.e. TestNG
/junittests run with
the same project classpath as you would do.
/max