I could be wrong, but I seem to recall that you cannot use the -cp flag when using -jar. I think it tries to get the classpath from the JAR's manifest.
--adam http://gordonizer.com On Mon, Aug 27, 2012 at 10:15 AM, Oliver Zemann <[email protected]>wrote: > The problem is that its not reliable to put the logback.xml into the > jar. Is there a way to do that with command line? I tried with java > -cp . -jar dist\AntTest.jar which was also not working. The > logback.xml was located in . > > 2012/8/27 Abraham Lin <[email protected]>: > > The "lib" folder is generally not on the classpath; however, JARs within > the > > folder are. If you know that other libraries are being successfully > loaded > > from the "lib" folder, then one thing to try is to create a minimal JAR > > containing just logback.xml. The other option would be to just package > > logback.xml with the rest of your application code (which is what Maven > does > > with items under src/main/resources by default). > > > > -Abraham > > > > > > On Mon, Aug 27, 2012 at 11:07 AM, Oliver Zemann <[email protected] > > > > wrote: > >> > >> How to reproduce: > >> > >> Create a new Java Application in Netbeans with following content: > >> > >> package com.logbackanttest; > >> > >> import ch.qos.logback.classic.LoggerContext; > >> import ch.qos.logback.core.util.StatusPrinter; > >> import org.slf4j.Logger; > >> import org.slf4j.LoggerFactory; > >> > >> public class LogbackAntTest { > >> private static final Logger LOG = > >> LoggerFactory.getLogger(LogbackAntTest.class); > >> /** > >> * @param args the command line arguments > >> */ > >> public static void main(String[] args) { > >> LOG.trace("TRACING"); > >> LOG.error("ERROR"); > >> LoggerContext lc = (LoggerContext) > >> LoggerFactory.getILoggerFactory(); > >> // print logback's internal status > >> StatusPrinter.print(lc); > >> > >> } > >> } > >> > >> Now try to get it working ;) > >> > >> I really tried alot, but it makes no difference where i copy the > >> logback.xml into. I tried it with the dist/ folder, with the lib > >> folder (which must be in the classpath, otherwise the application > >> would not start at all). > >> I have absolutly no idea whats going on - i guess with maven it just > >> copies the logback.xml into the jar and uses that (i created a > >> jar-with-dependencies). > >> > >> > >> > >> 2012/8/27 Oliver Zemann <[email protected]>: > >> > I was able to easily get it working with maven when i copied the file > >> > into my resources folder, but it is not working with ant. Somehow it > >> > is not found, in that case all debugging options in the xml makes no > >> > sense as this is just not found. > >> > > >> > I tested it with StatusPrinter and printing the LoggerContext: > >> > > >> > run: > >> > 12:58:06.590 [main] ERROR com.logbackanttest.LogbackAntTest - ERROR > >> > 12:58:06,545 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > >> > Could NOT find resource [logback.groovy] > >> > 12:58:06,545 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > >> > Could NOT find resource [logback-test.xml] > >> > 12:58:06,545 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > >> > Could NOT find resource [logback.xml] > >> > 12:58:06,546 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > >> > Setting up default configuration. > >> > > >> > I am currently in the project root directory, where a logback.xml is > >> > located. Also the dist folder (created by netbeans) contains a > >> > logback.xml and inside this dist folder the folder lib is created > >> > (containing the 3 jars, logback common, classic and slf4j) where also > >> > a logback.xml is located. > >> > > >> > 2012/8/27 Oliver Zemann <[email protected]>: > >> >> The problem is that the software is running productive on customer > >> >> side, so there is no way to just deinstall the application and > >> >> reinstall it... > >> >> > >> >> * What version of logback and slf4j are you using? > >> >> logback 1.0.6 (classic and core), slf4j-api 1.6.5 > >> >> > >> >> * Which flavor (and version) of Linux are you running? > >> >> CentOS 5.8 and 6.3 > >> >> > >> >> * Does the same problem occur when you try your logback config in a > >> >> simple > >> >> HelloWorld app (outside of install4j)? > >> >> Just tried it with creating a standalone jar from maven > >> >> (jar-with-dependencies) and its working as expected but its embedded > >> >> now. will check this in a few moments. > >> >> > >> >> Regards, > >> >> Oli > >> >> > >> >> 2012/8/27 Thorbjørn Ravn Andersen <[email protected]>: > >> >>> Have you enabled automatic printing of status messages in case of > >> >>> warming or > >> >>> errors? > >> >>> > >> >>> > >> >>> > >> >>> (see > >> >>> > >> >>> > http://logback.qos.ch/manual/configuration.html#automaticStatusPrinting) > >> >>> > >> >>> > >> >>> > >> >>> It will go to your console. > >> >>> > >> >>> > >> >>> > >> >>> From: [email protected] [mailto: > [email protected]] > >> >>> On > >> >>> Behalf Of Tony Trinh > >> >>> Sent: 25. august 2012 23:57 > >> >>> To: logback users list > >> >>> Subject: Re: [logback-user] Problem with Logging in Linux > >> >>> > >> >>> > >> >>> > >> >>> On Fri, Aug 24, 2012 at 6:52 AM, Oliver Zemann > >> >>> <[email protected]> > >> >>> wrote: > >> >>> > >> >>> Hi, i have the absolut identical file for Windows which works as > >> >>> expected (logging), but not for linux: > >> >>> > >> >>> http://rifers.org/paste/show/1801 > >> >>> > >> >>> There is just no logging - i started everything as root. Even when i > >> >>> use the FileAppender with its file name property set to > "somelog.log" > >> >>> or "/root/somelog.log" it just saves nothing and i have no idea why. > >> >>> > >> >>> I used updatedb && locate to find a file called like this but there > >> >>> was nothing. Also lsof with a grep find nothing opened. So it is > >> >>> really not logging. > >> >>> > >> >>> Regards, > >> >>> Oli > >> >>> > >> >>> > >> >>> > >> >>> Your config for the RollingFileAppender is missing the <file> > element. > >> >>> The > >> >>> manual contains a good example of all the necessary elements [1]. > >> >>> logback > >> >>> should print a warning in the debug output for this. > >> >>> > >> >>> > >> >>> > >> >>> It would be helpful if you provided additional details to reproduce > >> >>> the > >> >>> problem: > >> >>> > >> >>> > >> >>> > >> >>> * What version of logback and slf4j are you using? > >> >>> > >> >>> * Which flavor (and version) of Linux are you running? > >> >>> > >> >>> * Does the same problem occur when you try your logback config in a > >> >>> simple > >> >>> HelloWorld app (outside of install4j)? > >> >>> > >> >>> > >> >>> > >> >>> FYI, your logback config works (writes to a file) for me in Android. > >> >>> > >> >>> > >> >>> > >> >>> It looks like Install4j supports a console [2], when running the > >> >>> installer > >> >>> with "-c". It might be worth seeing if logback's debug-output prints > >> >>> in that > >> >>> console. > >> >>> > >> >>> > >> >>> > >> >>> [1]: > >> >>> > http://logback.qos.ch/manual/appenders.html#logback-RollingTimeBased > >> >>> > >> >>> [2]: > http://www.ej-technologies.com/products/install4j/whatsnew4.html > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> _______________________________________________ > >> >>> Logback-user mailing list > >> >>> [email protected] > >> >>> http://mailman.qos.ch/mailman/listinfo/logback-user > >> _______________________________________________ > >> Logback-user mailing list > >> [email protected] > >> http://mailman.qos.ch/mailman/listinfo/logback-user > > > > > > > > _______________________________________________ > > Logback-user mailing list > > [email protected] > > http://mailman.qos.ch/mailman/listinfo/logback-user > _______________________________________________ > Logback-user mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
