Re: Re: Configurable version in artifactId

2018-11-20 Thread Mathieu Malaterre
> Is junit ignored in debian/maven.ignoreRules? Indeed, I failed to understand the role of maven.ignoreRules. Sorry for the noise

Re: Configurable version in artifactId

2018-11-14 Thread Emmanuel Bourg
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?

Re: Configurable version in artifactId

2018-11-14 Thread Mathieu Malaterre
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

Re: Configurable version in artifactId

2018-11-14 Thread Emmanuel Bourg
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/ * *

Configurable version in artifactId

2018-11-14 Thread Mathieu Malaterre
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