Re: mh_resolve_dependencies (was Re: Configuring Jersey Client in tomcat8)
- To: Thorsten Glaser <t.glaser@tarent.de>, Dominik George <nik@naturalnet.de>
- Cc: debian-java@lists.debian.org
- Subject: Re: mh_resolve_dependencies (was Re: Configuring Jersey Client in tomcat8)
- From: Emmanuel Bourg <ebourg@apache.org>
- Date: Fri, 2 Dec 2016 00:25:46 +0100
- Message-id: <[🔎] ad2c3d80-6973-8906-70a6-a9c622fa2421@apache.org>
- In-reply-to: <alpine.DEB.2.20.1611291320530.16515@tglase.lan.tarent.de>
- References: <20161127153450.4kkfbsb3d66x4uav@portux.lan.naturalnet.de> <20161127160633.7lsbusi4jvgchhc5@portux.lan.naturalnet.de> <alpine.DEB.2.20.1611291320530.16515@tglase.lan.tarent.de>
Le 29/11/2016 à 13:22, Thorsten Glaser a écrit : > Now, to the other real problem: how to tell mh_resolve_dependencies > to ignore some? (Case in point, multi-module project with parent POM > and several module POMs which depend on each other; the maven helper > stuff tries to find a Debian package for each dependency, even the > one we were just trying to compile.) Hi Thorsten, Do you have a link to the packaging repository? I'll get a look. Emmanuel Bourg
Reply to:
- Follow-Ups:
- Re: mh_resolve_dependencies (was Re: Configuring Jersey Client in tomcat8)
- From: Dominik George <nik@naturalnet.de>
- Re: mh_resolve_dependencies (was Re: Configuring Jersey Client in tomcat8)
- Prev by Date: Re: Fwd: Correct way to detect JAR dependencies
- Next by Date: Re: Fwd: Correct way to detect JAR dependencies
- Previous by thread: Re: Java version
- Next by thread: Re: mh_resolve_dependencies (was Re: Configuring Jersey Client in tomcat8)
- Index(es):