[forge-issues] [JBoss JIRA] (FORGE-417) forge does not start

forge does not start -------------------- Key: FORGE-417 URL: https://issues.jboss.org/browse/FORGE-417 Project: Forge Issue Type: Bug Environment: D:\Dev\forge>set ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\user1\AppData\Roaming CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=MPC ComSpec=C:\Windows\system32\cmd.exe ERROR_CODE=1 FORGE_HOME=D:\Dev\forge FP_NO_HOST_CHECK=NO gitdir=D:\Dev\git HOME=C:\Users\user1 HOMEDRIVE=C: HOMEPATH=\Users\user1 JAVA_HOME=d:\dev\jdk JBOSS_HOME=d:\dev\jboss6 JRE_HOME=d:\dev\jdk\jre LOCALAPPDATA=C:\Users\user1\AppData\Local LOGONSERVER=\\MPC M2=d:\dev\maven3\bin M2_HOME=d:\dev\maven3 MAVEN_OPTS=-Xms256m -Xmx512m NUMBER_OF_PROCESSORS=8 OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32 \WindowsPowerShell\v1.0\;D:\dev\SlikSvn\bin;d:\dev\jdk\bin;d:\dev\maven3\bin;D:\ Dev\forge\bin;D:\Dev\git\cmd;C:\Program Files\Intel\WirelessCommon\;C:\Program F iles\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\sys wow64; PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 30 Stepping 5, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=1e05 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\user1\AppData\Local\Temp TMP=C:\Users\user1\AppData\Local\Temp USERDOMAIN=mpc USERNAME=user1 USERPROFILE=C:\Users\user1 windir=C:\Windows D:\Dev\forge> Reporter: w m Priority: Blocker D:\Dev\forge>forge Fehler: Hauptklasse D:\Dev\forge\lib\aether-api.jar konnte nicht gefunden oder geladen werden D:\Dev\forge> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira