[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524982
]
Kan Ogawa commented on GERONIMODEVTOOLS-175:
--------------------------------------------
Thanks, committers.
I firstly commented that a few jars are added to ClasspathProvider class, but I
thought that this is very deep problem at the same time.
Because, application developer can freely configure any optional module as the
dependency element to Geronimo deployment plan.
Optional jars related to specified dependencies need to be dynamically added
into classpath, too.
( This is very similar to the dependencies configuration to eclipse plug-in
manifest in eclipse PDE. )
Summary - JARs in classpath
1. Required JARs
- Java EE 5 spec APIs.
2. Optional JARs
- Module APIs ( deployed in Geronimo server repository ) added as dependency
to Geronimo deployment plan.
If insufficient, please input to above summary.
Well, I think that this GERONIMODEVTOOLS-175 issue should resolve the "Required
JARs" task only.
About the "Optional JARs" task, we should re-discuss how to design and
implement it under new issue that will be reported as new feature task to JIRA.
> javamail package is not included in server runtime
> --------------------------------------------------
>
> Key: GERONIMODEVTOOLS-175
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-175
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.0
> Reporter: Song
> Assignee: Tim McConnell
> Fix For: 2.0
>
>
> If an application uses javamail, user have to manually add geronimo's
> javamail jar into build path.
> Why javamail jar is not included in server runtime by default?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
