Re: [RAT] Jenkins still using SVN

On Sat, 1 Jun 2019 at 21:00, P. Ottlinger wrote: > > Hi Sebb, > > thanks for the hints > > Am 01.06.19 um 20:26 schrieb sebb: > > Possibly create > > https://svn.apache.org/repos/asf/creadur/rat/README.txt which points > > to the Git location. > > > I tried to modify the existing README.md

Re: [CallForVOTE] Upgrade to JDK1.7 language level - was: Re: [Discuss] RAT-244 - update to language level 1.7 due to CVE issues in RAT

+1 (binding) On Sat, 1 Jun 2019 at 21:28, Romain Manni-Bucau wrote: > > +1 (non binding) > > Le sam. 1 juin 2019 à 22:25, P. Ottlinger a écrit : > > > Am 01.06.19 um 22:25 schrieb P. Ottlinger: > > > +1 - I'm in favour of the vote. > > > > +1 from me. > > > > Phil > >

Build failed in Jenkins: Creadur-Whisker-Site-Latest-Jdk #26

See -- [...truncated 86.83 KB...] [INFO] preparing 'generate' report requires 'compile' forked phase execution [INFO] [INFO] >>> jdepend-maven-plugin:2.0:generate >

Build failed in Jenkins: Creadur-Rat #439

See -- Started by upstream project "Creadur-Rat-ParentPom" build number 227 originally caused by: Started by user pottlinger [EnvInject] - Loading node environment variables. Building

Build failed in Jenkins: Creadur-Whisker-Site-Latest-Jdk #25

See -- [...truncated 126.58 KB...] [INFO] Downloaded from central:

Re: [CallForVOTE] Upgrade to JDK1.7 language level - was: Re: [Discuss] RAT-244 - update to language level 1.7 due to CVE issues in RAT

+1 (non binding) Le sam. 1 juin 2019 à 22:25, P. Ottlinger a écrit : > Am 01.06.19 um 22:25 schrieb P. Ottlinger: > > +1 - I'm in favour of the vote. > > +1 from me. > > Phil >

Re: [CallForVOTE] Upgrade to JDK1.7 language level - was: Re: [Discuss] RAT-244 - update to language level 1.7 due to CVE issues in RAT

Am 01.06.19 um 22:25 schrieb P. Ottlinger: > +1 - I'm in favour of the vote. +1 from me. Phil

[CallForVOTE] Upgrade to JDK1.7 language level - was: Re: [Discuss] RAT-244 - update to language level 1.7 due to CVE issues in RAT

Hi, as there were no concerns mentioned yet I'd like to call for a vote to upgrade to Java7 as minimum for Creadur RAT. Vote is open until 2019-06-17 to give enough time for people currently on vacation: +1 - I'm in favour of the vote. -1 - I'm against upgrading because of . and have the

Re: [RAT] Jenkins still using SVN

Hi Sebb, thanks for the hints Am 01.06.19 um 20:26 schrieb sebb: > Possibly create > https://svn.apache.org/repos/asf/creadur/rat/README.txt which points > to the Git location. I tried to modify the existing README.md but the commit was rejected: $ svn commit Sende README.md

[jira] [Updated] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-254: -- Description: After moving to Gitbox/Github: * get rid of all references to SVN in RAT's pom *

[jira] [Updated] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-254: -- Description: After moving to Gitbox/Github: * get rid of all references to SVN in RAT's pom *

Re: Build failures - any ideas?

Hi, the Jenkins stuff is back in the green after moving to gitbox/git ;) thanks sebb! The Travis problem is still not clear to me I filed a new topic in their community https://travis-ci.community/t/chosen-jdk-for-build-is-not-honoured-as-javac-and-java-binaries-differ-in-versions/3591 as

Re: [creadur-rat] branch trunk updated: Snapshots must not be advertised on public download pages

On Sat, 1 Jun 2019 at 20:11, P. Ottlinger wrote: > > Hi, > > we want to link to SNAPSHOTs and releases in order to motivate testing - > why did you remove this passage without starting a discussion first? Because such links are not allowed on the public download pages:

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

See

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

See

[jira] [Updated] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-254: -- Description: After moving to Gitbox/Github: * get rid of all references to SVN in RAT's pom *

Re: [creadur-rat] branch trunk updated: Snapshots must not be advertised on public download pages

Hi, we want to link to SNAPSHOTs and releases in order to motivate testing - why did you remove this passage without starting a discussion first? Phil Am 01.06.19 um 20:32 schrieb s...@apache.org: > This is an automated email from the ASF dual-hosted git repository. > > sebb pushed a commit to

Re: [RAT] Jenkins still using SVN

Am 01.06.19 um 20:26 schrieb sebb: > It would certainly be sensible to update the RAT website so the Source > Repo links are accurate: > https://creadur.apache.org/rat/source-repository.html thanks - I already file RAT-254 to take care of that. Phil

Build failed in Jenkins: Creadur-Rat-Site #312

See -- [...truncated 38.32 KB...] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) @ apache-rat-api --- [INFO] [INFO] --- apache-rat-plugin:0.12:check (default)

Re: [RAT] Jenkins still using SVN

On Sat, 1 Jun 2019 at 19:11, P. Ottlinger wrote: > > Hi, > > thanks for the reminder - I'll file a RAT issue for that and after > changing all of RAT's jobs file an issue with infra to get rid of RAT's > SVN completely. I don't think it's a good idea to delete SVN. It may be needed for historic

[jira] [Updated] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-254: -- Fix Version/s: 0.14 > Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure >

[jira] [Updated] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger updated RAT-254: -- Description: After moving to Gitbox/Github: * get rid of all references to SVN in RAT's pom *

[jira] [Assigned] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

[ https://issues.apache.org/jira/browse/RAT-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Ottlinger reassigned RAT-254: - Assignee: Philipp Ottlinger > Finish move to Gitbox/Gitlab, adapt build jobs and ASF

[jira] [Created] (RAT-254) Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure

Philipp Ottlinger created RAT-254: - Summary: Finish move to Gitbox/Gitlab, adapt build jobs and ASF infrastructure Key: RAT-254 URL: https://issues.apache.org/jira/browse/RAT-254 Project: Apache Rat

Re: [RAT] Jenkins still using SVN

Hi, thanks for the reminder - I'll file a RAT issue for that and after changing all of RAT's jobs file an issue with infra to get rid of RAT's SVN completely. That won't solve the Travis issue, but hopefully fix ASF-Jenkins problems :-) Thanks again! Phil Am 01.06.19 um 14:20 schrieb sebb: >

Re: [RAT] Jenkins still using SVN

On Sat, 1 Jun 2019 at 12:17, sebb wrote: > > One of the Jenkins builds is still using SVN > > https://builds.apache.org/job/Creadur-Rat-Site-Latest-Jdk/ Actually it looks like the only build that is using Git is: Creadur-Rat > The builds should either be dropped, or modified to use the >

[RAT] Jenkins still using SVN

One of the Jenkins builds is still using SVN https://builds.apache.org/job/Creadur-Rat-Site-Latest-Jdk/ The builds should either be dropped, or modified to use the appropriate Git branch. Perhaps worth checking all the Creadur builds: https://builds.apache.org/view/A-D/view/Creadur/ S.

Build failed in Jenkins: Creadur-Rat-Site #311

See -- [...truncated 38.59 KB...] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) @ apache-rat-api --- [INFO] [INFO] --- apache-rat-plugin:0.12:check (default)

Build failed in Jenkins: Creadur-Rat-Site-Latest-Jdk #301

See -- [...truncated 34.11 KB...] [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ apache-rat-project --- [INFO] [INFO] --- maven-antrun-plugin:1.8:run

Build failed in Jenkins: Creadur-Rat-Site-Latest-Jdk #300

See -- [...truncated 31.61 KB...] A apache-rat-api/src/main/java/org/apache/rat A apache-rat-api/src/main/java/org/apache/rat/api A

Build failures - any ideas?

Hi guys, can anyone reproduce the build failures? I don't really get why it fails on ASF's Jenkins . as I can build it locally with a JDK8 (including the site build). Travis seems to have a different problem as it runs with different versions of java and javac Thanks for any

Build failed in Jenkins: Creadur-Rat-Site #310

See -- [...truncated 39.24 KB...] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) @ apache-rat-api --- [INFO] [INFO] --- apache-rat-plugin:0.12:check (default)

Build failed in Jenkins: Creadur-Rat-Site-Latest-Jdk #299

See -- [...truncated 48.99 KB...] [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/xmlrpc/xmlrpc-client/3.0/xmlrpc-client-3.0.jar [INFO] Downloaded:

Build failed in Jenkins: Creadur-Rat-Site #309

See -- [...truncated 37.97 KB...] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) @ apache-rat-api --- [INFO] [INFO] --- apache-rat-plugin:0.12:check (default)

Build failed in Jenkins: Creadur-Rat-Site #308

See -- [...truncated 37.85 KB...] [INFO] Exclude: **/iso-8859-1.html [INFO] 17 resources included (use -debug for more details) [INFO] Rat check: Summary over all files. Unapproved: 0,

Build failed in Jenkins: Creadur-Rat-Site #307

See -- [...truncated 31.49 KB...] AUapache-rat-tasks/src/site/site.xml A apache-rat-tasks/src/site/apt AUapache-rat-tasks/src/site/apt/types.apt AU