You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2006/05/01 05:28:49 UTC
[jira] Updated: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=all ]
Alex Karasulu updated DIRSERVER-331:
------------------------------------
Fix Version: 1.0-RC3
(was: 1.0-RC2)
> JAR File Contents Cause JBoss Deployer To Fail
> ----------------------------------------------
>
> Key: DIRSERVER-331
> URL: http://issues.apache.org/jira/browse/DIRSERVER-331
> Project: Directory ApacheDS
> Type: Bug
> Components: sar
> Versions: 1.0-RC1
> Environment: JDK 1.4.2, JBoss 3.2
> Reporter: Simon Temple
> Assignee: Alex Karasulu
> Fix For: 1.0-RC3
>
> The presence of the META-INF/maven folders and/or their content causes the JBoss deployer to skip JAR files.
> Then we experience an avalanche of java.lang.NoClassDefFoundError exceptions!
> It could be argued that this is a problem with the JBoss deployer (perhaps seraching for .xml files in META-INF folders), however, we're not in a position to modify the JBoss deployer at this time.
> Can the maven folders be removed from the JARs or perhaps a build switch introduced to produce JBoss compatible JARs?
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira