[ 
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392304#comment-15392304
 ] 

Stephen Kitt commented on KARAF-4599:
-------------------------------------

In OpenDaylight, this was fixed by checking the exit status from the realname 
call; see 
https://git.opendaylight.org/gerrit/#/c/39982/12/karaf/opendaylight-karaf-resources/src/main/resources/bin/karaf
 (technically the ODL patch is EPL-licensed, so avoid that if you don't want to 
be "contaminated" — although I doubt the copyright holder on this would mind 
licensing it as ASL2 as well, if copyright even applies to such a small code 
change).

> 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.7, 3.0.8
>            Reporter: Michael Vorburger
>            Assignee: Jean-Baptiste Onofré
>            Priority: Critical
>             Fix For: 4.1.0, 4.0.6, 3.0.8
>
>
> 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)

Reply via email to