[jira] [Resolved] (RAT-216) Update versions in pom after release of 0.12 and update dependencies

Affects Versions: 0.13 >Reporter: Philipp Ottlinger >Assignee: Philipp Ottlinger > Fix For: 0.13 > > > After 0.12 is finally out we need to update to 0.13-SNAPSHOT in all poms. > * (/) migrate all poms to 0.13-SNAPSHOT > * (/) update lastRATVersion to 0.

Jenkins build is back to normal : Creadur-Rat-Site #219

See

Jenkins build is back to normal : Creadur-Rat-Site-Latest-Jdk #217

See

[jira] [Updated] (RAT-216) Update versions in pom after release of 0.12 and update dependencies

. * (/) migrate all poms to 0.13-SNAPSHOT * (/) update lastRATVersion to 0.12 * (/) 20160825 UPDATE: update to latest ASF parent-pom 19 (from 17), needs update of maven-enforcer-rules to avoid NPE (1.0-beta-5 from 1.0-beta-2). (/) Apart from that the following dependencies can be updated according to the JDK

[jira] [Reopened] (RAT-216) Update versions in pom after release of 0.12 and update dependencies

[ https://issues.apache.org/jira/browse/RAT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reopened RAT-216: --- > Update versions in pom after release of 0.12 and update dependencies >

Re: Build failed in Jenkins: Creadur-Rat-Site #218

Hi, Am 25.08.2016 um 10:56 schrieb Jochen Wiedmann: > Can anyone explain to me, what's wrong here? I tried upgrading some stuff - since the enforcer-rules are still in beta upgrading to 1.0-beta-5 fixed the problem. Thanks for bringing up the issue; no need to upgrade our language level from

Re: Build failed in Jenkins: Creadur-Rat-Site #218

If you don't think it's a code change that broke it, can you check if this ran on a different executor or the executor built the project with a different version of java, maven, or maven enforcer plugin? I know they've been consolidating versions on the build servers recently. See builds@mailing

Re: Build failed in Jenkins: Creadur-Rat-Site #218

Can anyone explain to me, what's wrong here? Okay, I did some changes (like updating dependencies). But nothing, that remotely reminds me of a reason for that. Caused by: org.apache.maven.plugin.PluginExecutionException: Execution enforce-bytecode-version of goal