[ 
https://issues.apache.org/jira/browse/GORA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696564#comment-13696564
 ] 

Hudson commented on GORA-125:
-----------------------------

Integrated in goraOracle #6 (See [https://builds.apache.org/job/goraOracle/6/])
    GORA-125 Clean up logging libraries (Revision 
8faaf51de5a59c0ef054b127f726f1102bb14491)
GORA-125 Clean up logging libraries v2 (Revision 
16accd4425801e350fdfa30876c1f64cc2888756)
reverse commit to r1373630 as GORA-125 breaks trunk (Revision 
d39962e57bd4644de8b1b04625c8dc0c68c5d8aa)

     Result = FAILURE
lewismc : 
Files : 
* gora-tutorial/pom.xml
* gora-cassandra/pom.xml
* pom.xml
* gora-core/pom.xml
* gora-hbase/pom.xml
* CHANGES.txt
* gora-sql/pom.xml

lewismc : 
Files : 
* gora-tutorial/pom.xml
* gora-sql/pom.xml
* gora-hbase/pom.xml
* gora-accumulo/pom.xml
* gora-core/pom.xml
* pom.xml
* gora-cassandra/pom.xml

lewismc : 
Files : 
* CHANGES.txt
* gora-core/pom.xml
* gora-cassandra/pom.xml
* gora-accumulo/pom.xml
* gora-tutorial/pom.xml
* gora-sql/pom.xml
* gora-hbase/pom.xml
* pom.xml

                
> Clean up logging libraries
> --------------------------
>
>                 Key: GORA-125
>                 URL: https://issues.apache.org/jira/browse/GORA-125
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: build process
>    Affects Versions: 0.2
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: GORA-125.patch
>
>
> Currently we have an issue GORA-77 open regarding adopting log4j over commons 
> logging. However we also maintain numerous logging dependencies in parent 
> pom.xml, namely 
> - slf4j-api
> - slf4j-simple
> - slf4j-jdk14
> It also appears that we have a property for commons-logging version 1.1.1 but 
> no dependency within the parent pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to