[jira] Updated: (JCR-564) Remove geronimo JTA as a runtime dependency

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-564:
------------------------------

    Attachment: jta.patch

Interesting, we actually had an existing issue for the change that was recently discussed on the mailing list [1].

The attached patch changes the scope of the geronimo-jta dependency from compile to test within jackrabbit-core. The only required code changes are about copying a few private transaction status constants. In fact, looking at the code flow, the status codes are mostly unused, and could easily be replaced with two boolean flags (prepared & rolledBack). However, in order to keep this patch strictly non-functional, I didn't include such changes.

I haven't yet looked at how this change affects downstream components like jackrabbit-jca.

[1] http://www.nabble.com/Using-the-geronimo-jta-dependency-only-in-test-scope-tf4466162.html

> Remove geronimo JTA as a runtime dependency
> -------------------------------------------
>
>                 Key: JCR-564
>                 URL: https://issues.apache.org/jira/browse/JCR-564
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: maven
>    Affects Versions: 1.0.1
>            Reporter: Michael Neale
>            Assignee: Jukka Zitting
>            Priority: Minor
>         Attachments: jta.patch
>
>
> Geronimo JTA is marked as a dependency for runtime when it should be (at most) a compile time dependency. 
> Is it possible to remedy this so when using the war or building your own, you don't get the geronimo jar stowing away?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.