无法构建kie-wb-webapp 6.1.x(JBPM)

时间:2015-06-29 22:18:39

标签: gwt maven-3 guava jbpm kie-workbench

我需要修改KIE Workbench源码,我有两个问题阻止我使用Maven 3.2.5构建,一个在Windows上,一个在Linux上。

在Windows 7上,我收到错误消息

[deletia...]SNAPSHOT\uberfire-backend-api-0.4.0-SNAPSHOT-sources.jar,
com.google.gwt.dev.Compiler,-logLevel, INFO, -style, OBF, -war, 
c:\kie-wb-webapp\target\kie-wb-webapp-6.1.1-SNAPSHOT, -localWorkers, 1,
-strict, -XfragmentCount, -1, -deploy, c:\kie-wb-webapp\target\gwt-symbols-deploy, -gen, 
c:\kie-wb-webapp\target\.generated, org.kie.workbench.FastCompiledKIEWebapp]: 
Error while executing process. Cannot run program "c:\development\software\jdk\jdk1.7.0_71\jre\bin\java": 
CreateProcess error=206, The filename or extension is too long.  

所以我查了一下,显然,这是众所周知的限制,因为gwt-maven-plugin会创建一个超过8191个字符的命令行,这是禁止的。所以我试了一下Ubuntu。

在Ubuntu上,

我得到了:

[INFO] --- gwt-maven-plugin:2.5.1:compile (gwt-compile) @ kie-wb-webapp     [ERROR] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option     MaxPermSize=256m; support was removed in 8.0
 [ERROR] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
[INFO] Compiling module org.kie.workbench.FastCompiledKIEWebapp
[INFO]    Validating units:
[INFO]       [ERROR] Errors in 'jar:file:/home/rich/.m2/repository/com/google/guava/guava-gwt/14.0.1/guava-gwt-14.0.1.jar!/com/google/common/primitives/Booleans.java'
[INFO]          [ERROR] Line 29: The import java.util.BitSet cannot be resolved
[INFO]    [ERROR] Aborting compile due to errors in some input files
[INFO]     ------------------------------------------------------------------------
[INFO] BUILD FAILURE*

我找到一个或两个问题的解决办法非常重要(我的猜测是,如果我在Windows上清除命令行问题,我将再次遇到番石榴问题)。此外,除非绝对必要,否则我无法升级到6.2.x,因为这会为我的项目带来很多工作。

有没有人碰到这个?

1 个答案:

答案 0 :(得分:0)

If you don't need Java 8 support, you may be able to solve the problem by using an earlier version of the JDK. I believe that you do this by setting JAVA_HOME for your Maven run. You can download a JDK 7 here.

You could also build Guava yourself from HEAD, as the problem has been fixed there but not included in a release. Or you could wait for a 19.0-rc1, which we hope to have out soon.