You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Simon Temple (JIRA)" <di...@incubator.apache.org> on 2006/01/31 14:12:33 UTC
[jira] Created: (DIREVE-332) JAR File Contents Cause JBoss Deployer
To Fail
JAR File Contents Cause JBoss Deployer To Fail
----------------------------------------------
Key: DIREVE-332
URL: http://issues.apache.org/jira/browse/DIREVE-332
Project: Directory Server
Type: Bug
Versions: 0.9.4
Environment: JDK 1.4.2, JBoss 3.2
Reporter: Simon Temple
Assigned to: Alex Karasulu
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
[jira] Commented: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=comments#action_12428903 ]
Alex Karasulu commented on DIRSERVER-331:
-----------------------------------------
I applied your patch. See if you can get the sar to work now.
> JAR File Contents Cause JBoss Deployer To Fail
> ----------------------------------------------
>
> Key: DIRSERVER-331
> URL: http://issues.apache.org/jira/browse/DIRSERVER-331
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: sar
> Affects Versions: 1.0-RC1
> Environment: JDK 1.4.2, JBoss 3.2
> Reporter: Simon Temple
> Assigned To: Alex Karasulu
> Fix For: 1.0-RC4
>
>
> 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
[jira] Commented: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=comments#action_12428648 ]
Jörg Henne commented on DIRSERVER-331:
--------------------------------------
The problem ist caused by the jboss-sar-maven-plugin. Although I reported the problem and supplied a patch, nobody bothered to apply it.
See http://jira.codehaus.org/browse/MOJO-377
> JAR File Contents Cause JBoss Deployer To Fail
> ----------------------------------------------
>
> Key: DIRSERVER-331
> URL: http://issues.apache.org/jira/browse/DIRSERVER-331
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: sar
> Affects Versions: 1.0-RC1
> Environment: JDK 1.4.2, JBoss 3.2
> Reporter: Simon Temple
> Assigned To: Alex Karasulu
> Fix For: 1.0-RC4
>
>
> 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
[jira] Updated: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=all ]
Alex Karasulu updated DIRSERVER-331:
------------------------------------
Component: sar
Fix Version: 1.0-RC2
Version: 1.0-RC1
> 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-RC2
>
> 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
[jira] Commented: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=comments#action_12365838 ]
Alex Karasulu commented on DIRSERVER-331:
-----------------------------------------
I have no idea if this is even possible regarding the maven folders. I'd have to check with the maven peeps. Now with regard to the exception are you certain that the maven folders are causing this? Did you try unjaring, removing them, jaring and redeploygin?
> 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
> Environment: JDK 1.4.2, JBoss 3.2
> Reporter: Simon Temple
> Assignee: Alex Karasulu
>
> 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
[jira] Commented: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Simon Temple (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=comments#action_12367350 ]
Simon Temple commented on DIRSERVER-331:
----------------------------------------
Yes I removed the maven XML files and the problem goes away.
Any XML file in a META-INF folder is regarded as instruction to a deployer... I checked to the JBoss code... they search for all files with the .xml extension beneath META-INF.
> 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-RC2
>
> 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
[jira] Closed: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=all ]
Alex Karasulu closed DIRSERVER-331.
-----------------------------------
Fix Version/s: 1.1.0
Resolution: Fixed
fix for 1.0 on 437399 here:
http://svn.apache.org/viewvc?view=rev&revision=437399
and for 1.1 here:
http://svn.apache.org/viewvc?view=rev&revision=437401
> JAR File Contents Cause JBoss Deployer To Fail
> ----------------------------------------------
>
> Key: DIRSERVER-331
> URL: http://issues.apache.org/jira/browse/DIRSERVER-331
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: sar
> Affects Versions: 1.0-RC1
> Environment: JDK 1.4.2, JBoss 3.2
> Reporter: Simon Temple
> Assigned To: Alex Karasulu
> Fix For: 1.1.0, 1.0-RC4
>
>
> 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
[jira] Updated: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DIRSERVER-331) JAR File Contents Cause JBoss
Deployer To Fail
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-331?page=all ]
Alex Karasulu updated DIRSERVER-331:
------------------------------------
Fix Version: 1.0-RC4
(was: 1.0-RC3)
> 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-RC4
>
> 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