Le 17/11/2014 03:16, Daniel Schepler a écrit :
By the way, after I built maven-jarjar-plugin with ant added, I got a
similar failure building sisu-guice:
I confirm this issue with a rebuilt version of velocity without a
dependency on Ant. This is caused by the pom of maven-jarjar-plugin
Source: jarjar-maven-plugin
Version: 1.9-2
Severity: important
In my locally rebuilt repository, ant is no longer automatically pulled in by
the Build-Depends of jarjar-maven-plugin (with the official package builds, it's
pulled in by velocity). As a result, I'm getting this error in the build:
Hi Daniel,
As I understand ant is pulled through
maven-debian-helper-velocity-ant. How did you manage to install the
build dependencies without ant installed?
Ant is a direct dependency so it would be a good idea to add it to the
build deps, but this error should not happen with the current
On 11/16/2014 09:53 AM, Emmanuel Bourg wrote:
Hi Daniel,
As I understand ant is pulled through
maven-debian-helper-velocity-ant. How did you manage to install the
build dependencies without ant installed?
Ant is a direct dependency so it would be a good idea to add it to the
build deps,
Daniel confirmed privately he rebuilt velocity locally. The pom.xml file
in velocity has a dependency on ant with the scope 'provided'. The
recent versions of maven-debian-helper no longer inject this kind of
dependencies in the package dependencies (because the provided
dependencies are usually
On Sun, Nov 16, 2014 at 11:26 AM, tony mancill tmanc...@debian.org wrote:
I believe what Daniel is saying is that if you rebuild the entire
dependency chain, ant isn't being pulled in (by velocity).
That's correct.
Or put another way, there is a difference between the dependency graph
that
6 matches
Mail list logo
