You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ji...@apache.org on 2004/04/17 16:51:30 UTC
[jira] Closed: (CACTUS-98) Why is there a requirement for ejb.manifest.classpath == true?
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-98
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-98
Summary: Why is there a requirement for ejb.manifest.classpath == true?
Type: Bug
Status: Closed
Priority: Blocker
Resolution: FIXED
Project: Cactus
Components:
Maven Integration
Fix Fors:
1.6
Assignee: Vincent Massol
Reporter: Archimedes Trajano
Created: Mon, 1 Mar 2004 11:14 PM
Updated: Sat, 17 Apr 2004 7:50 AM
Environment: Operating System: Other
Platform: Other
Description:
under <goal name="cactus:generate-ear-descriptor" prereqs="cactus:init">
there is a check for <j:if test="${dep.getProperty('ejb.manifest.classpath')
=='true'}"> this seems to be causing problems when testing EARs.
If I put in
<ejb.manifest.classpath>true</> in the project.xml file for the modules it
prevents deployment on jboss and if I remove it it does not add the module
into jboss.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org