Sometimes we need to use some commercial artifacts which are not available in the usual Maven repositories. These should of course be added to a repository hosted by your company or something like that, but sometimes it’s just simpler to stick those jars in the project directly and check them in with the rest of the code.
Found a nice way of doing that in the heroku devcenter documentation, so noting it down here for future reference.
We’ll start with deploying an artifact to a repo folder in our project by using the following command. I split it up so it’s easier to read, but it should of course all be a single command.
The group and artifact id you’d have to make up yourself of course. For example pull the artifact id from the library name and the group id from the main package used inside the library.
Remember to add this folder to your version control.
Add the following to your pom.xml to let Maven know about the project repository we just created.
And finally just define the dependency in your pom.xml like you’d usually do.
Clean and simple.