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 fixed now.
The next
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,
>
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
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 svn. I added
the JAR
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 :-).
Stefan
-
To unsubscribe, e-mail:
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
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
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
Dear Plutomeisters,
g...@vmgump.apache.org wrote:
Dear Gumpmeisters,
The following 1 notifys should have been sent
*** G U M P
[g...@vmgump]: Project portals-pluto-trunk-test (in module
[portals-pluto-trunk) failed
[EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 5 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project xstream (in module xstream) failed
[snip]
Tried to fix the descriptor...
- Jörg
On Sep 9, 2006, at 5:51 AM, [EMAIL PROTECTED] wrote:
The following work was performed:
http://vmgump.apache.org/gump/public/jaxen/gump_work/update_jaxen.html
Work Name: update_jaxen (Type: Update)
Work ended in a state of : Failed
Elapsed:
Command Line: cvs -q -z3 -
d :pserver:[EMAIL
Gotta love this response:
-[99ABF8]
Leo Simons,
Your ticket concerning 'Ticket: aanval.com mailconfig' has a new response.
Message:
System is operating as intended. Loop was already in place and prevented
further damage past 10 messages.
Ticket
Leo Simons wrote:
Gotta love this response:
-[99ABF8]
Leo Simons,
Your ticket concerning 'Ticket: aanval.com mailconfig' has a new response.
Message:
System is operating as intended. Loop was already in place and prevented further damage past 10
On Mon, 31 Jul 2006, Leo Simons [EMAIL PROTECTED] wrote:
Gotta love this response:
Nice, really.
---
Instruction:
To respond, simply use the reply button within your email client.
---
I like this part as well.
I unsubscribed the Aanval address BTW.
Stefan
This message is for all users sending submissions to [EMAIL PROTECTED];
** This address is no longer receiving support or assistance submissions. **
Aanval now requires all support and assistance requests to be entered into our
new form based support ticket system.
To submit for support or
This message is for all users sending submissions to [EMAIL PROTECTED];
** This address is no longer receiving support or assistance submissions. **
Aanval now requires all support and assistance requests to be entered into our
new form based support ticket system.
To submit for support or
-Original Message-
From: Sander Temme [mailto:[EMAIL PROTECTED]
Sent: Sun 3/5/2006 4:39 PM
To: Gump code and data
Subject: Re: BATCH: All dressed up, with nowhere to go...
On Mar 5, 2006, at 2:43 AM, [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]: Project junit (in module junit) failed
Bill Barker wrote on Monday, March 06, 2006 2:12 AM:
-Original Message-
From: Sander Temme [mailto:[EMAIL PROTECTED]
Sent: Sun 3/5/2006 4:39 PM
To: Gump code and data
Subject: Re: BATCH: All dressed up, with nowhere to go...
On Mar 5, 2006, at 2:43 AM, [EMAIL PROTECTED] wrote
On Nov 1, 2005, at 9:31 PM, Stefan Bodewig wrote:
Can you use a striplinebreaks filter reader in your loadfile task?
Definitely. I hadn't thought of that. Checked in, should build
tomorrow. Thanks again, Stefan!
andrew
On Mon, 31 Oct 2005, Andrew McIntyre [EMAIL PROTECTED] wrote:
This output, recorded to a file using the output attribute of an Ant
exec task, is then read back in to a property using Ant's
loadfile task. Ant diligently includes the newline as a part of
the property read in from the file,
On Oct 29, 2005, at 6:31 AM, Stefan Bodewig wrote:
I can't promise to find time to do more research
No worries, I got it. :-)
Most trivial idea: ${changenumber} expands to a value that ends with a
new-line or a cariage-return new-line sequence.
This guess is correct, and it turns out
On Oct 31, 2005, at 12:12 AM, Andrew McIntyre wrote:
it turns out that it's a subversion problem, not an Ant or platform
issue. The problem is that 'svnversion -n .' is returning a value
that contains a newline when the directory whose version you are
getting is 'exported,' when it should
On Wed, 26 Oct 2005, Andrew McIntyre [EMAIL PROTECTED] wrote:
That's what I suspected, but any idea why Ant would do that on
vmgump, but not elsewhere?
I can't promise to find time to do more research
Here's the first few lines of the manifest task:
manifest
Hi andrew,
Don't really understand the problem but I've put the db-derby dir from
vmgump at
http://vmgump.apache.org/derby-gump-snapshot.tgz
please holler when we can remove it.
cheers!
Leo
On Tue, Oct 25, 2005 at 03:11:01PM -0700, Andrew McIntyre wrote:
Just noticed that this is still
On Oct 27, 2005, at 7:19 AM, Leo Simons wrote:
Hi andrew,
Don't really understand the problem but I've put the db-derby dir from
vmgump at
http://vmgump.apache.org/derby-gump-snapshot.tgz
please holler when we can remove it.
I've got the file, so you can go ahead and remove it.
Thanks
On Tue, 25 Oct 2005, Andrew McIntyre [EMAIL PROTECTED] wrote:
Just noticed that this is still failing. I am unable to reproduce
the problem.
At least on vmgump there is an empty line in smf.mf between
Bundle-Version in the main section and Sealed: true. This line makes
the Sealed attribute
On Oct 26, 2005, at 9:22 PM, Stefan Bodewig wrote:
At least on vmgump there is an empty line in smf.mf between
Bundle-Version in the main section and Sealed: true. This line makes
the Sealed attribute the first one of a new section, which in turn
makes the manifest invalid.
That's what I
Just noticed that this is still failing. I am unable to reproduce the
problem. Please see my previous mail concerning this problem. It would
appear on the surface to be an issue with how Ant generates the
manifest file in the derbyjarwithoutosgi target. Is there any way
that I can get access to
On Aug 19, 2005, at 5:27 AM, [EMAIL PROTECTED] wrote:
derbyjarwithoutosgi:
[jar] Building jar: /x1/gump/public/workspace/db-derby/jars/
insane/derby.jar
[jar] Manifest is invalid: Manifest sections should start
with a Name attribute and not Sealed
BUILD FAILED
On Mon, 15 Aug 2005, Andrew McIntyre [EMAIL PROTECTED] wrote:
I've attached a patch which updates the URLs (and adds
repository/db-svn.xml),
Didn't reach the list, but I think I managed to guess it.
but I think someone is going to have to go to where the source is
checked out on vmgump and
On 8/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 11 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module db-derby success, but with warnings.
On 24-06-2005 15:25, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Fri, 24 Jun 2005, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Yes, I look for module failures and even worse for module success
but with warnings. The later usually means stuff has been moved
in svn, we are now unable to check it
On Mon, 27 Jun 2005, Leo Simons [EMAIL PROTECTED] wrote:
FWIW, the algorithm I have in my head (come to apachecon! We can
talk about it! :-))
I'll be there - and at the hackathon. Plenty of time to discuss it.
would mean that a migrated project would be *-ed, ie built and
linked against
Does anyone ever do anything with the content of these messages?
Yes, I look for module failures and even worse for module success but
with warnings. The later usually means stuff has been moved in svn,
we are now unable to check it out, but Gump doesn't consider it a
failure.
Stefan
Does anyone ever do anything with the content of these messages?
Yes, I look for module failures and even worse for module success but
with warnings. The later usually means stuff has been moved in svn,
we are now unable to check it out, but Gump doesn't consider it a
failure.
Want
On Fri, 24 Jun 2005, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Yes, I look for module failures and even worse for module success
but with warnings. The later usually means stuff has been moved
in svn, we are now unable to check it out, but Gump doesn't
consider it a failure.
Want this to
Hi gang,
Does anyone ever do anything with the content of these messages? I tend to
use them as a gauge of gump ran and it sent e-mail, but as the actual
content I would much rather have something like a list of
failures/successes, i.e. a condensed version of log.html.
Do you agree? Just
regards,
Adam
- Original Message -
From: Leo Simons [EMAIL PROTECTED]
To: Gump code and data general@gump.apache.org
Sent: Thursday, June 23, 2005 1:26 PM
Subject: Re: BATCH: All dressed up, with nowhere to go...
Hi gang,
Does anyone ever do anything with the content of these messages
On Thu, 24 Mar 2005, [EMAIL PROTECTED] wrote:
failed -ERROR- Synchronize Failed: Unicode Error. Can't copy
['spec1109ab\xe7d\xe9'] in
[u'/usr/local/gump/public/workspace/cvs/xml-xalan/test/tests/accept/spec11']
to
[u'/usr/local/gump/public/workspace/xml-xalan/test/tests/accept/spec11']:
does this mean that you worked around log4j?
On Nov 30, 2004, at 1:10 PM, [EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 2 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module jakarta-velocity success
[EMAIL
Hi all, I am a bit confused by this.. Is this message saying that the
module level work, which I guess is checking out from CVS, worked properly,
but then the build failed? I followed the link provided and everything says
Success.
Eric
-Original Message-
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 4 notifys should have been sent
[EMAIL PROTECTED]: Module lenya success, but with warnings.
There is something wrong. Lenya is not successful at all!
--
Stefano.
[EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 4 notifys should have been sent
[EMAIL PROTECTED]: Module lenya success, but with warnings.
There is something wrong. Lenya is not successful at all!
This stems from the old days when SF.net CVS was so flaky. Basically, if we
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]: Module james-server success, but with warnings.
this should be fixed (was looking in the wrong directory of the repository)
[EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings.
this is due to this line
Gump wrote:
Dear Gumpmeisters,
The following 1 notifys should have been sent
Sorry folks, this run got away on me. Please go about your business,
nothing to see here. :)
--
Sometimes the Universe needs a change of perspective.
--J. Michael Straczynski
smime.p7s
Description:
On Thu, 14 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote:
Instead, I suggest that we take the prettyprinter.jar from the
xdoclet CVS and make it into an installed package in Gump.
Just create a project for it inside xdoclet's descriptor. Name it
xdoclet-pretty or something. No need to
-Original Message-
From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
Sent: 14 October 2004 06:59
To: Gump code and data
Subject: Re: BATCH: All dressed up, with nowhere to go...
On Thursday 14 October 2004 12:33, Niclas Hedhman wrote:
I would suggest we mavenize xdoclet
On Thursday 14 October 2004 14:38, Stefan Bodewig wrote:
On Thu, 14 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote:
Instead, I suggest that we take the prettyprinter.jar from the
xdoclet CVS and make it into an installed package in Gump.
Just create a project for it inside xdoclet's
Niclas Hedhman wrote:
On Thursday 14 October 2004 12:33, Niclas Hedhman wrote:
I would suggest we mavenize xdoclet and remove jrefactory and friends
since they are clearly not enough friends of gump to live in the house
with him.
I will start on it straight away...
IIUIC, Xdoclet is not yet
Stefan Bodewig wrote:
On Thu, 14 Oct 2004, Niclas Hedhman [EMAIL PROTECTED] wrote:
Instead, I suggest that we take the prettyprinter.jar from the
xdoclet CVS and make it into an installed package in Gump.
Just create a project for it inside xdoclet's descriptor. Name it
xdoclet-pretty or
On Thursday 14 October 2004 12:33, Niclas Hedhman wrote:
I would suggest we mavenize xdoclet and remove jrefactory and friends
since they are clearly not enough friends of gump to live in the house
with him.
I will start on it straight away...
IIUIC, Xdoclet is not yet Mavenized. They
On Thursday 14 October 2004 12:17, Stefano Mazzocchi wrote:
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]: Project findbugs (in module findbugs) failed
[javac] Compiling 371 source files to
/usr/local/gump/public/workspace/findbugs/build/classes [javac] javac:
invalid target release:
At 11:45 AM 8/23/2004, you wrote:
Dear Gumpmeisters,
The following 13 notifys should have been sent
*** G U M P
[snip]
[EMAIL PROTECTED]: jetty/jetty-plus failed
*** G U M P
[snip]
Stefan Bodewig wrote:
[EMAIL PROTECTED]: mx4j/mx4j-tools-from-packaged-jetty failed
The top item on my TODO list. A real API compatibility problem
between mx4j and Axis.
hehehe. It's high on mine too...I need jetty to build :D
Another random thought: it would be nice to be able to annotate parts
On Thu, 25 Mar 2004, Leo Simons [EMAIL PROTECTED] wrote:
hehehe. It's high on mine too...I need jetty to build :D
You can fall back to the packaged jetty for the time being.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Wed, 24 Mar 2004, Stefan Bodewig [EMAIL PROTECTED] wrote:
Tapestry is a problem in itself, since the Gump descriptor is inside
the tapestry module. A manual nag together with a patch to the
descriptor may help. Number two on my TODO list, helping hands
welcome 8-)
Actually it is number
On Tue, 23 Mar 2004, Adam Jack [EMAIL PROTECTED] wrote:
Can we find a community e-mail address that would possible be
willing to 'hear' these, and approach them?
Difficult, the issues are too diverse.
Let's look at them case by case
[EMAIL PROTECTED]: webwork/webwork failed
At least one
]
Sent: Tuesday, March 16, 2004 9:09 AM
Subject: Re: BATCH: All dressed up, with nowhere to go...
[EMAIL PROTECTED] wrote:
Dear Gumpmeisters,
The following 6 nags should have been sent
G U M P
[EMAIL PROTECTED]: webwork/webwork
anywhere
to be sent -- hence they return to the Gumpmeisters.
I believe Nicola has plans for javasrc.
regards
Adam
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Tuesday, March 16, 2004 9:09 AM
Subject: Re: BATCH: All dressed up
this is a very cool feature. I just love all the intelligence that gump
is developing lately!
--
cheers,
- Leo Simons
---
Weblog -- http://leosimons.com/
IoC Component Glue -- http://jicarilla.org/
Articles
60 matches
Mail list logo
