[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-390) Build option for building without Java 5

[Michal Matloka (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKWRAP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766259#comment-12766259 ] 

Michal Matloka commented on SHRINKWRAP-390:
-------------------------------------------

I vote for Aslak proposition - source and target 1.5 + animal sniffer (which does both signature check and check of usage of only jdk5 classes). Currently IDE detects shrinkwrap as java 7. Allows to use Java 7 features and classes. Invalid features are detected during mvn build by <compilerArguments> (now I think it is deprecated, and because of that IDE allows java 7), and invalid classes are detected during tests run by jdk5 usage.

Now:
{noformat}
<plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <inherited>true</inherited>
        <configuration>
          <source>1.7</source>
          <target>1.7</target>
          <showDeprecation>false</showDeprecation>
          <showWarnings>true</showWarnings>
          <optimize>true</optimize>
          <compilerVersion>1.7</compilerVersion>
          <fork>true</fork>
          <compilerArguments>
            <source>1.5</source>
            <target>1.5</target>
          </compilerArguments>
        </configuration>
      </plugin>
{noformat}
                
> Build option for building without Java 5
> ----------------------------------------
>
>                 Key: SHRINKWRAP-390
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-390
>             Project: ShrinkWrap
>          Issue Type: Task
>          Components: build
>         Environment: Fedora 17
>            Reporter: Carlo de Wolf
>            Assignee: Michal Matloka
>
> Fedora 17 does not have a Java 5 JDK, so it is impossible to get through the enforcer check.
> "JAVA5_HOME needs to be set to run some tests in the JRE5 runtime"

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