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

Oliver B. Fischer updated TAMAYA-55:
------------------------------------
    Description: 
After introducing a separation of "java7" vs. "java8" for many components, the 
Parent POM in the top level of the repository should no longer make assumptions 
like
{code}
<jdkVersion>1.8</jdkVersion>
<maven.compile.targetLevel>${jdkVersion}</maven.compile.targetLevel>
<maven.compile.sourceLevel>${jdkVersion}</maven.compile.sourceLevel>
{code}
There's at least one more place in the configuration of maven-enforcer-plugin 
also assuming
{code}
 <requireJavaVersion>
          <version>1.8.0</version>
 </requireJavaVersion>
{code}

This should for those and other possible cases be pushed down into OS-related 
POMs.

  was:
After introducing a separation of "java7" vs. "java8" for many components, the 
Parent POM in the top level of the repository should no longer make assumptions 
like
{code}
    <jdkVersion>1.8</jdkVersion>
        <maven.compile.targetLevel>${jdkVersion}</maven.compile.targetLevel>
        <maven.compile.sourceLevel>${jdkVersion}</maven.compile.sourceLevel>
{code}
There's at least one more place in the configuration of maven-enforcer-plugin 
also assuming
{code}
 <requireJavaVersion>
          <version>1.8.0</version>
 </requireJavaVersion>
{code}

This should for those and other possible cases be pushed down into OS-related 
POMs.


> Parent POM should not assume Java 8
> -----------------------------------
>
>                 Key: TAMAYA-55
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-55
>             Project: Tamaya
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 0.1-incubating
>            Reporter: Werner Keil
>            Assignee: Oliver B. Fischer
>              Labels: Java, Maven
>             Fix For: 0.1-incubating
>
>
> After introducing a separation of "java7" vs. "java8" for many components, 
> the Parent POM in the top level of the repository should no longer make 
> assumptions like
> {code}
> <jdkVersion>1.8</jdkVersion>
> <maven.compile.targetLevel>${jdkVersion}</maven.compile.targetLevel>
> <maven.compile.sourceLevel>${jdkVersion}</maven.compile.sourceLevel>
> {code}
> There's at least one more place in the configuration of maven-enforcer-plugin 
> also assuming
> {code}
>  <requireJavaVersion>
>           <version>1.8.0</version>
>  </requireJavaVersion>
> {code}
> This should for those and other possible cases be pushed down into OS-related 
> POMs.



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

Reply via email to