Le 14/11/2018 à 12:12, Mathieu Malaterre a écrit :
> So -again-, do you have a suggestion as to why the pom.xml has dropped
> reference to junit (compared to the original .save file). For
> reference my current maven.rules is:
Is junit ignored in debian/maven.ignoreRules?
Hi,
On Wed, Nov 14, 2018 at 11:57 AM Emmanuel Bourg wrote:
>
> Le 14/11/2018 à 11:25, Mathieu Malaterre a écrit :
>
> > What would you recommend in this case ?
>
> For junit this substitution rule should work:
>
> junit junit * s/.*/4.x/ * *
>
> And for xmlgraphics-commons:
>
> org.apache.xml
Le 14/11/2018 à 11:25, Mathieu Malaterre a écrit :
> What would you recommend in this case ?
For junit this substitution rule should work:
junit junit * s/.*/4.x/ * *
And for xmlgraphics-commons:
org.apache.xmlgraphics xmlgraphics-commons * s/.*/debian/ * *
Hi Emmanuel,
I believe I understand now why mh_make was getting confused all along
with junit4/xmlgraphics-commons. It turns out that fop made the
version of those configurable from the top-level parent to the
children, eg:
$ cd fop
$ cat fop-events/pom.xml
...
org.apache.xmlgraphics
Le 14/11/2018 à 09:59, Mathieu Malaterre a écrit :
> Depending on the order of the binary package in d/control, I get a
> different build. How can I specify for src:fop package that I'd like
> to build libfop-java and not fop.
Hi Mathieu,
Assuming all the jar files are installed in libfop-java I
Hi there,
Depending on the order of the binary package in d/control, I get a
different build. How can I specify for src:fop package that I'd like
to build libfop-java and not fop.
Otherwise it fails with:
dh binary --buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_aut
6 matches
Mail list logo
