You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Bernd Waibel (JIRA)" <se...@james.apache.org> on 2016/07/19 09:00:28 UTC
[jira] [Created] (JAMES-1803) Classpath to long on windows running
james with run.bat
Bernd Waibel created JAMES-1803:
-----------------------------------
Summary: Classpath to long on windows running james with run.bat
Key: JAMES-1803
URL: https://issues.apache.org/jira/browse/JAMES-1803
Project: James Server
Issue Type: Bug
Components: Deployment Modules
Affects Versions: 3.0-beta4
Environment: Windows 10 Professional
Reporter: Bernd Waibel
Priority: Blocker
Fix For: 3.0.0-beta5
Running James3 with run.bat on windows will fail, cause the classpath may be to long.
The run.bat is created with a CLASSPATH=... which has more than 8192 characters (currently about 10.000 when beta5-SNAPSHOT is used). These are too much characters for Windows cmd.exe (currently running on windows 10), cause the limit is 8192 characters.
When running "run.bat" you will get a message "command line too long".
This may get better, as soon as the "SNAPSHOT" Tag is removed from the .jar files. But this will occur again, if there are more other libs and projects.
A solution would be:
Use the feature of java.exe, which is acception a "*" as classpath, since Java6.
So I would recommend to use:
set CLASSPATH="%BASEDIR%"\conf;"%REPO%"\*;
instead, and not to generate the CLASSPATH.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org