4 ms·

How did people use this before if it wasn't in the Maven Central Repo? I know it's possible to not use mvn, just wondering what people did in cases like this w

by maaaats 10y ago

How did people use this before if it wasn't in the Maven Central Repo? I know it's possible to not use mvn, just wondering what people did in cases like this where a possibly major component in the stack was unavailable. Most big stuff in Java can be found in mvn, and if not we often end up using an alternative. But that's not so easy for a driver.

jayd16 10y ago
Run a company maven repo. Make an internal maven plugin with what you need and add it to the company repo.
- eropple 10y ago
  Or just have a bash script that installs it to the local Maven repository first. Not recommended, but plenty of folks do it.
koolba 10y ago
Short of having a common / private repo (which is good advice for many other reasons), you can add it directly to the project so that it comes bundled with your source. This has the disadvantage of adding the JAR files to your source (which fattens things) but it has the advantage of working out of the box without any special config on a new developer's machine. Here's a nice article explaining how to do it: https://devcenter.heroku.com/articles/local-maven-dependencies https://devcenter.heroku.com/articles/local-maven-dependenci...
vbezhenar 10y ago
I have similar library and I use the following approach. I have "lib" directory in the project and I have those jar files there. Also there's simple install.sh script which calls "mvn install:install-file" for every jar-file. So developer has to run install.sh script once and he's done.
- emmelaich 10y ago
  Yep, same. For artifacts I've dealt with before it is semi-automated; it infers the groupid-artifactid-version from the name of the file downloaded from the vendor site.
Roboprog 10y ago
In my case, I'm only using Oracle from a (Java) web app, so I just put the driver directly into the JBoss (JEE server brand of the day) container setup, rather than something else in the Maven build. The driver is only needed at run time, not compile time, at least in this case.

by maaaats 10y ago

jayd16 10y ago

Run a company maven repo. Make an internal maven plugin with what you need and add it to the company repo.

eropple 10y ago
Or just have a bash script that installs it to the local Maven repository first. Not recommended, but plenty of folks do it.

koolba 10y ago

Short of having a common / private repo (which is good advice for many other reasons), you can add it directly to the project so that it comes bundled with your source. This has the disadvantage of adding the JAR files to your source (which fattens things) but it has the advantage of working out of the box without any special config on a new developer's machine. Here's a nice article explaining how to do it: https://devcenter.heroku.com/articles/local-maven-dependencies https://devcenter.heroku.com/articles/local-maven-dependenci...

vbezhenar 10y ago

I have similar library and I use the following approach. I have "lib" directory in the project and I have those jar files there. Also there's simple install.sh script which calls "mvn install:install-file" for every jar-file. So developer has to run install.sh script once and he's done.

emmelaich 10y ago
Yep, same. For artifacts I've dealt with before it is semi-automated; it infers the groupid-artifactid-version from the name of the file downloaded from the vendor site.

Roboprog 10y ago

In my case, I'm only using Oracle from a (Java) web app, so I just put the driver directly into the JBoss (JEE server brand of the day) container setup, rather than something else in the Maven build. The driver is only needed at run time, not compile time, at least in this case.