On Mon, Dec 7, 2020 at 8:19 PM Markus Koschany <a...@debian.org> wrote: > > Am Montag, den 07.12.2020, 15:33 +0100 schrieb Thorsten Glaser: > > On Mon, 7 Dec 2020, Markus Koschany wrote: > > > > > Ideally the Butterfly source code is included in src:openrefine and Maven > > > would > > > do the rest. > > > > Does maven-debian-helper handle multi-module projects (where some of > > the modules depend on some of the other modules to be built as part > > of the project) nowadays? That was the biggest problem, back when I > > tried to package something… > > I don't think it does. Last time I stumbled upon this problem I had to patch > the pom.xml and use the scope=system approach. > > <dependency> > <groupId>foo</groupId> > <artifactId>bar</artifactId> > <version>1.0</version> > <scope>system</scope> > <systemPath>../../some.jar</systemPath> > </dependency>
I recently worked on uploading eclipse-tracecompass which had this situation and I have not used "scope=system". Just adding the dependency in pom.xml was enough (which will take "scope=compile" by default). As an example 'org.eclipse.tracecompass.analysis.counters.core' depends on 'org.eclipse.tracecompass.common.core' and was just mentioned in pom.xml at [1] which was sufficient. Same was done for all the other modules and its interdependencies. [1]. https://salsa.debian.org/java-team/eclipse-tracecompass/-/blob/master/debian/pom/analysis/org.eclipse.tracecompass.analysis.counters.core/pom.xml#L46 -- Regards Sudip
