[
https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655008#comment-13655008
]
Dan Tran edited comment on KARAF-1545 at 5/10/13 11:25 PM:
-----------------------------------------------------------
this enhancement will create surprise to existing user base.
Also, lib is universal 'lib' directory used by lots of appl and genenated
script ( ie produce by appassembler-maven-plugin), each script can place jar
file under lib and hand pick the exacts jars to be loaded into the script's
main class ( same for karaf ). This is a good contract which to be broken when
next release of karaf that has this enhancement
was (Author: danttran):
this ehancement will create surprise to existing user base
> Jar files in lib directory require "karaf-" prefix in order to be loaded
> ------------------------------------------------------------------------
>
> Key: KARAF-1545
> URL: https://issues.apache.org/jira/browse/KARAF-1545
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 2.2.2
> Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc.
> Java home: /home/jcarman/Programs/jdk1.6.0_32/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix"
> Reporter: James Carman
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.12, 2.3.2, 2.4.0, 3.0.0
>
> Attachments: karaf-3.0_1545.diff
>
>
> I was trying to configure JDBC fail-over, so I put my mysql driver jar in the
> KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the
> advice of someone on IRC, I changed the name to
> "karaf-mysql-connector-java.jar" and it started working. Why the karaf-
> prefix requirement? If that's the intended behavior, then please update the
> README file in the lib directory. It says:
> "Any jar in this folder will be part of the main classloader used to load
> Karaf."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
