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/01 23:38:50 UTC
[jira] Commented: (GERONIMO-2917) All the spec jars should be in
jee-spec config. Might not be ideal for the app client but simplifies
build management
[ https://issues.apache.org/jira/browse/GERONIMO-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477110 ]
David Jencks commented on GERONIMO-2917:
----------------------------------------
these changes made in rev 513538. Talking with rick geronimo-javamail_1.4_mail is the correct jar for mail, need to change that back.
> All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2917
> URL: https://issues.apache.org/jira/browse/GERONIMO-2917
> 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-beta2
>
>
> some spec jars aren't in the jee-spec config. It might be better to have 2 modules, one shared between client and server and the other for the server-only specs, but lets have just one until we get certified.
> missing specs I have found so far:
> geronimo-interceptor_3.0_spec
> geronimo-javamail_1.4_spec vs geronimo-javamail_1.4_mail
> geronimo-jpa_3.0_spec
> myfaces-api
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.