Re: Problem running Apache Gump [vmgump]

This is my fault. I (still) haven't added the Derby JARs correctly. I'm working on this now. Mark On 23/05/2024 03:14, g...@gump-vm2.apache.org wrote: There is a problem with run 'vmgump' (23052024_01), location : http://gump-vm2.apache.org/

Re: Cron cd /srv/gump/public/gump/cron; /bin/bash gump.sh all

Nothing to worry about. I started the run early so this is just the cron job complaining about the job I started. Mark On 21/05/2024 19:00, Cron Daemon wrote: The lock file [/srv/gump/public/gump/gump.lock] exists, and is locked.. Either Gump is still running, or it terminated very

Re: FYI - Gump will be moving to Java 22 EA shortly

Hi all, It took a little longer than I expected to do this. I've just switched vmgump to Java 22. The first run should start in ~4.5 hours. Mark On 24/10/2023 12:32, Mark Thomas wrote: Hi all, Tomcat now needs Java 22 to build the development branch so I'll be moving Gump to use Java 22

FYI - Gump will be moving to Java 22 EA shortly

Hi all, Tomcat now needs Java 22 to build the development branch so I'll be moving Gump to use Java 22 once it is available in the ASF package repository. I anticipate this move happening in the next week or so. Mark - To

Re: Cron cd /srv/gump/public/gump/cron; /bin/bash gump.sh all

On 19/05/2023 13:00, Cron Daemon wrote: The lock file [/srv/gump/public/gump/gump.lock] exists, and is locked.. Either Gump is still running, or it terminated very abnormally. Please resolve this (waiting or removing the lock file) before retrying. Looks like Tomcat test failures causing a

Re: Gump build switched to Java 21

On 11/05/2023 16:57, Stefan Bodewig wrote: On 2023-05-10, Mark Thomas wrote: Tomcat 11 is about to move to requiring Java 21 so I have just switched Gump to building with the latest Java 21 EA. I am expecting things to break and for it to take a couple of days for me to get everything fixed

Gump build switched to Java 21

Hi all, Tomcat 11 is about to move to requiring Java 21 so I have just switched Gump to building with the latest Java 21 EA. I am expecting things to break and for it to take a couple of days for me to get everything fixed. Fingers crossed... Mark

Maven bumped from 3.6.2 to 3.6.3

Hi all, A number (all?) of Commons projects now require Maven 3.6.3 as a minimum so I bumped the Maven version to 3.6.3. I thought about taking it to the latest 3.x release but opted for the minimal change at this point. If this goes well, I may move Gump to Maven 3.9.1 next week. Mark

Re: Direction of Gump

On 19/02/2023 11:56, Stefan Bodewig wrote: Hi all after Gump's last board report one of the members asked whether we aren't disturbed by not adding any new committers for many years now (actually I don't believe anybody who is a not a PMC member already has posted anything to ths list for

Re: Moving to Java 17

Looks to be back to where we were before the Java 17 update. Mark On 19/01/2023 09:38, Mark Thomas wrote: Quick update, I just switched Gump over. Should start to see the impact with the 12.00 UTC run in ~2.5 hours time. Mark On 12/01/2023 07:27, Stefan Bodewig wrote: On 2023-01-11, Mark

Re: Moving to Java 17

Quick update, I just switched Gump over. Should start to see the impact with the 12.00 UTC run in ~2.5 hours time. Mark On 12/01/2023 07:27, Stefan Bodewig wrote: On 2023-01-11, Mark Thomas wrote: Once I have confirmed Java 17 has been installed, I'll switch Gump over to Java 17 and wait

Moving to Java 17

Hi all, Tomcat is about to move the main development branch to Java 17. So Gump can continue to build Tomcat, I intend to move Gump to Java 17. I have added Java 17 to the packages installed by Puppet (and removed Java 8 since we have been using Java 11 for a while now). Once I have

Re: Problem running Apache Gump [vmgump]

On 11/11/2021 08:16, Mark Thomas wrote: This will be the changes I made yesterday to add JaCoCo which it looks like I messed up. I'll take a look now. Should be fixed now. Running an official run as the one at midnight failed. Mark On 11/11/2021 02:36, g...@gump-vm2.apache.org wrote

Re: Problem running Apache Gump [vmgump]

This will be the changes I made yesterday to add JaCoCo which it looks like I meessed up. I'll take a look now. Mark On 11/11/2021 02:36, g...@gump-vm2.apache.org wrote: There is a problem with run 'vmgump' (2021_01), location : http://gump-vm2.apache.org/

Re: Starting to move Gump to using Java 11

On 20/08/2021 17:53, Mark Thomas wrote: On 20/08/2021 09:06, Stefan Bodewig wrote: I've already added the jar and changed the descriptors. Unfortunately I did so before realizing that my ssh key is unknown to the current vmgump and so I've not been able to update the working copy

Re: Starting to move Gump to using Java 11

On 20/08/2021 09:06, Stefan Bodewig wrote: On 2021-08-19, Mark Thomas wrote: On 19/08/2021 17:53, Stefan Bodewig wrote: Tomcat transitvely inherits antlr4*.jar but this jar doesn't seem to contain the "runtime" package. I believe you also want https://mvnrepository.com/artifact

Re: Starting to move Gump to using Java 11

On 19/08/2021 17:53, Stefan Bodewig wrote: On 2021-08-19, Mark Thomas wrote: Many thanks for cleaning up the mess I created. You didn't create a mess here, you just uncovered an undetected bug. The -bootclasspath/p problems of xml-apis and xml-resolver are probably not really fixable. We

Re: Starting to move Gump to using Java 11

On 19/08/2021 13:39, Stefan Bodewig wrote: On 2021-08-19, Stefan Bodewig wrote: It looks as if you may have uncovered a bug in Ant's build, no, the Gump descriptor has been broken before. While compiling the tests Ant didn't see the main classes it had just compiled. It could only see those

Re: Starting to move Gump to using Java 11

It looks like I have broken the Ant build somehow. I can't see what I have done wrong. No rush, but some help on this from someone more familiar with the Ant build than I would be helpful. Mark On 12/08/2021 10:57, Mark Thomas wrote: On 12/08/2021 10:46, Stefan Bodewig wrote: Many thank

Re: Starting to move Gump to using Java 11

On 12/08/2021 10:46, Stefan Bodewig wrote: Many thank for doing this, Mark On 2021-08-10, Mark Thomas wrote: Is there a way in Gump to get just some projects to build with a different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11 is the minimum requirement. We can then take

Re: Starting to move Gump to using Java 11

On 11/08/2021 10:46, Mark Thomas wrote: On 11/08/2021 09:06, Adam Jack wrote: I am traveling home from abroad right now but I can look into things when I get settled back. That said, I am sure others are far less rusty than me on this. That said, from my rusty/simplistic perspective: Would

Re: Starting to move Gump to using Java 11

out to be a lot simpler than it appears, once the dependencies are tidied up. Mark Regards, Adam On Tue, Aug 10, 2021 at 11:15 PM Mark Thomas wrote: On 10/08/2021 21:38, Mark Thomas wrote: On 10/08/2021 21:17, Adam Jack wrote: Thanks for the update. Good luck. Thanks. I think I am going to n

Re: Starting to move Gump to using Java 11

On 10/08/2021 21:38, Mark Thomas wrote: On 10/08/2021 21:17, Adam Jack wrote: Thanks for the update. Good luck. Thanks. I think I am going to need it. This is going to be *far* from simple. There is lots of code currently being built by Gump that needs changes to build with Java 9+. You

Starting to move Gump to using Java 11

All, Since Tomcat's main development branch now requires Java 11, I have started the process of moving Gump over to Java 11. So far, I have added Java 11 to the packages installed by Puppet. I want to confirm that Java 11 has been installed, then I'll switch JAVA_HOME to point to Java 11

Re: Problem running Apache Gump [vmgump]

On 26/04/2021 18:10, g...@gump-vm2.apache.org wrote: There is a problem with run 'vmgump' (26042021_180001), location : http://gump-vm2.apache.org/ Looks like a temporary problem with network access. Subsequent runs look to be OK. Mark

Re: Cron cd /srv/gump/public/gump/cron; /bin/bash gump.sh all --official

On 02/12/2020 00:00, Cron Daemon wrote: > The lock file [/srv/gump/public/gump/gump.lock] exists, and is locked.. > Either Gump is still running, or it terminated very abnormally. > Please resolve this (waiting or removing the lock file) before retrying. This is expected. I started a manual run

Re: Gump, Ubuntu 20.04 and python

.S. I also managed to SSH into gump-vm2. Glad that worked. Once you set-up OPIE you should be able to use sudo: https://cwiki.apache.org/confluence/display/INFRA/OPIE Kind regards, Mark > > regards, > > Adam > > On Mon, Nov 30, 2020 at 8:01 AM Mark Thomas wrote: > >

Re: Gump, Ubuntu 20.04 and python

the cron jobs. Almost there... Mark On 30/11/2020 08:41, Mark Thomas wrote: > On 29/11/2020 22:04, Adam Jack wrote: >> Hey Mark >> >> It transpires that there was an "isinstance(self.value, NoneType)" that got >> converted to an "self.value is *not* None&

Re: Gump, Ubuntu 20.04 and python

s continuing with the branch? Mark > > regards > > Adam > > On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas wrote: > >> Hi Adam, >> >> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at: >> http://gump-vm2.apache.org/buildLog.

Re: Gump, Ubuntu 20.04 and python

Correct. home.a.o only allows sftp. I'll need to add you to gump-vm2.a.o - I'll do that shortly. Mark > > regards, > > Adam > > On Sun, Nov 29, 2020 at 1:06 PM Mark Thomas wrote: > >> On 29/11/2020 18:50, Adam Jack wrote: >>> Thanks Mark, >>> >

Re: Gump, Ubuntu 20.04 and python

npkiIpNKuFDRr7YfH0RyBRYTE494wd55V8+3BDqfWbrCZXtbLJ+4PWm/9ECYuwEVe9UXRceNaq0kOKK7ZGXUoHK+3Xl7OJZ/M0w3Y7p5RqJvb Mark Thomas 20170112 Cheers, Mark > > regards, > > Adam > > On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas wrote: > >> Hi Adam, >> >> The current r

Re: Gump, Ubuntu 20.04 and python

/2020 18:03, Mark Thomas wrote: > On 29/11/2020 15:18, Adam Jack wrote: >> Thanks for testing it out Mark. >> >> If you need help taking it from here, let me know, and if I can gain access >> to the VM I'll help out. >> >> [ I am away (social distancing at a

Re: Gump, Ubuntu 20.04 and python

udo. I'm just fixing the errors I can see in preparation for the next run. Thanks, Mark > > regards, > > Adam > > On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas wrote: > >> On 29/11/2020 01:18, Adam Jack wrote: >>> Hey Mark, >>> >>> I'

Re: Gump, Ubuntu 20.04 and python

. Mark > > regards, > > Adam > > On Fri, Nov 27, 2020 at 12:29 PM Mark Thomas wrote: > >> Hi, >> >> Ubuntu 20.04 comes with python3. You can make python2 work but it >> involves jumping through some hoops. >> >> Gump doesn't work with p

Gump, Ubuntu 20.04 and python

Hi, Ubuntu 20.04 comes with python3. You can make python2 work but it involves jumping through some hoops. Gump doesn't work with python 3. I've spent a couple of hours trying to fix this (patch on gump-vm2 in /home/markt) and I have reached the end of my (very) limited python skills. So, we

Re: Board Report

On 09/06/2020 11:07, Stefan Bodewig wrote: > Hi all > > the board report is due tomorrow. From my POV Mark has been fixing > things and nothing really changed. Gump works and the Tomcat community - > i.e. Mark - makes sure it remains useful for them. +1. Gump continues to provide value to the

Re: svn commit: r1878298 - /gump/metadata/project/jsch.xml

On 30/05/2020 00:34, ma...@apache.org wrote: > Author: markt > Date: Fri May 29 23:34:14 2020 > New Revision: 1878298 > > URL: http://svn.apache.org/viewvc?rev=1878298=rev > Log: > Update jsch to 0.1.55 This might just fix the failing ant-dist build... ...assuming I haven't forgotten a version

Re: Problem running Apache Gump [vmgump]

On 06/05/2020 09:48, g...@gump-vm.apache.org wrote: > There is a problem with run 'vmgump' (06052020_01), location : > http://gump-vm.apache.org/ > > The log ought be at: >http://gump-vm.apache.org/gump_log.txt >

Re: Where are we going?

On 07/03/2020 15:35, Stefan Bodewig wrote: > Hi all > > nowadays Gump has become a tool that really only gets used by Tomcat. As > long as it is useful for Tomcat this is probably fine. But is this the > future of this project? Honestly, I haven't got any other vision to > share. It is

Gump runs taking ~9 hours

With the creation of an additional Tomcat branch and another set of 3 unit tests, the Gump runs are now taking ~9 hours. I have reduced the daily runs to 2: midnight (the main run) and noon UTC. Mark - To unsubscribe, e-mail:

Re: BATCH: All dressed up, with nowhere to go...

On 05/02/2020 09:52, Mark Thomas wrote: > The root cause of these errors is this: > https://support.sonatype.com/hc/en-us/articles/360041287334-Central-501-HTTPS-Required > > Maven central now requires https. > > I'm not sure how easy a fix this is going to be. Should be fi

Re: BATCH: All dressed up, with nowhere to go...

The root cause of these errors is this: https://support.sonatype.com/hc/en-us/articles/360041287334-Central-501-HTTPS-Required Maven central now requires https. I'm not sure how easy a fix this is going to be. Mark On 19/01/2020 01:21, g...@gump-vm.apache.org wrote: > Dear Gumpmeisters, >

Re: Gump CI build failing for Apache Forrest for more than 1 year

Hi, I am going to assume that Forrest no longer requires the services of Apache Gump and go ahead with the clean-up. Mark On 2019/06/17 12:07:56, Mark Thomas wrote: > On 17/06/2019 12:46, Tim Williams wrote: > > Hey Mark, > > I suspect not... instead, we should have th

Re: Maven updated on vmgump

On 20/11/2019 16:50, Mark Thomas wrote: > Hi, > > I saw the Easymock build has been failing for a while as it requires > Maven 3.5.0 or later. > > I've updated the /opt/maven3 symlink to point to the latest Maven 3.x > (3.6.2). > > I'll keep an eye on the next fe

Maven updated on vmgump

Hi, I saw the Easymock build has been failing for a while as it requires Maven 3.5.0 or later. I've updated the /opt/maven3 symlink to point to the latest Maven 3.x (3.6.2). I'll keep an eye on the next few builds to see what breaks. Mark

Re: Problem running Apache Gump [vmgump]

Known config issue. I think I have fixed it. Need to chat with Infra to figure out how to make the config change persist. Mark On 27/07/2019 00:00, g...@gump-vm.apache.org wrote: > There is a problem with run 'vmgump' (27072019_02), location : > http://gump-vm.apache.org/ >

Re: Gump CI build failing for Apache Forrest for more than 1 year

t decides to got to the attic or not, is make the following offer: If Forrest no longer needs the services of Apache Gump let me (via general@gump.apache.org) know and I'll take care of cleaning all that up for you. Mark > > Thanks, > --tim > > On Mon, Jun 17, 2019 at 6:55 AM Mark

Gump CI build failing for Apache Forrest for more than 1 year

All, The last successful Apache Forrest build on Gump was over 12 months ago. Looking back ~6 months I don't see any indications of the Apache Forrest community working on the build failures. Granted the issues are mostly in dependencies but that shouldn't prevent the Forrest community

Re: BATCH: All dressed up, with nowhere to go...

FYI: The gump-vm instance (the new one) is taking a little over 6 hours for a complete run. I am currently starting some of the runs manually to try and get three runs a day rather than two. I will also take a look at the machine specs and the configuration of the long running Tomcat tests to see

Re: Cron /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm > /dev/null 2>&1

On 31/05/2019 14:36, Stefan Bodewig wrote: > On 2019-05-31, Mark Thomas wrote: > >> On 31/05/2019 13:22, Stefan Bodewig wrote: >>> On 2019-05-31, sebb wrote: > >>>> The command: > >>>> /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /

Re: Cron /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm > /dev/null 2>&1

On 31/05/2019 13:22, Stefan Bodewig wrote: > On 2019-05-31, sebb wrote: > >> The command: > >> /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm > >> /dev/null 2>&1 > >> should perhaps be > >> /usr/bin/find /tmp -type f -ctime +6 > /dev/null 2>&1 | /usr/bin/xargs >> -r /bin/rm >

Re: svn commit: r1829908 - /gump/metadata/project/eclipse.xml

On 23/04/18 18:00, bode...@apache.org wrote: > Author: bodewig > Date: Mon Apr 23 17:00:37 2018 > New Revision: 1829908 > > URL: http://svn.apache.org/viewvc?rev=1829908=rev > Log: > fix filename > > Modified: > gump/metadata/project/eclipse.xml > > Modified:

Re: BATCH: All dressed up, with nowhere to go...

On 22/04/18 20:02, Stefan Bodewig wrote: > On 2018-04-22, Mark Thomas wrote: > >> I think I've fixed this. > > Don't forget to update the checked out copy on vmgump-vm3 (I forgot to > do so for hamcrest-library :-). All good on that one. I didn't know the packages were in

Re: BATCH: All dressed up, with nowhere to go...

I think I've fixed this. Sorry for the noise. Mark On 22/04/18 18:46, g...@vmgump-vm3.apache.org wrote: > Dear Gumpmeisters, > > The following 1 notifys should have been sent > > *** G U M P > [GUMP@vmgump-vm3]: Project

Re: BATCH: All dressed up, with nowhere to go...

There was an svn glitch overnight. Things should sort themselves out in the next run. Mark On 15/03/18 01:23, g...@vmgump-vm3.apache.org wrote: > Dear Gumpmeisters, > > The following 24 notifys should have been sent > > *** G

Re: Is Gump still useful for you?

On 23/02/18 17:52, Stefan Bodewig wrote: > Hi all > > when writing Gump's quarterly report for the Apache board we usually > include the phrase "Gump seems to remain useful for the projects using > it". Back in September 2017 Gump builds stopped for several weeks and > nobody seems to have

Re: svn commit: r1817993 - /gump/metadata/project/tomcat-trunk.xml

On 14/12/17 13:18, Konstantin Kolinko wrote: > Hi, Mark! > > To dev@tomcat, cc: general@gump. > > > The result of this change is that Gump building Tomcat downloads > tar.gz for Commons-Daemon from mirrors. Drat. That wasn't the intention at all. > The "mvn package" command used by Gump

Re: Board Report

On 13/12/17 10:10, Stefan Bodewig wrote: > On 2017-12-13, Mark Thomas wrote: > >> On 13/12/17 09:37, Konstantin Kolinko wrote: >>> 2017-11-30 17:21 GMT+03:00 Stefan Bodewig <bode...@apache.org>: >>>> Hi all > >>>> current draft is >>

Re: Board Report

On 13/12/17 09:37, Konstantin Kolinko wrote: > 2017-11-30 17:21 GMT+03:00 Stefan Bodewig : >> Hi all >> >> current draft is >> https://wiki.apache.org/gump/Drafts/BoardReports/20171220 - I'll have to >> submit it in about two weeks. >> >> Back when vmgump failed in September I

Re: do we want to keep the vmgump.apache.org hostname?

On 08/11/2016 17:35, Stefan Bodewig wrote: > On 2016-11-08, Mark Thomas wrote: > >> On 08/11/2016 16:33, Stefan Bodewig wrote: > >>> the new machine is vmgump-vm3 rather than vmgump. Do we want to keep the >>> old name as an alias? > >> -0. I don't see

Re: do we want to keep the vmgump.apache.org hostname?

On 08/11/2016 16:33, Stefan Bodewig wrote: > Hi > > the new machine is vmgump-vm3 rather than vmgump. Do we want to keep the > old name as an alias? -0. I don't see a need but I have no objection if someone wants that. on a related issue, I can confirm I have access to the new vm. Mark

Re: vmgump is going to get turned off

On 07/11/2016 05:23, Stefan Bodewig wrote: > Hi all > > we've seen the first emails coming from vmgump-vm3 and I've just > (hopefully) fixed the workspace definition so the nag mails contain URIs > that point to the new machine. > > As a result the migration seems to be complete and infra is

Re: Gump on Mac OS X is back -- sort of

On 30/08/2016 19:45, Sander Temme wrote: > Dear Community, > > Having been pestered with two e-mails a day about failing Gump cron > jobs ever since I upgraded the OS on adam.apache.org to Mountain Lion > (Mac OS X 10.8), I finally found the time this week to put the Gump > installation back

Re: Gump is building stale Checkstyle sources (and other GitHub projects)

FYI. I have manually updated openssl-master and checkstyle to the latest source. Mark - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org

Re: svn commit: r1728586 - /gump/live/python/gump/core/update/git.py

On 05/02/2016 01:58, billbar...@apache.org wrote: > Author: billbarker > Date: Fri Feb 5 01:58:25 2016 > New Revision: 1728586 > > URL: http://svn.apache.org/viewvc?rev=1728586=rev > Log: > revert previous attempt. We can go back to fixing corrupt files the old > fashoned way. Thanks to

Updating Java

I'm updating the version of Java that Gump runs with to the latest Oracle Java 8 release. We may see some strange errors/failures. Mark - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands,

Re: BATCH: All dressed up, with nowhere to go...

On 24/06/2015 01:31, g...@vmgump.apache.org wrote: Dear Gumpmeisters, The following 20 notifys should have been sent *** G U M P [GUMP@vmgump]: Module apache-commons failed I've removed the broken externals caused by some

Re: Problem running Apache Gump [vmgump]

On 05/05/2015 00:00, g...@vmgump.apache.org wrote: There is a problem with run 'vmgump' (05052015_01), location : http://vmgump.apache.org/gump/public The log ought be at: http://vmgump.apache.org/gump/public/gump_log.txt

Re: Switching Gump to Java 8

Sorry this isn't a proper reply - I'm not subscribed to the list so I am reading the archives. I'll go ahead and switch vmgump to Java 8. Mark - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional

Switching Gump to Java 8

Folks, Work on Tomcat 9 has started which requires Java 8 as a minimum. Since there have been a few stable Java 8 releases now would it be possible to switch Gump over to use Java 8 rather than Java 7? I'm assuming it isn't possible to control this on a per project basis. If that is possible

JAR update request

Hi, Please could the Eclipse JDT jar be updated to version P20140317-1600 as this is now required by the Tomcat builds (to pick up Java 8 support). I did try to do this myself but I don't have sudo on vmgump so I couldn't make the change. Cheers, Mark

Re: JAR update request

On 20/03/2014 08:36, Stefan Bodewig wrote: On 2014-03-20, Mark Thomas wrote: Please could the Eclipse JDT jar be updated to version P20140317-1600 as this is now required by the Tomcat builds (to pick up Java 8 support). I would if I knew how to obtain it - I'm not an eclipse user myself

Investigating failing Tomcat trunk unit test

Hi, I've been unable to re-create the current Tomcat trunk unit test failure observed by Gump. Therefore, I'd like to request ssh access to vmgump in order to be able to run the unit test in the same environment, hopefully recreate the problem and fix it. Looking at the infrastructure repo, I

Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed

Stefan Bodewig bode...@apache.org wrote: On 2013-08-20, Mark Thomas wrote: On 18/08/2013 00:42, b...@apache.org wrote: snip/ build-only: [javac] Compiling 97 source files to /srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes [javac] /srv/gump/public/workspace

Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed

On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle]

Re: Your Gump Build(s)

On 24/06/2013 14:20, Stefan Bodewig wrote: Dear Community Apache Gump builds some of your projects and it is quite possible you don't know or have by now forgotten about it. More than half a year ago a technical problem has forced us to turn off emails on build failures as we would have