Reminder about your invitation from A, Jorge Garcia

LinkedIn This is a reminder that on June 28, A, Jorge Garcia sent you an invitation to become part of his or her professional network at LinkedIn. Follow this link to accept A, Jorge Garcia's invitation.

Bug#575411: [PATCH] fop shell wrapper: add LOGGING variable to configure proper logging

Tags: patch By default, FOP uses log4j for logging, if it is available. This behavior can be overridden, however, by setting the org.apache.commons.logging.Log system property. Since in Debian the fop package depends on libcommons-logging-java but not on liblog4j1.2-java, assume that the

Bug#575411: fop: log4j not initialized correctly

Hello, Shouldn't this be fixed in commons-logging ? Removing the classpath entry from MANIFEST-MF (06_classpath_manifest.patch in commons-logging) should fix the problem in applications. Individual applications might want to add log4j in their classpath to make their log4j.properties settings

Processed: your mail

Processing commands for cont...@bugs.debian.org: tags 575411 patch Bug #575411 [fop] fop: log4j not initialized correctly Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 575411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575411 Debian

Bug#586288: fop: log4j not initialized correctly

Hello, Shouldn't this be fixed in commons-logging ? Removing the classpath entry from MANIFEST-MF (06_classpath_manifest.patch in commons-logging) should fix the problem in applications. Individual applications might want to add log4j in their classpath to make their log4j.properties settings

Bug#575411: fop: log4j not initialized correctly

On 2011-07-11 15:42, Gabriel Corona wrote: Hello, Shouldn't this be fixed in commons-logging ? Removing the classpath entry from MANIFEST-MF (06_classpath_manifest.patch in commons-logging) should fix the problem in applications. Individual applications might want to add log4j in their

Bug#613808: fop: crashes with java.lang.UnsupportedClassVersionError: Bad version number in .class file

Hello, Can you try removing the java5 package ? Or check that Java6 is the default alternative ? (ll /etc/alternatives/java or using update-alternatives). -- Gabriel __ This is the maintainer address of Debian's Java team

metainf-services 1.2-1 MIGRATED to testing

FYI: The status of the metainf-services source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

Processed: Re: Bug#630720: sat4j: Please update to 2.3.0

Processing commands for cont...@bugs.debian.org: severity 631382 serious Bug #631382 [eclipse] [eclipse] New upstream version: 3.7 Indigo Severity set to 'serious' from 'wishlist' thanks Stopping processing here. Please contact me if you need assistance. -- 631382:

Processed: severity of 632999 is serious, severity of 631382 is wishlist

Processing commands for cont...@bugs.debian.org: severity 632999 serious Bug #632999 [eclipse-platform] eclipse-platform: sat4j dependency unsatisfiable in sid Severity set to 'serious' from 'normal' severity 631382 wishlist Bug #631382 [eclipse] [eclipse] New upstream version: 3.7 Indigo

Bug#460398: After upgrading libapache2-mod-jk from 1.2.25-2 to 1.2.26-1 apache stoped forwarding requests to tomcat.

Hi, Le samedi 12 janvier 2008 12:41:02, go...@oles.biz a écrit : Package: libapache2-mod-jk Version: 1:1.2.25-2 Severity: normal Apache http server do not forward requests to tomcat and failed with error The requested URL // was not found on this server. It's very strange behavior for

Bug#561693:

I am having a business proposal to share with you. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.