[ 
https://issues.apache.org/jira/browse/KARAF-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet moved FELIX-2373 to KARAF-84:
---------------------------------------------

              Project: Karaf  (was: Felix)
                  Key: KARAF-84  (was: FELIX-2373)
    Affects Version/s:     (was: karaf 1.6.0)
          Component/s:     (was: Karaf)
        Fix Version/s: 1.6.2
                           (was: karaf-1.6.2)

> Wrapper service is not configured properly in Karaf 1.6.0
> ---------------------------------------------------------
>
>                 Key: KARAF-84
>                 URL: https://issues.apache.org/jira/browse/KARAF-84
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: Bengt Rodehav
>            Assignee: Guillaume Nodet
>             Fix For: 1.6.2
>
>
> Changes related to Karaf startup has been done in Karaf 1.6.0 but those 
> changes have not been reflected in the configuration of the Wrapper service. 
> I had to do the following changes in "karaf-wrapper.conf" to get Karaf 1.6.0 
> to work with the Wrapper service:
> a) Change the main class:
>   wrapper.app.parameter.1=org.apache.felix.karaf.main.Main
> b) Add the following line to the classpath:
>   
> wrapper.java.classpath.4=%KARAF_HOME%/system/org/apache/felix/org.apache.felix.framework/2.0.5/org.apache.felix.framework-2.0.5.jar
> c)  Add the following JVM parameters:
>   
> wrapper.java.additional.6=-Djava.endorsed.dirs="%JAVA_HOME%/lib/endorsed;%KARAF_HOME%/lib/endorsed"
>   
> wrapper.java.additional.7=-Djava.ext.dirs="%JAVA_HOME%/lib/ext;%KARAF_HOME%/lib/ext"
>  
>  
> Actually "c)" wasn't really necessary to get Karaf started but it seemed to 
> have been omitted in comparison to "karaf.bat". Overall I think someone 
> should compare the settings in "karaf.bat" with the ones in 
> "karaf-wrapper.conf" to make sure they are the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to