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

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?

1 answer

1 accepted

0 votes
Accepted answer

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>

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 smile

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

211 views 3 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you