[
https://issues.apache.org/jira/browse/TAMAYA-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272053#comment-14272053
]
Mark Struberg commented on TAMAYA-55:
-------------------------------------
Oh now I understand. You switched the whole system to java7 and only made a few
java8 modules on top of it. Does that mean that you also like to move our
current core to java7 and re-use most parts of it by simply extending them in
the java8 core module?
> 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)
