On 04/29/2013 04:36 AM, Stephen Connolly wrote:
Turns out this is actually a rather nasty bug in Jenkins' Maven project type
https://issues.jenkins-ci.org/browse/JENKINS-17775
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscri
Go on then I'll bite...
If we had a useable alternative then we may not all be using it...
this includes (of the top of my head)
* knowing what is installed (by maven) so that it (can be optionally)
automatically added as an archive.
* plugins that don’t fail the build when the foobar.xml
On Fri, Apr 26, 2013 at 4:03 PM, Mirko Friedenhagen
wrote:
> the job is trying to get maven-hpi-plugin-1.74 from central and fails because
> of this
Yes a bunch of BuildHive jobs for Jenkins plugins got broken recently
due to a change in Maven mirror handling. We are working on
determining the r
Hello,
please take a look at
https://buildhive.cloudbees.com/job/jenkinsci/job/jswidgets-plugin/9/org.jenkins-ci.plugins$jswidgets/console
While the build itself seems to succeed, a goal running afterwards
does not. It seems the job is trying to get maven-hpi-plugin-1.74 from
central and fails b
