-
1. Re: nightmare on building JBPM6 source code
salaboy21 May 4, 2014 8:20 AM (in response to big_chen)Hi Charles,
Building all the projects takes too long, that's why we have dedicated machines to build them all. My question to you, is why do you need to build all the projects? We usually just build the one that we are interested in changing, and all the others are downloaded from maven.
You can try also running without the tests, and try to avoid building the projects called *-webapp which are the ones that compiles the gwt permutations and those takes some time and a lot of CPU. If you still want to compile the -webapp distributions, you can take a look at the GWT maven plugin for tweaking the GWT maven compilation parameters such as memory, threads etc.
HTH
-
2. Re: nightmare on building JBPM6 source code
big_chen May 4, 2014 9:01 AM (in response to salaboy21)Dear Mauricio Salatino,
Many thanks to your earnest reply.
I've evaluate the jbpm-console module and found it is suit for me, but I want to learn how to work out it from relevant github source code.
Firstly, I build jbpm-console-ng.war from one sub-directory of droolsjbpm project, but I found that it cannot let me to evaluate the jbpm like jbpm-console.war because I cannot login it successfully. I guess maybe the jbpm-console-ng module is not the all part of jbpm-console-ng.
I've just want to know how to build a jbpm-console.war, and falled into the source code building, and expect it can work out the war file.
Can you give me the right way to work out the jbpm-console.war?
Thanks in advance!
Sincerely yours,
Charles
-
3. Re: nightmare on building JBPM6 source code
greenday_ra May 7, 2014 1:30 AM (in response to big_chen)Hi Charles
Try to compile jbpm-console-ng/jbpm-console-ng-showcase sub project, i think it's all you need.
if you found memory problem in compile time replace <extraJvmArgs> tag in your jbpm-console-ng-showcase/pom.xml with this one
<extraJvmArgs>-Xmx2048m -XX:MaxPermSize=512m -Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory -Djetty.custom.sys.classes=bitronix;javax.transaction -Dorg.kie.demo=true -Dorg.kie.clean.onstartup=true</extraJvmArgs>
this parameter prevent concurrent gwt permutations compile, and keeps ram free, but then you need more time to compile.
"-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory"
-
4. Re: nightmare on building JBPM6 source code
big_chen May 13, 2014 3:02 AM (in response to greenday_ra)Dear Reza Azizi,
Many thanks to your earnest reply.
I've built the jbpm-console-ng sub-project, and got the war package, but cannot find the way to login (not the same username/password pair as jbpm-console). and have to think other strategies.
Could any maven know how to evaluate thoroughly with jbpm-console-ng with sucessfully login into it?
Thanks in advance!
Yours sincerely,
Charles
-
5. Re: nightmare on building JBPM6 source code
salaboy21 May 13, 2014 4:25 AM (in response to big_chen)Hi there,
you need to build the -distribution-wars projects inside the jbpm console ng in order to deploy the application to the supported containers. And then configure the users and roles for those containers. If you want, you can start the application in developer mode, which can be triggered from the jbpm-console-ng-showcase/ directory using the
mvn gwt:run command. For hosted mode, there are some files inside the application which actually contains the users, roles and passwords. If you are planning to deploy on jboss you must use the distribution wars (the one tagged with jboss-as7 or something like that), and the configure the users as stated in the jbpm documentation.
Regards
-
6. Re: nightmare on building JBPM6 source code
greenday_ra May 14, 2014 3:14 AM (in response to big_chen)Hi Chen
About, deployment you must consider 2 configuration file.
../jbpm-console-ng/jbpm-console-ng-showcase/src/main/webapp/WEB-INF/web.xml
../jbpm-console/jbpm-console-ng/jbpm-console-ng-showcase/src/main/resources/META-INF/persistence.xml
you can check the jbpm-console-ng-distribution-wars folder and you will see that these configuration file are different from the original one in showcase project.
when you finished the compile process of showcase subproject then go to distribution-wars subproject and run mvn clean install again.
this process, extract the original showcase war file, make changes to those configuration, remove some extra files and make another war file in ../jbpm-console-ng-distribution-wars/target folder.
this war file can be deployed, but you need a well configured jboss AS as well.
the jbpm-6.0.x.Final-installer-full.zip package have an ant script (build.xml) that show everything you need to configure JBoss for JBPM deployment.
Regards