What is the recommended way of handling jars not available in mvn central, such as javax.jms

[LilianaZ]

I have a project which depends on camel-jms, which in turn depends on javax.jms.jms 1.1 jar. This jar is not available in maven central (AFAIU due to licensing on this jar) so the build fails. The build works locally for me as I manually installed it into the local maven cache, but what is the recommended way of dealing with jars like this in Bitbucket Pipelines environment?

[ojongerius · Accepted solution]

You can pull this particular dependency in by adding the JBoss Maven repository to your POM file:

<repositories>
      <repository>
        <id>repository.jboss.org-public</id>
        <name>JBoss.org Maven repository</name>
        <url>https://repository.jboss.org/nexus/content/groups/public</url>
      </repository>
  </repositories>

[LilianaZ]

Thanks, it seems that corporate culture of blocking everything (like adding own repos in poms) has brainswashed me into missing the most obvious, simple solution