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

[Paul Gier (JIRA)]

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

Paul Gier commented on JBAS-8274:
---------------------------------

The groupId "apache-log4j" was deprecated because the exact same jars exist in central under the groupId "log4j".  So we should be using the upstream groupId.  There is some information about this in the wiki: http://community.jboss.org/wiki/JBossDeprecatedRepository

If commons-httpclient is missing required dependencies, we should probably file an upstream jira to get that fixed.

> 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