-
1. anybody encounter this which drive me crazy?
mwtemple Apr 3, 2011 5:14 PM (in response to chaiyilin)The command line launch has exceeded 32k...
I know it sounds amazing but, there are over 400+ jars in JBoss (not sure about Tomcat).
Depending on where you installed it, it makes a HUGE difference.
Are you on windows?
Mark
-
2. Re: anybody encounter this which drive me crazy?
chaiyilin Apr 3, 2011 6:33 PM (in response to mwtemple)yes, i am on windows.
but how to solve this problem? i have changed the maven repo folder to D:\.m2\r, the error still remain same!
i believe this situation is pretty common
-
3. Re: anybody encounter this which drive me crazy?
chaiyilin Apr 3, 2011 6:55 PM (in response to chaiyilin)thanks god and Mark. solved!
1. short repo folder to D:\.m2\r
2. do the trick mention above:http://community.jboss.org/thread/162340
-
4. Re: anybody encounter this which drive me crazy?
mwtemple Apr 3, 2011 7:03 PM (in response to chaiyilin)Definitely the classpath is too long.
You did a good move with shortening the path to the repository..
It's probably the path to Jboss or Tomcat...
You can see what is really being executed (and how long the classpath really is) by doing the following:
After the run fails, go to the debug perspective and right-click on the terminated run:
View the properties and see how long the command was:
Now, I select the entire command line output and copy it into Notepad++ and replace ";" with ";/n" to get a better idea of what is going on:
Mark
-
5. anybody encounter this which drive me crazy?
chaiyilin Apr 4, 2011 8:22 AM (in response to mwtemple)thanks again. Mark
-
6. anybody encounter this which drive me crazy?
mwtemple Apr 4, 2011 10:00 AM (in response to chaiyilin)Glad I could help!