Document URL: JDG Developer's Guide and/or Getting Started Guide Section Number and Name: N/A Describe the issue: The documentation does not include details on packaging the jars for JDG library mode or the client side of client/server. The quickstarts use maven to do it behind the user's back, which does not necesssarily work in an environment with more complicated classloading such as in JBoss EAP. Suggestions for improvement: The documentation should include explicit information on packaging JDG library mode or the client side of client/server: what jars must be packaged, details on using isolated classloading, etc. Specific examples for popular containers such as JBoss EAP 6 would be useful. Additional information:
For the following point: * A list of dependencies we need to package. - If someone can point me to such a list, I can include it as a table with a quick blurb about what feature it offers. We have a txt file in the library distro that lists all the modules and their dependencies. the dependency jars will likely change beta -> GA and further for each subsequent release so it seems sensible to point users to this list in the distro rather than to document the list in the docs (in an appendix).
I've emailed Divya about this, so he can reopen this bug if he has objections. Dereed, I'm tracking the EAP packaging in another bug for a future release (you are CC'd in that bug IIRC). Closing this as NOTABUG for 6.2