aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hughes (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-679) Some JDK5 compatibility sniff testing for projects that generate Java5 byte code
Date Wed, 26 Oct 2011 16:23:32 GMT

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

Jeremy Hughes updated ARIES-679:
--------------------------------

    Fix Version/s: blueprint.core-0.4
                   blueprint.cm-0.3.2
                   blueprint.annotation.impl-0.3.2
                   blueprint.annotation.api-0.3.2
                   blueprint uber bundle 0.4
                   proxy.impl-0.4
                   proxy.api-0.4
                   proxy uber bundle 0.4
                   quiesce.manager-0.3.1
    
> Some JDK5 compatibility sniff testing for projects that generate Java5 byte code
> --------------------------------------------------------------------------------
>
>                 Key: ARIES-679
>                 URL: https://issues.apache.org/jira/browse/ARIES-679
>             Project: Aries
>          Issue Type: Improvement
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>             Fix For: parent-0.5.0, testsupport.unit-0.4, util-0.4, quiesce.manager-0.3.1,
proxy uber bundle 0.4, proxy.api-0.4, proxy.impl-0.4, blueprint uber bundle 0.4, blueprint.annotation.api-0.3.2,
blueprint.annotation.impl-0.3.2, blueprint.cm-0.3.2, blueprint.core-0.4
>
>
> As previously mentioned on the mailing list, there is quite a few projects, which are
Java5 compatible and produce Java5 byte code. However, there is also a number of projects,
which look like they should be compatible in producing the right bytecode but use JDK6 APIs.

> A simple build check using the animal-sniffer plugin will check projects using java5-parent
0.4.1-SNAPSHOT and above for compatibility to the Java5 APIs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message