Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Mon, 27 May 2013 12:35:26 +0000 (UTC)
From: "Forrest Xia (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <JIRA.12536478.1325055385537.26079.1369658126186@arcas>
In-Reply-To: <JIRA.12536478.1325055385537@arcas>
References: <JIRA.12536478.1325055385537@arcas>
Subject: [jira] [Updated] (GERONIMO-6246) remove package versions from most
 spec jars until there's an osgi recommendation on what they should be.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Forrest Xia updated GERONIMO-6246:
----------------------------------

    Fix Version/s:     (was: 3.0.1)
                   3.0.2
    
> remove package versions from most spec jars until there's an osgi recommendation on what they should be.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6246
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6246
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: specs
>    Affects Versions: 3.0.0
>            Reporter: David Jencks
>             Fix For: 3.0.2
>
>
> except maybe for servlet, there aren't any osgi recommendations for package versions of spec api packages.  We will just cause incompatibility and confusion if we decide on our own what the versions should be.  This has already happened with our use of 3.0 for the servlet 3.0 package versions, whereas everyone seems to agree it should be 2.6 (and this should be checked.... maybe some packages haven't changed from 2.5).
> This will require recompiling all bundles that have been compiled against our specs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira