bmuschko/gradle-cargo-plugin

the tomcat localhost.log is missing

rlagoue opened this issue · 4 comments

Sorry I was not notified about your answer.
Here are my configurations
cargo { containerId = "${rootProject.cargoContainerId}" local { homeDir = file(cargoHome) configHomeDir = file(cargoHome) outputFile = file('build/containerOutput.log') logFile = file('build/containerOutput.log') logLevel = 'low' sharedClasspath = files(configurations.postgresJdbc.resolvedConfiguration.resolvedArtifacts*.file) ... } }

The problem is that unexpected exceptions stacktrace are not printed out in any cargo output log files. When I use the war generated by my application during the gradle build in a normal tomcat installation, I can see the stack trace in the file <TOMCAT_HOME>/logs/localhost..log

It is a little bit annoying since I have to check it in a normal tomcat installation everytime I get into troubles

Thank you

Here is a screenshot of the gradle script file
image

What kind of logging are we talking about (that is not found in the log files), System out/err or something that comes from a logging framework? What logging framework are you using?

Keep in mind that this plugin only calls off to the Cargo Ant tasks. It's likely an issue with either Cargo itself or the Ant integration of Gradle core. Can you provide a simplistic example project on GitHub that demonstrates the issue?

Hi Benjamin,

Thank you for your answer. I am speaking about the log for the virtual host within tomcat (the localhost-.log) . Usually there's not much of interest in it, but when you cannot find an error in catalina.out and something is seriously wrong, this file should be checked.

In ongoing development the coder needs sometime have to take the war file generated by gradle and put it in a standalone tomcat installation, in order to understand why the application does not start using the gradle-cargo-plugin.

Cheers

For that I'd like to refer you to the Cargo mailing list as that functionality is implemented by Cargo. Please ask the question over there. Let me know if a newer version of Cargo does implemented this functionality.

ok.. I will check this out