CODEWITHSUNDEEP
javamavenwebsphere
J Fabian Meier
J Fabian Meier

Reputation: 35901

POM files for Websphere specific jars

Websphere offers a set of provided jars, including com.ibm.ws.ejb.thinclient_8.5.0.jar, com.ibm.ws.batch.runtime.jar, com.ibm.ws.orb_8.5.0.jar, etc.

In the ANT build process, some people had these files on the classpath. Now we are moving to Maven, and I am not sure what I should do with these files:

Upvotes: 0

Views: 4770

Answers (2)

Scott Kurz
Scott Kurz

Reputation: 5330

Try the "was_public" JAR and POM shipped along with WebSphere Application Server traditional, starting with Version 8.

See here.

Upvotes: 1

hotzst
hotzst

Reputation: 7526

If you are using a company maven repository as a proxy to maven central, the best thing to do is to make these jar files available there:

mvn install:install-file -Dfile=<path to the jarfile> -DgeneratePom=true -Dpackaging=jar -Dversion=<version> -DgroupId=<groupId> -DartifactId=<artifactId>

In such a case the groupId is usualy composed by your company prefix and then the base package of the artifact. The artefactId would be the last part without the version. For example for com.ibm.ws.ejb.thinclient_8.5.0.jar, the version is 8.5.0, the artifactId thinclient and the groupId something like com.example.thirdparty.com.ibm.ws.ejb. The same approach works as well if you are the sole developer and install these artifacts in your local repository.

See also the official documentation

Another approach would be to have these files as part of the project and reference them through a local path and install it from there either using the maven-install-plugin or by issuing the steps from the first approach as part of the build process. See Maven and adding JARs to system scope and Maven: add a dependency to a jar by relative path.

Disclaimer: I always used the first option, as this seems to be the proper way.

Upvotes: 3

Related Questions