[jboss-jira] [JBoss JIRA] (WFLY-11165) Eliminate unessential module dependencies on the org.jboss.as.transactions module

[Ondra Chaloupka (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647816#comment-13647816 ] 

Ondra Chaloupka commented on WFLY-11165:
----------------------------------------

hi [~bstansberry], I currently investigate on splitting the transaction module dependencies. I was thinking to split the transaction dependency jar dependency (tracked at https://issues.jboss.org/browse/WFLY-9588). I just experiment with the approach and I haven't discussed it in the Narayana team yet. So maybe it will be a wrong way.
Anyway I can be of help with this issue in scope of the Galleon task (even I can assign this task to me). I have to admit I lack a bit the expertise in Galleon to cover the context so I would need some clues, possibly.

> Eliminate unessential module dependencies on the org.jboss.as.transactions module
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-11165
>                 URL: https://issues.jboss.org/browse/WFLY-11165
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Class Loading, Management, Transactions
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Major
>
> As part of our work on getting maximum benefit from Galleon, we want to eliminate unnecessary hard dependencies between Galleon packages, most of which are just provisioning wrappers around the FS content for our  JBoss Modules modules.  So that means cutting dependency links between modules.
> The org.jboss.as.transactions module necessarily has a large dependency tree, so if other modules depend on it, they then also have a large dependency tree, perhaps much larger than whatever they really need.  So I want to eliminate such dependencies whereever possible.
> There are quite a few modules that depend on org.jboss.as.transactions solely for ServiceName constants for services that provide value types not from org.jboss.as.transactions,  e.g. TransactionManager which is from the javax.transaction.api module. So the main (perhaps only) task here will be to eliminate those links.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)