You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "jamie campbell (JIRA)" <ji...@apache.org> on 2011/02/01 04:18:28 UTC
[jira] Created: (KARAF-430) don't force a karaf deploy to have a
lib directory
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
Priority: Minor
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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ 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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992360#comment-12992360 ]
Andreas Pieber commented on KARAF-430:
--------------------------------------
This was already fixed on trunk (before we've spitted off 2.2.x). I simply back-ported the solution from trunk to 2.1.x
> 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: Improvement
> 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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated KARAF-430:
----------------------------------
Issue Type: Improvement (was: Wish)
> 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: Improvement
> 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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber updated KARAF-430:
---------------------------------
Fix Version/s: 2.1.4
Assignee: Andreas Pieber
Already fixed for trunk; I'll fix it for 2.1.4
> 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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-430.
--------------------------------
> 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: Improvement
> Components: karaf-core
> 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 directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-430) don't force a karaf deploy to have a
lib directory
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992359#comment-12992359 ]
Guillaume Nodet commented on KARAF-430:
---------------------------------------
Has that been backported to trunk / 2.2.x branch ? I don't like the idea that things end up only in the maintenance branch ...
> 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 directory.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira