You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/08/03 13:38:19 UTC
[jira] Created: (GERONIMO-281) Optional packages support
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-281
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-281
Summary: Optional packages support
Type: New Feature
Status: Unassigned
Priority: Major
Project: Apache Geronimo
Components:
deployment
OpenEJB
Assignee:
Reporter: Jacek Laskowski
Created: Tue, 3 Aug 2004 4:37 AM
Updated: Tue, 3 Aug 2004 4:37 AM
Description:
Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
[...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
---------------------------------------------------------------------
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
[jira] Assigned: (GERONIMO-281) Optional packages support
Posted by de...@geronimo.apache.org.
Message:
The following issue has been re-assigned.
Assignee: Jacek Laskowski (mailto:jlaskowski@apache.org)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-281
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-281
Summary: Optional packages support
Type: New Feature
Status: Open
Priority: Major
Project: Apache Geronimo
Components:
deployment
OpenEJB
Assignee: Jacek Laskowski
Reporter: Jacek Laskowski
Created: Tue, 3 Aug 2004 4:37 AM
Updated: Tue, 3 Aug 2004 4:37 AM
Description:
Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
[...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
---------------------------------------------------------------------
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
[jira] Updated: (GERONIMO-281) Optional packages support
Posted by de...@geronimo.apache.org.
The following issue has been updated:
Updater: Dain Sundstrom (mailto:dain@coredevelopers.net)
Date: Wed, 8 Sep 2004 8:47 PM
Changes:
description changed from
Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
[...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...] to Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
[...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
Version changed to 1.0-M1
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/GERONIMO-281?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-281
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-281
Summary: Optional packages support
Type: New Feature
Status: In Progress
Priority: Major
Project: Apache Geronimo
Components:
deployment
OpenEJB
Versions:
1.0-M1
Assignee: Jacek Laskowski
Reporter: Jacek Laskowski
Created: Tue, 3 Aug 2004 4:37 AM
Updated: Wed, 8 Sep 2004 8:47 PM
Description:
Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
[...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
---------------------------------------------------------------------
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
[jira] Closed: (GERONIMO-281) Optional packages support
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-281?page=history ]
Gianny DAMOUR closed GERONIMO-281:
----------------------------------
Resolution: Fixed
Fix Version: 1.0-M3
This has been fixed by Dain when he has rewritten the deployment code.
> Optional packages support
> -------------------------
>
> Key: GERONIMO-281
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-281
> Project: Apache Geronimo
> Type: New Feature
> Components: deployment, OpenEJB
> Versions: 1.0-M1, 1.0-M2
> Reporter: Jacek Laskowski
> Assignee: Jacek Laskowski
> Fix For: 1.0-M3
>
> Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
> As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
> The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
> [...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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
[jira] Updated: (GERONIMO-281) Optional packages support
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://nagoya.apache.org/jira/browse/GERONIMO-281?page=history ]
Gianny DAMOUR updated GERONIMO-281:
-----------------------------------
Version: 1.0-M2
Add 1.0-M2 to the list of affected versions.
> Optional packages support
> -------------------------
>
> Key: GERONIMO-281
> URL: http://nagoya.apache.org/jira/browse/GERONIMO-281
> Project: Apache Geronimo
> Type: New Feature
> Components: deployment, OpenEJB
> Versions: 1.0-M1, 1.0-M2
> Reporter: Jacek Laskowski
> Assignee: Jacek Laskowski
>
> Add optional packages support. Optional packages are resources listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.
> As a workaround it's possible to copy the resources to repository directory and specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.
> The suggested approach to handle it is (Dain's email to OpenEJB dev mailing list):
> [...]Instead I would create a lib directory in the config-store directory for the module (i.e., a config-store/${number}/lib directory). Then, just read in the manifest class path entries for the ejb jar, copy them into the lib dir and add them to the configuration class-path. One trick is you must repeat this for each jar copied into the lib as each of these can have manifest class path entries. Also watch out for circular dependencies in the manifest class path entries.[...]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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