[
https://jira.jboss.org/browse/JBAS-8274?page=com.atlassian.jira.plugin.sy...
]
Andrew Dinn commented on JBAS-8274:
-----------------------------------
Hi Paul,
I am not exactly sure what is going on here but I think the problem is because JBossTS is
inheriting the AS project pom to define the versions of dependent code and the project pom
explicitly excludes the dependencies on log4j. This appears to be to do with the need to
be able to plug in alternative logging implementations.
Anyway, whatever the reason I have managed to work around this problem by explicitly
depending upon the missing libraries in the TS pom so this JIRA can be closed.
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