[jbosstools-issues] [JBoss JIRA] (JBIDE-12378) Use of Java 6 API where Java 5 is declared as the execution environment

Denis Golovin (JIRA) jira-events at lists.jboss.org
Mon Aug 13 19:35:44 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Golovin updated JBIDE-12378:
----------------------------------

        Fix Version/s: 3.4.0.M1
    Affects Version/s: 3.3.0.Final

    
> Use of Java 6 API where Java 5 is declared as the execution environment
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-12378
>                 URL: https://issues.jboss.org/browse/JBIDE-12378
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS/Servers, maven
>    Affects Versions: 3.3.0.Final
>            Reporter: Peter Palaga
>            Assignee: Rob Stryker
>            Priority: Trivial
>             Fix For: 3.4.0.M1
>
>         Attachments: JBIDE-12378-patch.txt
>
>
> (1) The project org.jboss.tools.maven.ui uses java.lang.String.isEmpty() which is available since Java 6 but the project's MANIFEST.MF states 
>    Bundle-RequiredExecutionEnvironment: J2SE-1.5
> (2) There is a similar problem in org.jboss.ide.eclipse.as.ui where in its MANIFEST.MF the execution environment is declared properly as JavaSE-1.6 but the .classpath file contains something else, namely J2SE-1.5.
> I will provide a patch for both (1) and (2).
> A similar issue has recently been fixed in org.jboss.tools.seam.ui by changing the declared execution environment in MANIFEST.MF to JavaSE-1.6.

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

        


More information about the jbosstools-issues mailing list