Looking at my last post when I last did this, it’s been a year since I last deployed something to OpenShift with my own custom dependent jars 🙂 And looks like some of the paths might have changed since last time, but the approach is still the same.
What worked for me this time:
mvn install:install-file -DgeneratePom=true -Dfile=../../jar-file-name-inc-version-number.jar -DgroupId=your-group-id -DartifactId=artifact-name -Dversion=0.0.1-SNAPSHOT -Dpackaging=jar
Looks like the relative path to where the jar gets copied to in your remote account changed slightly since last time.
The odd thing is I still ran into issues with my prebuild script file losing it’s executable flag, and it never seems to run as part of my build, but I can run it manually my ssh’ing into my account and just running it by hand.