[jboss-jira] [JBoss JIRA] Commented: (JBAS-8274) Over-zealous deprecation of *JBoss* artifacts breaks *JBoss* projects

[Andrew Dinn (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542465#action_12542465 ] 

Andrew Dinn commented on JBAS-8274:
-----------------------------------

The log4j code is found missing under commons-httpclient code which is looking for an apache log4j LoggerFactory. It may have been an update to commons-httpclient which caused this problem since in previous runs the test code did not have to include any other libraries in order to use httpclient.

 I have managed to fix this problem by installing jars jcl-over-slf4j and slf4j-simple in my classpath. These are both available in the repo and I inherited the versions identified in the component matrix pom. Is this the correct way to locate the relevant logging code?

> Over-zealous deprecation of *JBoss* artifacts breaks *JBoss* projects
> ---------------------------------------------------------------------
>
>                 Key: JBAS-8274
>                 URL: https://jira.jboss.org/browse/JBAS-8274
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>    Affects Versions: 6.0.0.M4
>            Reporter: Andrew Dinn
>            Assignee: Paul Gier
>
> apache-log4j:log4j.jar appears to have been moved to the JBoss deprecated repository (also the versions located in maven central under groupid apache-log4j appear to have been excluded form the JBoss public repo). This has broken the JBossTS hudson test builds. Can we please have our ball back?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira