Avoid error when running java tests which generate super long command lines?

Question

I get a:

Exception occurred executing command line.
CreateProcess

Cause by a too long commandline (too many libraries, too long path to the jars) when running from eclipse. The only solution for me is to go to run as configuration... then create a configuration, remove all default dependencies and manually add only the things which are required, so the commandline does not get cut off.

I normally do this for jUnit tests.

This is a waste of time, is there a different solution?

thanks

score 4 · Accepted Answer · edited May 23 '17 at 11:56

4

If you're on java >= 6 you can use classpath wildcards.

That should be enough unless you have your jars scattered around the filesystem, which would call for some cleanup.

edit

If you're simply running junit tests with run as junit test in eclipse then you can define 'user library' and add that to the classpath. Haven't tested it though, and it might suffer from some limits on environmental variable length in windows, but i think that's the safest bet.

edit2

You can try this plugin mentioned in this answer. It worked on indigo, so i guess it will work on helios.

edited May 23 '17 at 11:56

Community

1
1

answered Feb 08 '12 at 14:57

soulcheck

36,297
6
91
90

Well I can use them, but is eclipse is capable of doing so? I use 3.6.2 helios – Toskan Feb 08 '12 at 16:29
@Toskan how exactly are you running the tests? – soulcheck Feb 08 '12 at 16:53
i'll test it soon to see how it goes, for now, i'll accept your answer – Toskan Feb 09 '12 at 13:03

score 0 · Answer 2 · answered Feb 08 '12 at 16:01

You can play around with forking settings - if you do not fork junit execution, you should be fine. However, classpath management in eclipse is a big mess - it does not separate production and test scopes.

Real alternative would be working maven build, which you should have, as eclipse is not a proper building tool - surefire plugin provides anough alternatives to overcome classpath environmen shortage.

Avoid error when running java tests which generate super long command lines?

2 Answers2

Related