Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-27 Thread Stephen Connolly
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

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-27 Thread Stephen Connolly
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

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-27 Thread Hervé BOUTEMY
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

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-27 Thread Stephen Connolly
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 > >

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-22 Thread Stephen Connolly
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

Re: FYI INFRA-15524 created for the better Jenkins UX

2017-11-21 Thread Arnaud Héritier
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 :

FYI INFRA-15524 created for the better Jenkins UX

2017-11-21 Thread Stephen Connolly
https://issues.apache.org/jira/browse/INFRA-15524 Hervé it is nearly time to party!

FYI I rebased the MNG-6069 and MNG-6216 to pick up e44c39c

2017-08-29 Thread Stephen Connolly
https://github.com/apache/maven/commit/e44c39c2eb5afda9efe60b9dd0ffc32c62501c5f fixes the Jenkinsfile after the changes introduced by JENKINS-43507 so in order to get those two branches to have a realistic integration test result status I have `git push --force-with-lease` these two branches after

Re: FYI: on exotic nodes for our CI

2017-03-16 Thread Michael Osipov
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!

Re: FYI: on exotic nodes for our CI

2017-03-16 Thread Stephen Connolly
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

RE: FYI: on exotic nodes for our CI

2017-03-16 Thread Jason Pyeron
> -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

Re: FYI: on exotic nodes for our CI

2017-03-16 Thread 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... This is somewhat ridiculous. Exotic is HP-UX or AIX, but CentOS, Solaris a

FYI: on exotic nodes for our CI

2017-03-16 Thread 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...

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-15 Thread Baptiste Mathus
+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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-11 Thread Hervé BOUTEMY
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-10 Thread Dan Tran
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-10 Thread Dan Tran
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 >

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-10 Thread Robert Scholte
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-06 Thread Hervé BOUTEMY
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 >

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-06 Thread Dan Tran
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-06 Thread Dan Tran
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-06 Thread Hervé BOUTEMY
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-06 Thread Robert Scholte
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,

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-05 Thread Dan Tran
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-05 Thread Dan Tran
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 (

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-05 Thread Hervé BOUTEMY
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

Re: [FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-05 Thread Dan Tran
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 >

[FYI] maven-scm-plugin IT is failing since Feb 25

2014-05-05 Thread Dan Tran
https://builds.apache.org/job/maven-scm/ Thanks -D

Re: FYI: site descriptor is messed up for org.apache.maven.plugins:maven-plugins:15

2009-10-29 Thread Benjamin Bentmann
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

FYI: site descriptor is messed up for org.apache.maven.plugins:maven-plugins:15

2009-10-29 Thread Stephen Connolly
Benjamin is on the case This is just an FYI -Stephen

FYI: I've had some SMTP troubles

2009-03-29 Thread Dennis Lundberg
Hi all If my mails seems to have come out of order lately, it's because I've had to resend them. My ISP has changed their SMTP server, but the old one still responded. It simply swallowed all my messages without complaining... -- Dennis Lundberg -

Re: FYI

2008-08-14 Thread Jason van Zyl
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

plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or... - FYI

2007-08-07 Thread Praveen Kumar Kumashi
other similar issues. For some reason, the web repo for some plugins gets updated with SNAPSHOT versions, when it should not have been. Mailing this since I did not find similar info either in faqs nor in mailing lists. FYI, Thanks, praveen

Re: FYI: Developing maven utility library

2006-12-22 Thread Brett Porter
use maven specific variables (e.g. ${basedir}, ${pom.artifactId}) Not sure how I will notify people of changes as of yet. Comments? Suggestions? Regards, Tony -- View this message in context: http://www.nabble.com/FYI%3A- Developing-maven-utility-library-tf2627249s177.html#a7331336 Sent from

Re: Logging Fight! (and suggestion) - Was: Re: FYI: de-plexus-utils'ing

2006-12-05 Thread Brett Porter
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

Logging Fight! (and suggestion) - Was: Re: FYI: de-plexus-utils'ing

2006-12-05 Thread Joakim Erdfelt
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

Re: FYI: de-plexus-utils'ing

2006-12-03 Thread Jason van Zyl
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

Re: FYI: de-plexus-utils'ing

2006-12-03 Thread Carlos Sanchez
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

Re: FYI: de-plexus-utils'ing

2006-12-02 Thread Jason van Zyl
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-

FYI: de-plexus-utils'ing

2006-12-02 Thread Henri Yandell
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-utils and how they can either be replaced by other compone

Re: FYI: Developing maven utility library

2006-11-14 Thread Tony Truong
gt;> ${pom.artifactId}) >> >> Not sure how I will notify people of changes as of yet. Comments? >> Suggestions? >> >> Regards, >> >> Tony >> -- >> View this message in context: >> http://www.nabble.com/FYI%3A-Developing-maven-utility-l

Re: FYI: Developing maven utility library

2006-11-14 Thread Stephane Nicoll
age in context: http://www.nabble.com/FYI%3A-Developing-maven-utility-library-tf2627249s177.html#a7331336 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional co

FYI: Developing maven utility library

2006-11-13 Thread Tony Truong
}, ${pom.artifactId}) Not sure how I will notify people of changes as of yet. Comments? Suggestions? Regards, Tony -- View this message in context: http://www.nabble.com/FYI%3A-Developing-maven-utility-library-tf2627249s177.html#a7331336 Sent from the Maven Developers mailing list archive at

FYI [Fwd: [JCI] proposed contribution]

2005-05-10 Thread Brett Porter
I don't think I dropped this here yet. If anyone is interested, please join commons-dev. Cheers, Brett --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've been looking over JCI (Java Compiler Interface) in the sandbox and have quickly checked in with Torsten about it's c

FYI - Submitted a patch to the Ant project for the JUnit task that allows a single test method to be executed

2005-05-04 Thread sissonj
FYI.. I have submitted a patch to the Ant project for the JUnit task that allows a single test method to be executed. If accepted, I will also create a simple patch for the Maven-1 Test plug-in to take advantage of it. See http://issues.apache.org/bugzilla/show_bug.cgi?id=34748 for details

FYI

2004-02-06 Thread Jason van Zyl
Howdy, I'll be shunting in a lot of code but it won't be ready until Monday I'm just afraid of losing anything on my machine here so I'm checking it in. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude