[MGNLSCH-20] Exclude jta from quartz's dependencies Created: 06/Sep/11 Updated: 02/Dec/13 Resolved: 02/Dec/13 |
|
| Status: | Closed |
| Project: | Scheduler |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.x |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Federico Grilli |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Quartz's pom has a non-optional, non-scope:provided dependency on JTA. It's unclear why, since afaik this API would in most cases be provided by the container. It causes problems when deploying on jboss for example, because it conflicts with the one shipped with jboss. Before simply excluding the dependency, it would be good to clarify why this is the case, and if it indeed should not be the case, report this as a bug to the Quartz developers. |
| Comments |
| Comment by Federico Grilli [ 02/Dec/13 ] |
|
Current Quartz version (1.8.6) we use both in master (2.0.x) and in maintenance (1.5.x) branches doesn't have such dependency |