As I have continued to work on developing java code for PEX, using the workflow as described in the InterSystems book that can be found here,  I think it would add a lot of value for you to store the jars in a public maven repository such as Maven Central .  The reason is that we develop the java classes outside of InterSystems first, again per the workflow recommended by InterSystems.   Without them being in a repo for maven to download, we have a couple options to work around this, which are all ugly:

• Add the jars locally as with a system scope.
  • Causes maven warnings and this is a deprecated maven functionality.
• Create a local repository which requires a lot of configuration and means that if someone downloads my project from git, will be missing all the jar files.
• Create an internal company maven repository which requires a lot of work across multiple teams.

The first option is the best as anyone can then download my project from version control (git, svn, etc...) and have all the needed files. With the system scope set in the pom for these jars, the jars will not be included in the built jar.  This, unfortunately, is a deprecated maven function.   As more InterSystems customers start using PEX, I think having them in a public repository will add a lot of business value for InterSystems.

That means the jar files will be available to the java code during runtime, which works.  During development of the java code, I just added the jar files in maven with a scope of system, which should solve my problem.  

Thank you for the quick response!