You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/03/06 19:25:24 UTC
[jira] Created: (GERONIMO-2937) clean up geronimo-openejb
geronimo-dependency.xml
clean up geronimo-openejb geronimo-dependency.xml
-------------------------------------------------
Key: GERONIMO-2937
URL: https://issues.apache.org/jira/browse/GERONIMO-2937
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M3
Reporter: David Jencks
Fix For: 2.0-beta1
At least the geronimo-openejb geronimo-dependency.xml needs to be drastically cleaned up.
Guidelines for when to put a dependency in geronimo-dependency.xml rather than a config dependency:
- If the jar is something that will ONLY be used by the jar being built or things that MUST use the jar being built and there is NO CHANCE anyone else will want to use the jar put it in geronimo-dependency.xml. Typical examples of this are when you are integrating an external project such as jetty, tomcat, or openejb. Generally it is not appropriate to put a library in geronimo-dependency.xml since someone else might want to use it but not your jar.
- In all other cases but the dependency in a config. Put it in the config that you think everyone who wants to use the jar will depend on, not necessarily in the config that depends on the jar you are building.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2937) clean up geronimo-openejb
geronimo-dependency.xml
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-2937.
----------------------------------
Resolution: Fixed
Assignee: David Jencks
At some point I did clean up the geronimo-dependencies.xml, but these principles should really be in a more accessible place than this jira
> clean up geronimo-openejb geronimo-dependency.xml
> -------------------------------------------------
>
> Key: GERONIMO-2937
> URL: https://issues.apache.org/jira/browse/GERONIMO-2937
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M3
> Reporter: David Jencks
> Assigned To: David Jencks
> Fix For: 2.0-M4
>
>
> At least the geronimo-openejb geronimo-dependency.xml needs to be drastically cleaned up.
> Guidelines for when to put a dependency in geronimo-dependency.xml rather than a config dependency:
> - If the jar is something that will ONLY be used by the jar being built or things that MUST use the jar being built and there is NO CHANCE anyone else will want to use the jar put it in geronimo-dependency.xml. Typical examples of this are when you are integrating an external project such as jetty, tomcat, or openejb. Generally it is not appropriate to put a library in geronimo-dependency.xml since someone else might want to use it but not your jar.
> - In all other cases but the dependency in a config. Put it in the config that you think everyone who wants to use the jar will depend on, not necessarily in the config that depends on the jar you are building.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.