Re: [Springframework-developer] Preparing for 1.0.2

[Colin S. <col...@ex...>]

The latest versions of Eclipse seem to essentially try to walk the 
entire dependency tree of the code in your project, presumably so you 
get better code comprehension when you look at hierarchies and the like.

I have added the JCA 1.5 api jar to make it happy.

By the way, and Eclipse users not using 3.0 M9 should give it a try. 
I've been using the 3.0 stream since about M3, but the last month or so 
they've really done a lot of tuning and little tweaks all over the place 
in terms of usability and look and feel.

Colin


Dmitriy Kopylenko wrote:

> There is a resource adapter implementation of SessionFactory in 
> Hibernate namly net.sf.hibernate.jca.JCASessionFactoryImpl.
>
>
> Thomas Risberg wrote:
>
>> It is orm.hibernate.SessionFactoryUtils - Eclipse claims that it is 
>> indirectly referenced from required .class files.
>>
>> Thomas
>>
>>
>> jürgen höller [werk3AT] wrote:
>>
>>> Doesn't j2ee.jar include the entire J2EE RI, rather than just the 
>>> J2EE APIs? In any case, I prefer the individual jars, as they allow 
>>> to pick individual API versions rather than a particular J2EE 
>>> collective. They also allow application developers to pick just the 
>>> API jars that they actually need to compile against.
>>>
>>> So if we need JCA for some odd reason, I vote for adding the 
>>> individual jca.jar to our libs. However, I don' t know of any JCA 
>>> dependency in our code... Everything compiled nicely on my machine - 
>>> without JCA.
>>>
>>> Juergen
>>>
>>>
>>> ________________________________
>>>
>>> Von: spr...@li... im 
>>> Auftrag von Thomas Risberg
>>> Gesendet: Sa 22.05.2004 22:26
>>> An: spr...@li...
>>> Betreff: Re: [Springframework-developer] Preparing for 1.0.2
>>>
>>>
>>>
>>> I get an error in Eclipse - can't find javax.resource.Referencable.
>>> That's part of JCA I think and it does not seem to be in any of our 
>>> j2ee
>>> libs. Why don't we replace servlet.jar, ejb.jar, jdbc2_0-stdext.jar,
>>> jms.jar and jta.jar with the full j2ee.jar. That way we have all the
>>> dependencies resolved. What version? I tried 1.3 and with it everything
>>> compiles. The new 1.4 seems to have some new methods in some of the
>>> interfaces and some of our MockObject implementations did not compile.
>>>
>>> Thomas
>>>
>>> jürgen höller [werk3AT] wrote:
>>>
>>>  
>>>
>>>> Hi everybody,
>>>>
>>>> I've just finished my final preparations for our upcoming Spring 
>>>> release 1.0.2, scheduled for Sunday night. See the changelog for 
>>>> details; most issues have been discussed on the mailing lists or in 
>>>> JIRA. All remaining issues in JIRA have been addressed but do not 
>>>> incur Spring changes; I plan to close most of them at the time of 
>>>> the 1.0.2 release, resolved as "Won't fix".
>>>>
>>>> I've also updated our dependencies: FreeMarker 2.3 RC4, Hibernate 
>>>> 2.1.3, iBATIS SQL Maps 2.0 RC4, Velocity Tools 1.1 final, Commons 
>>>> Attributes May 9th snapshot. (Will Commons Attributes ever get out 
>>>> of the Jakarta sandbox?? At least some sort of official beta 
>>>> release would be nice.) BTW, MockObjects is no longer in our 
>>>> libraries, neither in CVS nor in the release distribution, as we 
>>>> don't use it anymore.
>>>>
>>>> I plan to create the actual release Sunday night. So for all you 
>>>> weekend workhorses out there, there's still a chance to test and 
>>>> review the current CVS head :-) Please no further enhancements, 
>>>> though: As the changelog shows, we've already gathered a lot of 
>>>> minor bugfixes and enhancements, so we should get out 1.0.2 ASAP. 
>>>> Further enhancements should go into 1.0.3, scheduled for late June.
>>>>
>>>> Juergen
>>>