Both the jdk-1.6-parent and jdk-1.5-parent fail building with missing artifacts:
jdk-1.6: 1 required artifact is missing. for artifact: org.wicketstuff:javaee-inject-example-war:war:1.5-SNAPSHOT jdk1.5: 1) org.wicketstuff:wicket-osgi-test-service:jar:1.5-SNAPSHOT 2) org.wicketstuff:wicketstuff-osgi:jar:1.5-SNAPSHOT 3) org.wicketstuff:wicketstuff-ioc-bundle:jar:1.5-SNAPSHOT I Haven't Lost My Mind - It's Backed Up On Disk Somewhere On Mon, Jul 4, 2011 at 19:51, Ron Smits <ron.sm...@gmail.com> wrote: > Actually looking at the output at > http://wicketstuff.org/hudson/job/Wicket%20Stuff%20Core%20Java6%20%28wicket%201.4-SNAPSHOT%29/lastFailedBuild/consoleyou > will see that it cannot find the git program: This is actually the > giveaway: > > Cannot run program "git": java.io.IOException: error=2, No such file or > directory > > Ron > > I Haven't Lost My Mind - It's Backed Up On Disk Somewhere > > > On Mon, Jul 4, 2011 at 19:42, Martin Grigorov <mgrigo...@apache.org>wrote: > >> Hi, >> >> I think Michael O'Cleiri has its own Jenkins which is building regularly. >> >> I have ssh access to wicketstuff.org but I haven't administrated Jenkins >> so far. >> What should be done ? >> >> On Mon, Jul 4, 2011 at 7:37 PM, Harald Wellmann <harald.wellm...@gmx.de> >> wrote: >> > Am 03.07.2011 15:09, schrieb Attila Király: >> >> >> >> I don't know about other public wicketstuff related CI server. >> >> In my experience wicketstuff hudson/jenkins was broken for most of the >> >> time >> >> during this year. >> > >> > Oh cool, so Wicketstuff is the leader in Discontinuous Integration ;-) >> > >> >> Currently it seems it can not connect to the remote github repository >> >> (could >> >> be dns related, it had problems with that in the past). >> >> >> > >> > Ok, but then it shouldn't be too difficult to fix if the Jenkins admin >> and >> > the sysadmin of the box it's running on worked together. >> > >> > So what's the root cause? >> > >> > a) At least one of these two admin roles is not assigned. >> > b) Ping pong between the two roles. >> > c) Admin not aware of problem. >> > d) No time to fix it. >> > e) No permissions to fix it. >> > f) Does not know how to fix it. >> > >> > Identifying the blocker issue is the first step to remove it... >> > >> > Regards, >> > Harald >> > >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> > >
