[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4548?page=c...
]
Steve Ebersole commented on HHH-4548:
-------------------------------------
Ideally maven itself would fix this to allow to "remap" dependencies (allow you
to say javax.transaction:jta:1.1 should really be resolved as com.acme:transation-api:99).
But, well, it does not.
Of course the downside to changing to a new set of maven coordinates here is the
fragmentation of this. There are dozens of jta.jar bundles under various licensing terms.
The effect being that excluding or declaring <dependencyManagement/> for jta
becomes problematic.
Alter poms to not use javax.* artifacts under Sun proprietary
license
---------------------------------------------------------------------
Key: HHH-4548
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4548
Project: Hibernate Core
Issue Type: Improvement
Components: build
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.3.x, 3.5
Currently we referenence both javax.transaction:jta and javax.security:jacc in the
Hibernate poms. These artifacts are distributed under a goofy, proprietary license and
are not really usable as such from maven repos.
Eventually we should use the CDDL+GPL versions created as part of GlassFish. But those
are unfortunately not yet published to any repos. In the meantime, use the corresponding
JBoss LGPL developed artifacts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira