Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
Package: javahelper Version: 0.43 Severity: important I've tried listing my classpath JARs in both debian/manifest and in debian/rules (export CLASSPATH) Either way, the generated MANIFEST.MF is broken, because of the line wrapping issue, e.g. I have Class-Path: /usr/share/java/jar1.jar

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:47, Niels Thykier wrote: On 2013-08-08 15:15, Daniel Pocock wrote: On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:59, Niels Thykier wrote: On 2013-08-08 15:49, Daniel Pocock wrote: [...] Just to clarify: you are suggesting that I should manually break the lines in debian/manifest at 72 characters No, jh_manifest will do that for you - whether you like it or not. and then the JVM

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 16:43, Emmanuel Bourg wrote: If you just want to set the classpath I suggest using jh_classpath instead. The debian/package.classpath file contains one line per jar and you don't have to care about the length of the lines: usr/share/java/foo.jar jar1.jar jar2.jar jar3.jar

Bug#705565: more detail

2013-08-27 Thread Daniel Pocock
severity -1 grave Not usable currently Easily fixed though It needs the main class declared in the manifest, from upstream, that appears to be com.google.javascript.jscomp.CommandLineRunner I tried running the JAR from this package manually: java -classpath

Bug#705565: more detail

2013-08-30 Thread Daniel Pocock
On 30/08/13 05:11, Rogério Brito wrote: Hi there. On Aug 27 2013, Daniel Pocock wrote: Easily fixed though (...) finally, it works with this command line: java -classpath /usr/share/java/closure-compiler.jar:/usr/share/java/args4j.jar:/usr/share/java/guava.jar:/usr/share/java/json.jar

Bug#705565: fixing closure-compiler, package rename?

2013-10-11 Thread Daniel Pocock
that it includes an executable? I haven't uploaded though - please let me know if I should upload or if somebody else has work in progress From f3a53a7ea17f51da7c19ef976e2015a5f1cb03b3 Mon Sep 17 00:00:00 2001 From: Daniel Pocock dan...@pocock.com.au Date: Fri, 11 Oct 2013 11:38:47 +0200 Subject

Bug#705565: Getting closure compiler back in testing?

2013-12-30 Thread Daniel Pocock
On 30/12/13 00:48, Rogério Brito wrote: Hi there. Can we have a late Christmas present (or even an New Year's present)? The closure compiler: * has already been removed from testing [1] * has many applications and users that depend/want it * already has patches in the BTS [2] [1]:

Bug#705565: Getting closure compiler back in testing?

2013-12-30 Thread Daniel Pocock
On 30/12/13 20:35, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he is working to resolve this The rename of the binary package from libclosure-compiler-java - closure-compiler should probably be done now

Bug#705565: Getting closure compiler back in testing?

2013-12-30 Thread Daniel Pocock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/13 21:03, tony mancill wrote: On 12/30/2013 11:54 AM, Daniel Pocock wrote: On 30/12/13 20:35, Thomas Koch wrote: On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote: Tony made some commits in Git and it appears he

Bug#733996: Generate a ‘closure-compiler’ binary package for the compiler program

2014-01-04 Thread Daniel Pocock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/14 06:16, tony mancill wrote: On 01/04/2014 07:07 PM, Ben Finney wrote: The binary ‘closure-compiler’ package would install: * the ‘/usr/bin/closure-compiler’ command (perhaps a symlink, as now) * the manpage (not yet written?)

Bug#740441: suggest jmxetric, provide convenient way to enable it

2014-03-01 Thread Daniel Pocock
Package: tomcat7 Severity: wishlist It would be useful to suggest libjmxetric-java and provide a convenient way to enable it. If enabled by the user, it needs to be added to the JVM boot classpath as described here:

Bug#740441: sample /etc/default/tomcat7 entries

2014-03-01 Thread Daniel Pocock
Adding this to /etc/default/tomcat7 makes it work with the default ganglia-monitor configuration on Debian # for JMXetric # - install packages ganglia-monitor and libjmxetric-java # - cp /usr/share/doc/libjmxetric-java/jmxetric.xml \ # /etc/ganglia/jmxetric-tomcat7.xml # - edit

Bug#740441: suggest jmxetric, provide convenient way to enable it

2014-03-02 Thread Daniel Pocock
Emmanuel Bourg ebo...@apache.org wrote: jmxetric looks interesting but I don't think tomcat7 should suggest a monitoring tool, apache2 doesn't suggest nagios3 for example. The difference is that jmxetric does JMX, so it is specific to Java app servers, of which tomcat is obviously the most

Bug#740554: mangles classpath in upstream manifest

2014-03-02 Thread Daniel Pocock
Package: maven-ant-helper Version: 7.7 Severity: important In debian/build.properties (for the jmxetric package) I have manifest=src/main/resources/META-INF/MANIFEST.MF to copy the upstream manifest The manifest contains: Manifest-Version: 1.0 Premain-Class:

Bug#740554: mangles classpath in upstream manifest

2014-03-03 Thread Daniel Pocock
On 03/03/14 01:36, Emmanuel Bourg wrote: Hi Daniel, maven-ant-helper was useful to build the Maven dependencies when Maven wasn't packaged yet (or to break circular dependencies). It's a limited implementation of the Maven lifecycle using only Ant, and it can't really aim at being on par

Bug#740554: mangles classpath in upstream manifest

2014-04-23 Thread Daniel Pocock
On 05/03/14 13:57, Emmanuel Bourg wrote: Le 04/03/2014 07:48, Daniel Pocock a écrit : When I search for Debian Java mvn packaging, Google had referred me to this wiki: https://wiki.debian.org/Java/MavenRepoHelper which suggested using libplexus-io-java as an example. That is using

Bug#740554: mangles classpath in upstream manifest

2014-04-23 Thread Daniel Pocock
On 23/04/14 16:51, Emmanuel Bourg wrote: Le 23/04/2014 16:34, Daniel Pocock a écrit : I have a couple more packages I want to make this week, using maven-debian-helper + dh - could you point out any example of a package I should refer to? maven-debian-helper isn't as well integrated

Bug#758611: include all modules?

2014-08-19 Thread Daniel Pocock
Package: maven-debian-helper When running mh_make I see the prompt: This project contains modules. Include all modules? [y]/n What exactly does this mean - is it about what should be built or what should be included in the binary package? For my own package, some of the modules need to be

Bug#758051: upstream changing to Maven

2014-08-19 Thread Daniel Pocock
The upstream build system is currently hybrid Maven and Ant I'm adapting it to be just Maven and the next package upload uses maven-debian-helper exclusively, hopefully that will resolve the problem and then this bug can be closed. __ This is the maintainer address of Debian's Java team

Bug#758639: creates extra .poms file

2014-08-19 Thread Daniel Pocock
Package: maven-debian-helper When creating the source package for libphonenumber, I notice that an extra file is created, debian/libphonenumber6-dev.poms The binary package libphonenumber6-dev doesn't actually contain any Java artifacts, it is for the C/C++ headers. debian/rules was created by

Bug#797835: new upstream releases

2015-09-21 Thread Daniel Pocock
Given the nature of this package (phone number country, region and network codes are volatile) we probably need to just update to the latest upstream version but I haven't had time to get onto that while doing other releases. __ This is the maintainer address of Debian's Java team