[jira] [Closed] (FELIX-3486) Allow for easy specification of class file compliance and Java API use

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler closed FELIX-3486.
-----------------------------------

> Allow for easy specification of class file compliance and Java API use
> ----------------------------------------------------------------------
>
>                 Key: FELIX-3486
>                 URL: https://issues.apache.org/jira/browse/FELIX-3486
>             Project: Felix
>          Issue Type: Improvement
>    Affects Versions: parent-2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: parent-3
>
>
> Currently the build target is hard coded with the compiler plugin. I propose to make this easily configurable using system or pom properties:
>    * felix.build.source -- Source compliance level; default to 1.3 as in Parent POM 2.1
>    * felix.build.target -- Target (class file) compliance level; default to 1.3 as in Parent POM 2.1
> In addition, it would make testing and compliance easier, if the bundles would be checked for compliance with offical Java API. To this avail the Codehaus Animal Sniffer plugin can be configured. Again to make overwriting simpler, the actual API signature used is defined by system or pom properties:
>    * felix.java.signature.groupId -- GroupId of the Java API signature; default: org.codehaus.mojo.signature
>    * felix.java.signature.artifactId -- ArtifactId of the Java API signature; default: java13-sun (java13 does not exist)
>    * felix.java.signature.version -- Version of the Java API signature; default: 1.0
> To use a different API signature projects generall just have to overwrite the felix.java.signature.artifactId property, e.g. to java14 for Java 1.4 or java15 for Java 5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)