You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ted Kirby (JIRA)" <ji...@apache.org> on 2007/08/30 22:16:30 UTC

[jira] Commented: (GERONIMODEVTOOLS-175) javamail package is not included in server runtime

    [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523926 ] 

Ted Kirby commented on GERONIMODEVTOOLS-175:
--------------------------------------------

Thanks for the input Kan.  It seems easy to add a jar to the classpath, but for me that raises the questions: What should be in the classpath?  I don't think adding a few jars here and there that are someone's favorite at the time is what we ought to do.
It seems to me that all jars that are on the classpath by default when a module is deployed ought to be there.
If a user will have to add them to his classpath for them to work when deployed on the server, then having us add them here I do not think is proper, nor does it really help the user out.  I'd like further input on what the classpath should be.

> 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.