"kukeltje" wrote : You may file a jira issue for this usecase. I'd appreciate
that.
Thank you Ronald, here it is:
https://jira.jboss.org/jira/browse/JBPM-1908
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195824#4195824
Reply to the post :
http://www.jboss
You may file a jira issue for this usecase. I'd appreciate that.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195756#4195756
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195756
__
The installer needs improving, that is known and that is why there was a
release to get some feedback on the usage. A separate zip with just the jars
will not be needed if the installer improves.
Anyway, thanks for the feedback
View the original post :
http://www.jboss.com/index.html?module=bb
Ok, thank you Ronald for your kind reply.
Anyway, I would suggest jBPM developers to release two packets (a plain ZIP and
an installer) or to let the user uncheck the server/DB deployment phase of the
installation process, because the current behaviour is misleading (by the way,
I find it a bit
The usecase for the installer is different than the one for the zip
If you want the separate jars, use the maven repo.
The .jar file is an installer that you can install with the command I mentioned
in one (or two) posts below this one, the one about documentation and
installing jBPM 3.3 (sear
