Are the "No repository found" messages a consequence of this change?
I am asking because in looking though a recent maven build log,
I don't see both the log4j messages and the "No repository found"
messages together for the same tests.
I think both of these are pretty irritating. If fixing one causes
the other, then I don't think this is an improvement. If we can
fix both, that would be great. Does anyone know how we could
remove the "No repository found" messages as well?
Simon
Luciano Resende wrote:
Today, when we run some samples or test cases, we get an annoying log4j
warnings
log4j:WARN No appenders could be found for logger (
org.apache.axiom.om.util.StAXUtils).
log4j:WARN Please initialize the log4j system properly.
I have found a way to fix that, basically by adding a project called
log4j-props inside modules, that has a log4j.properties file only, to be
packaged in a jar file, then make the projects that are seeing the annoying
log4j warning messages to include this dependency as <scope>test</scope>
<dependency>
<groupId>org.apache.tuscany.sca</groupId>
<artifactId>tuscany-log4j-props</artifactId>
<version>1.0-incubating-SNAPSHOT</version>
<scope>test</scope>
</dependency>
After the changes, you would see something like :
URLBasedAxisConfigurator.getAxisConfiguration (68) : No repository found ,
module will be loaded from classpath
URLBasedAxisConfigurator.getAxisConfiguration (68) : No repository found ,
module will be loaded from classpath
If people are OK with this, please let me know and I can commit this
changes, and we could start adding the dependencies on demand.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
