This bug will be evaluated for the next JDG release.
I'm increasing the severity on this BZ, because 6.2 made a much larger mess of this. We need to get this documented *now*. It can't wait until 6.3. In 6.1 there were 8 jars in the library distribution, so throwing them in a module was somewhat straightforward. In 6.2 there are now 68 jars in the library distribution. There is now a runtime-classpaths.txt included, which lists dependencies. But: - several of the jars listed as dependencies are not even included - quite a few of the jars are most likely optional, but there's no indication of that in runtime-classpaths.xml - there's a lot of recursive dependencies -- infinispan-core depends on infinispan-commons, which depends on a bunch of other jars, etc. making it a bit of a pain. We need straight-forward documentation on exactly what/how to package JDG. This is the very first thing any JDG customer runs into.
Starting a thread in relevant lists to discuss how we can test and document this, perhaps in a maintenance release and copying in dereed.
runtime-classpaths.txt is not recursive: for each jar the transitives are completely specified.
*** Bug 1067736 has been marked as a duplicate of this bug. ***
This bug is now available as part of the JDG 6.3 Beta documentation: https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Grid/
(In reply to Misha H. Ali from comment #15) > This bug is now available as part of the JDG 6.3 Beta documentation: > > https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Grid/ Misha, you should add a note that the modules are not provided with the EAP distribution. You need to download the EAP modules from CSP and unzip it to EAP directory