On Tue 28 Nov 2017 at 07:25, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Tue 28 Nov 2017 at 06:53, Hervé BOUTEMY wrote:
>
>> awesome!
>> It even shows the owl icon :)
>>
>> now, every build looks to fail, and I can't open Blue Ocean to try to
>> figure
>
>
I think that’s beca
On Tue 28 Nov 2017 at 06:53, Hervé BOUTEMY wrote:
> awesome!
> It even shows the owl icon :)
>
> now, every build looks to fail, and I can't open Blue Ocean to try to
> figure
> out at which step. From log, IIUC, there is an issue with JDK 9: that's it?
Yes jdk 9 on Windows. Gavin asked Chris
awesome!
It even shows the owl icon :)
now, every build looks to fail, and I can't open Blue Ocean to try to figure
out at which step. From log, IIUC, there is an issue with JDK 9: that's it?
We're really in the right direction: soon, we'll be ready to start plugins (40
plugins) and shared (20
PARTY PARTY PARTY TIME
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
On 22 November 2017 at 09:48, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Scheduled for the November 26th upgrade: https://cwiki.apache.
> org/confluence/display/INFRA/Jenkins+Plugin+Upgrades
>
>
Scheduled for the November 26th upgrade:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins+Plugin+Upgrades
On 21 November 2017 at 14:46, Arnaud Héritier wrote:
> yeah !!
>
> On Tue, Nov 21, 2017 at 2:10 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > https://issues
yeah !!
On Tue, Nov 21, 2017 at 2:10 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/INFRA-15524
>
> Hervé it is nearly time to party!
>
--
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype :
Am 2017-03-16 um 19:53 schrieb Stephen Connolly:
Don't be shooting the messenger!
Not my intention.
I'm suspecting that it would be a case of sponsoring a node on AWS or rack
space or Google's cloud.
That would have a static IP, could be isolated from any corporate networks
and there you go!
Don't be shooting the messenger!
I'm suspecting that it would be a case of sponsoring a node on AWS or rack
space or Google's cloud.
That would have a static IP, could be isolated from any corporate networks
and there you go!
But anyway, this is more that there is a route available... that the r
> -Original Message-
> From: Michael Osipov
>
> Am 2017-03-16 um 13:39 schrieb Stephen Connolly:
> > https://reference.apache.org/committer/node-hosting
> >
> > So if somebody really feels that we need exotic node types... and is
> > willing to provide such a node and hook it up...
>
> T
Am 2017-03-16 um 13:39 schrieb Stephen Connolly:
https://reference.apache.org/committer/node-hosting
So if somebody really feels that we need exotic node types... and is
willing to provide such a node and hook it up...
This is somewhat ridiculous. Exotic is HP-UX or AIX, but CentOS, Solaris
a
+1 with Robert's solution (though I don't remember it was the actual issue
for that ci build failure some weeks ago...).
That's something I've also been planning to do after working recently with
buildnumber. BTW, not sure yet why, but sometimes IT won't fail doing a svn
info under the hood althou
ASF Jenkins has some hikkups these days + now the mail outage =
since last time, I coded the svn upgrade thing, and I even downgraded the .svn
directory in sources to svn 1.6 to match version used by ASF Jenkins
everything should be ok now on this front
on the ASF Jenkins front, problems are so
This issue is very stubborn -)
I saw Hervé make a few changes, but builds.apache.org also have not
triggered a new build? what is the schedule for this job?
-Dan
On Thu, May 8, 2014 at 9:25 AM, Robert Scholte wrote:
> it's probably something like .execute( null, basedir ) to ensure the righ
Yes, it is a better approach since the build is currently falling at ubuntu
build at builds.apache.org
-D
On Tue, May 6, 2014 at 3:14 PM, Hervé BOUTEMY wrote:
> I think Roberts' idea about "svu upgrade"ing is good
> just need to revert locally and test, or we'll get the same problem in some
>
it's probably something like .execute( null, basedir ) to ensure the right
working directory is used.
Robert
http://groovy.codehaus.org/groovy-jdk/java/lang/String.html#execute%28java.util.List,%20java.io.File%29
Op Wed, 07 May 2014 00:14:07 +0200 schreef Hervé BOUTEMY
:
I think Roberts
I think Roberts' idea about "svu upgrade"ing is good
just need to revert locally and test, or we'll get the same problem in some
time, when svn 1.9 is out
Regards,
Hervé
Le mardi 6 mai 2014 15:00:58 Dan Tran a écrit :
> Thanks Hervé, it works on my local windows build with svn client 1.8.5
>
Thanks Hervé, it works on my local windows build with svn client 1.8.5
-D
On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY wrote:
> I updated content to svn 1.8: not really a long term solution, but at least
> give us time to find a better solution
>
> Regards,
>
> Hervé
>
> Le lundi 5 mai 2014
Just tried it and still failing ( but not known why yet)
[INFO] --- maven-invoker-plugin:1.8:run (integration-test) @
maven-scm-plugin ---
[INFO] Building: scm-741-validate-scm-url-matches-working-copy\pom.xml
[INFO] run script prepare.groovy
[INFO] ..FAILED (6.6 s)
[INFO] The build exited with
I updated content to svn 1.8: not really a long term solution, but at least
give us time to find a better solution
Regards,
Hervé
Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit :
> perhaps, we need to disable this specific test for now?
>
> -D
>
> On Mon, May 5, 2014 at 9:18 PM, Dan Tran wrot
Would it help if this was added to the prepare.groovy?
try
{
"""svn upgrade""".execute()
}
catch( Exception e )
{
// noop, no need to upgrade
}
return true
I seem to have a matching client version, so the IT works on my system.
Could someone verify the code above?
thanks,
Robert
Op Tue,
perhaps, we need to disable this specific test for now?
-D
On Mon, May 5, 2014 at 9:18 PM, Dan Tran wrote:
>
> Looks like we stuck without a new snapshot until this is fixed!!
>
> -D
>
>
> On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY wrote:
>
>> seems related to SCM-741: the IT added contains
Looks like we stuck without a new snapshot until this is fixed!!
-D
On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY wrote:
> seems related to SCM-741: the IT added contains a copy of .svn content
> taken
> from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a
> different one (
seems related to SCM-741: the IT added contains a copy of .svn content taken
from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a
different one (format 31)
don't know how wa can improve the IT to be more tolerant to svn version
updates
Regards,
Hervé
Le lundi 5 mai 2014 0
change list https://builds.apache.org/job/maven-scm/changes
-D
On Mon, May 5, 2014 at 9:01 AM, Dan Tran wrote:
>
>
>
> https://builds.apache.org/job/maven-scm/
>
> Thanks
>
> -D
>
To be precise, the site descriptors are completely missing from central
for the three parents I released, i.e.:
- maven-parent:14
- maven-plugins:15
- maven-shared-components:13
effectively making those parents useless.
I was thinking about just adding those files (which are both tagged and
i
I haven't work on it for a few weeks. So go ahead and do your release.
We can call what I have a different version later. I'll have no time
in the next month to push it in.
On 14-Aug-08, at 6:06 AM, Lukas Theussl wrote:
Jason,
Do you have any updates on that?
Vincent is urging me to prepa
Had this flagged to take a look. No source (can't find it in
subversion), no website (can't find it on opensource.atlassian.com),
no javadoc, no license... not really sure what I can do with this :)
Was it submitted via JIRA for inclusion in Maven somewhere?
- Brett
On 14/11/2006, at 3:27 P
I'm taking a response to plexus-dev. Basically, +1.
On 06/12/2006, at 9:26 AM, Joakim Erdfelt wrote:
ooh! Logging fight! logging fight! ;-)
(Jason and I argue about this constantly)
Paul Hammant's blog entry - http://paulhammant.com/blog/000241.html
He was railing on about...
* Instantiating
ooh! Logging fight! logging fight! ;-)
(Jason and I argue about this constantly)
Paul Hammant's blog entry - http://paulhammant.com/blog/000241.html
He was railing on about...
* Instantiating logging using IoC techniques.
* Using static logging in a component.
* Logging is mostly never read.
He
On 3 Dec 06, at 11:29 PM 3 Dec 06, Carlos Sanchez wrote:
I think something like http://www.slf4j.org/ can allow using libraries
that use commons-logging without getting its problems
I didn't see it in there anyway, but the problem is not only that
commons-logging is a piece of crap, but tha
I think something like http://www.slf4j.org/ can allow using libraries
that use commons-logging without getting its problems
On 12/2/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 2 Dec 06, at 1:51 PM 2 Dec 06, Henri Yandell wrote:
> Brett mentioned on IRC that plexus is trying to move off of
On 2 Dec 06, at 1:51 PM 2 Dec 06, Henri Yandell wrote:
Brett mentioned on IRC that plexus is trying to move off of
plexus-utils, so I've started moving Archiva off and onto the
originals from which plexus-utils was forked. That should hopefully
get me slowly into understanding what's in plexus-
Yes, it can, as it uses some code from PropertyUtil. The code may be a bit
ugly though, as the latest version of Maven Embedder (2.0.4) doesn't seem to
work properly with the code.
Stephane Nicoll-2 wrote:
>
> Hi,
>
> I think this can include the resources filtering we need in various
> mojos
Hi,
I think this can include the resources filtering we need in various
mojos, right?
WDYT?
Stéphane
On 11/14/06, Tony Truong <[EMAIL PROTECTED]> wrote:
Hi guys,
For your interest, I have made a library which we have found useful here
down in Atlassian.
http://repository.atlassian.com/maven
34 matches
Mail list logo
