Hide Forgot
Description of problem: Thanks for Prakash 's concerns on this for user better understanding on the structure of standalone package. In the meanwhile, we would move drools client jars to jboss-as/client/drools as well. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I would advice against this, as this would: - make it more difficult for users to find the runtime libraries they need - a split up of jars (into jbpm and drools) would make it difficult to add these jars as a jBPM runtime in Eclipse - it gives the impression jBPM requires an application server to run I believe a separate jbpm runtime folder at the root level is useful (although a rename might be appropriate).
This user case is similar to drools which is stored in jboss-as/client. This is also considering for a better organization of the folder stucture. PM have made decision to have: jboss-as/client/ drools/ jbpm/ Note that jbpm/lib folder was removed, all jbpm jars are put into one folder. This should be more convinent for JBDS user. Plus, BRMS document would have description on how to add the runtime libraries. Code changed in productise level, assign to Lee to update documentations.
Thanks Ryan, I've updated the BRMS Getting Started Guide [1] the changes should be live on the internal docstage with the next hour. Users are now instructed to use the directories: jboss-as/client/ drools/ jbpm/ Thanks Lee [1]http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html-single/BRMS_Getting_Started_Guide/index.html#runtimes
Update status to ON_QA. Please verify them against ER6.
Libraries have been moved there. VERIFIED.
Closing as status already set to verified.