Hello,
It looks like two builds from the maven-3.x-jenkinsfile Jenkins
project are stuck on the Windows nodes (on both windows machines).
Both seem to be running for over 6 days and are holding up 3 executors
(possibly slowing down other builds that want to run on Windows).
The builds are:
- mave
On 2017-02-07T11:47:16 +
org.apache.maven.u...@io7m.com wrote:
> Here's an example project that uses version ranges to specify
> intra-project dependencies between modules:
>
> https://github.com/io7m/independent-versioning-20170207
Interestingly, these issues don't
oject that uses version ranges to specify
intra-project dependencies between modules:
https://github.com/io7m/independent-versioning-20170207
When attempting to build this project, the assembly plugin can't find
the modules even though they're part of the reactor build:
[ERROR] Fa
Hi,
there's currently a discussion in JIRA regarding MNG-5576 (Zips on classpth)
and Michael Osipov suggested to bring the discussion to the dev list.
Actually this already happened once last August:
Paul Benedict wrote:
> I would like to reopen MNG-5567 because I find the solution incomplete