karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (KARAF-430) don't force a karaf deploy to have a lib directory
Date Tue, 01 Feb 2011 11:20:29 GMT

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

Andreas Pieber resolved KARAF-430.

    Resolution: Fixed

resolved on karaf-2.1.x

Committing to https://svn.apache.org/repos/asf/karaf/branches/karaf-2.1.x ...
        M       main/src/main/java/org/apache/karaf/main/Main.java
Committed r1065998

> don't force a karaf deploy to have a lib directory
> --------------------------------------------------
>                 Key: KARAF-430
>                 URL: https://issues.apache.org/jira/browse/KARAF-430
>             Project: Karaf
>          Issue Type: Wish
>          Components: runtime
>    Affects Versions: 2.1.3
>         Environment: ubuntu 10.04
>            Reporter: jamie campbell
>            Assignee: Andreas Pieber
>            Priority: Minor
>             Fix For: 2.1.4
> I've done a maven-based approach to creation of a karaf environment using the same dependencies
as the downloadable karaf does.  In mine, the jaas.boot and karaf main jars are in the system/
hierarchy, not in lib.  However, I have to have my deploy create an empty lib directory because
karaf crashes with null pointer exception otherwise.  This is because it does a for loop based
on listfiles() for this directory, which crashes if it doesn't exist.
> My wish is for this code (src/main/src/main/java/org/apache/karaf/main/Main.java , line
950) to first check existence of lib directory, and skip the for loop if there is no such

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message