It's conceivable you don't have to mess with any sort of repackaging. The problem is that the MQ classes that your container loads have to be in a specific location, with a specific name. Simply deploy your unmodified application into a container with an altered classpath, where those "special" jars are in front of everything else on the classpath.
On Fri, Jul 25, 2014 at 9:07 AM, Steve Cohen <sco...@javactivity.org> wrote: > I have a client application that was developed with Websphere MQ. Our > company has a Maven nexus repository. In this repository, we have a place > to store third party jars. In here I stored the MQ jars. Since the > repository demanded a version number I provided one (7.0.1.8, 7.0.1.9, etc) > and in each case these version numbers were appended to the jar name. This > led to a clean build and deploy process and everyone was happy. > > Now we have need of turning on MQ traces. It turns out that IBM offers no > way of doing this unless the jar files are in a single directory named > exactly as IBM named them in their release. So we have to repackage the > application so as to accomplish this. > > Before I jump into hacking this mess into place, is there a recommended > way of handling this so that the maven repository, maven, and ibm are all > happy? > > Thanks, > Steve Cohen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
