[
http://jira.jboss.com/jira/browse/JBMESSAGING-467?page=all ]
Ovidiu Feodorov updated JBMESSAGING-467:
----------------------------------------
Description:
Currently we've imported JBossAS in the lib area of our project to keep the project
compiling. This is hardly an acceptable solution. The proper solution involves:
1) Deciding what JBossAS depenencies we need and getting rid of artificially introduced
dependencies
2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed
in the repository.
was:
Currently we've imported JBossAS in the lib area of our project to keep the project
compiling. This is hardly an acceptable solution. The proper solution involves:
1) Deciding what JBossAS depenencies we need and getting rid of arificially dependencies
2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed
in the repository.
Sort out JBoss AS dependencies
------------------------------
Key: JBMESSAGING-467
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-467
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Alpha1
Currently we've imported JBossAS in the lib area of our project to keep the project
compiling. This is hardly an acceptable solution. The proper solution involves:
1) Deciding what JBossAS depenencies we need and getting rid of artificially introduced
dependencies
2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed
in the repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira