geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2917) All the spec jars should be in jee-spec config. Might not be ideal for the app client but simplifies build management
Date Thu, 05 Apr 2007 15:31:32 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-2917.
----------------------------------

    Resolution: Fixed

Haven't found any more specs in a while.... we can reopen if necessary.

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


Mime
View raw message