[jbosscache-dev] jboss-javaee.jar shipped with JBC

[Manik Surtani]

So if JBoss AS can't ship jta-1.1.jar because of license  
incompatibilities, then neither could JBC.

Interestingly, Hibernate Core, also LGPL, ships with jta-1.1.jar.


On 15 May 2008, at 16:58, Scott Stark wrote:

> Its just licensing differences and source availability (at least  
> historically). Ours is lgpl, sun's should be dual cddl/proprietary,  
> but that would have to be validated.
>
> Dimitris Andreadis wrote:
>> Regarding the javaee apis, I believe there is a licensing issue,  
>> whether we ship the Sun provided libraries or ours (the content  
>> should be the same).
>>
>> Scott?
>>
>> Brian Stansberry wrote:
>>> No, not sure what that one is; looks like something official from  
>>> Sun given its pom [1]. Seems the one I'm talking about is only a  
>>> CR1: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-transaction-api/1.0.1.CR1/jboss-transaction-api-1.0.1.CR1.jar
>>>
>>> Dimitris -- do you see any advantage in JBC integrating the  
>>> org.jboss.javaee/jboss-transaction-api.jar vs this javax/ 
>>> transaction/jta-1.1.jar? AFAICT, seems like both just contain JTA  
>>> 1.1 version of the javax.transaction packages.  (Why do we produce  
>>> our own if Sun already produces one?) The AS is going to integrate  
>>> the full org.jboss.javaee/jboss-javaee.jar so either way there's  
>>> going to be a trivial maven dependency mismatch so we'll just  
>>> exclude the JBC dependency in the AS pom.
>>>
>>> [1] http://repository.jboss.org/maven2/javax/transaction/jta/1.1/jta-1.1.pom
>>>
>>> Manik Surtani wrote:
>>>> I'm guessing that's jta-1.1.jar?
>>>>
>>>> On 15 May 2008, at 15:27, Brian Stansberry wrote:
>>>>
>>>>> The jboss-javaee project has recently been refactored so that  
>>>>> jar is now an assembly of a set of jars for each of the specs  
>>>>> that comprise JEE; there should be a jta-only component jar as  
>>>>> well.  I'll find it for you.
>>>>>
>>>>> Manik Surtani wrote:
>>>>>> Guys,
>>>>>> The only reason we ship jboss-javaee.jar with JBC is for the  
>>>>>> JTA interfaces.  jboss-javaee.jar, however, brings along with  
>>>>>> it whole bunch of excess baggage, which (1) makes the distro  
>>>>>> unnecessarily large, and (2) causes problems in some  
>>>>>> environments [1].
>>>>>> Can anyone see anything wrong with dropping jboss-javaee.jar  
>>>>>> and replacing it with jta-1.1.jar [2]?  I'm guessing we'd need  
>>>>>> to make sure this is marked as optional in Maven, so it can be  
>>>>>> excluded from projects that get deployed in an EE environment  
>>>>>> (or any other environment where JTA is provided).
>>>>>> Thoughts?
>>>>>> Manik
>>>>>> [1] http://jira.jboss.org/jira/browse/JBCACHE-1347
>>>>>> [2] http://repository.jboss.org/maven2/javax/transaction/jta/1.1/
>>>>>> -- 
>>>>>> Manik Surtani
>>>>>> Lead, JBoss Cache
>>>>>> manik at jboss.org
>>>>>> _______________________________________________
>>>>>> jbosscache-dev mailing list
>>>>>> jbosscache-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>>>>>
>>>>> -- 
>>>>> Brian Stansberry
>>>>> Lead, AS Clustering
>>>>> JBoss, a division of Red Hat
>>>>> brian.stansberry at redhat.com
>>>>
>>>> -- 
>>>> Manik Surtani
>>>> Lead, JBoss Cache
>>>> manik at jboss.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>

--
Manik Surtani
Lead, JBoss Cache
manik at jboss.org