[KARAF-4599] KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.7, 3.0.8
• Fix Version/s: 4.1.0, 4.0.6, 3.0.8
• Assignee: Guillaume Nodet
• Reporter: Michael Vorburger
• Created: 29/Jun/16 18:50
• Updated: 29/Jul/16 08:10
• Resolved: 29/Jul/16 08:10

Description

KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but this introduced a new regression: Following that change, the ./karaf startup command now only works when invoked from current directoy, no longer via absolute path. For example:

git clone git://git.apache.org/karaf.git
cd karaf
git checkout karaf-3.0.x
cd tooling/karaf-maven-plugin
mvn clean install
cd ../..
mvn clean install -DskipTests
cd assemblies/apache-karaf/target/assembly/bin/
chmod +x karaf
./karaf
cd ../../../../..
./assemblies/apache-karaf/target/assembly/bin/karaf
Error: Could not find or load main class org.apache.karaf.main.Main

Of course we could further fiddle with the startup script to solve this somehow, but it occurred to me that perhaps somewhere on Apache there is a ready made script for this already? Like maybe looking at e.g. how the Maven / Ant & other such tools (Gradle?) would be valuable.

Perhaps some sort of non-regression integration test for both start-up scenarios, from current as well as via abs. path, would be of value?

Issue Links

• is related to: KARAF-4628 Can not start karaf on linux