karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Vorburger (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
Date Wed, 29 Jun 2016 18:51:05 GMT
Michael Vorburger created KARAF-4599:
----------------------------------------

             Summary: KARAF-4564 impact: karaf startup command now only works when invoked
from current directoy, no longer via absolute path
                 Key: KARAF-4599
                 URL: https://issues.apache.org/jira/browse/KARAF-4599
             Project: Karaf
          Issue Type: Bug
    Affects Versions: 3.0.8
            Reporter: Michael Vorburger
            Priority: Critical


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:

{noformat}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
{noformat}

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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message