[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524742
]
Rick McGuire commented on GERONIMODEVTOOLS-175:
-----------------------------------------------
The javamail jar is a merged jar file that includes the javamail spec apis
inside of this. This was done to get around the configuration problems anybody
who chose to use the SMTP provider kept running into. Because the jars were
split originally, the javamail apis were in the default classpath, but the
provider classes were not, resulting in NoProviderFound exceptions. In 2.0,
the merged uber jar replaced the split setup, so the javamail jar file is the
api replacement for the old javamail spec jar.
In any event, this should be part of the server classpath, as this is a
required component of the javaee5 specification.
> 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.
