Re: Fwd: Correct way to detect JAR dependencies

[Jose Gutierrez de la Concha <jose@zeroc.com>]

Hi Emmanuel,

My JAR has already a Class-Path entry in MANIFEST.MF

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.7
Created-By: 1.8.0_102-8u102-b14.1-2-b14 (Oracle Corporation)
Main-Class: IceGridGUI.Main
Class-Path: file:///usr/share/java/ice-3.6.3.jar file:///usr/share/java/icelocatordiscovery-3.6.3.jar file:///usr/share/java/icebox-3.6.3.jar file:///usr/share/java/icestorm-3.6.3.jar file:///usr/share/java/glacier2-3.6.3.jar file:///usr/share/java/icegrid-3.6.3.jar file:///usr/share/maven-repo/com/jgoodies/jgoodies-looks/debian/jgoodies-looks-debian.jar file:///usr/share/maven-repo/com/jgoodies/jgoodies-forms/debian/jgoodies-forms-debian.jar file:///usr/share/maven-repo/com/jgoodies/jgoodies-common/1.x/jgoodies-common-1.x.jar

Do I need to pass any params to dh maybe --with javahelper? 

On Thu, Dec 1, 2016 at 11:51 PM, Emmanuel Bourg <ebourg@apache.org> wrote:

Hi Jose,

For ${java:Depends} to be properly populated with the package
dependencies you have to ensure the jar files in your package have a
Class-Path attribute in their MANIFEST.MF file. But if you don't want to
mess with the manifests you can simply put the dependencies manually in
debian/control.

Emmanuel Bourg

--

José Gutiérrez de la Concha
ZeroC, Inc.