ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Midon (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ODE-397) log4j configuration loaded from rampart-core.jar
Date Tue, 23 Dec 2008 00:41:44 GMT

     [ https://issues.apache.org/jira/browse/ODE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alexis Midon resolved ODE-397.

       Resolution: Fixed
    Fix Version/s:     (was: 2.0)

I duplicated the current log4j.properties file into axis2-war/src/test/resources/test-log4j.properties
and set buildr so that testng will use this new file.

This issue does not have to be reported into ODE trunk.

> log4j configuration loaded from rampart-core.jar
> ------------------------------------------------
>                 Key: ODE-397
>                 URL: https://issues.apache.org/jira/browse/ODE-397
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3
> rampart-core is shipped with its log4j.properties file. When executing buildr, this file
is picked by default. 
> we need the ODE log4j properties to be used.
> log4j: Using URL [jar:file:/home/alexis/.m2/repository/org/apache/rampart/rampart-core/1.3/rampart-core-1.3.jar!/log4j.properties]
for automatic log4j configuration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message