[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515512
]
Kan Ogawa commented on GERONIMODEVTOOLS-175:
--------------------------------------------
This cause is:
In Geronimo Eclpse plug-in's runtimeClasspathProvider, jar or zip files that
are placed in only location "repository/org/apache/geronimo/specs/" are by
default added to buildpath as its library entry.
For more detail, see source code of
org.apache.geronimo.st.core.RuntimeClasspathProviderDelegate class.
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/GeronimoServerRuntimeTargetHandler.java
Besides, jsf-api library (in Apache Myfaces) is similar, too.
I think that G-Repository directory structure for jee-spec-api library files
needs to be reconsidered including possibility of
RuntimeClasspathProviderDelegate class fix.
> 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
>
> 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.
