But you can still use the 1.4 jre and the 1.5 jre in the same
workspace on different projects.
You have to explicitly mention the JRE to use in the classpath
(instead of it using the default). Problem is mine (on linux) might
be called 'jre1.4' mine on OSX is called 'Java 1.4.2' and on windows
its called 'my favorite jre'. So each computer would have to modify
the .classpath file, thus causing problems during check in.
This is another argument for not having the eclipse files in the repo.
TTFN,
-bd-
On Aug 2, 2006, at 2:28 PM, Andrus Adamchik wrote:
>
>> Is this really necessary?
>
> No, if you are just browsing the code or making occasional changes.
>
> Yes, if you are actively developing.
>
> This piece of code will be happily accepted under JDK 1.5 JRE with
> JDK 1.4 compiler settings:
>
> StringBuilder b = new StringBuilder();
>
> Andrus
>
>
> On Aug 2, 2006, at 4:24 PM, Kevin Menard wrote:
>
>>> * create two workspaces - one for JDK 1.4 and one for 1.5 code.
>>> * import the following projects to 1.4 workspace:
>>>
>>> core/cayenne-jdk1.4-core/
>>> modeler/modeler
>>>
>>> * import the following projects to 1.5 workspace
>>>
>>> core/cayenne-jdk1.5-core
>>> core/cayenne-jpa
>>
>> Is this really necessary? You can configure the compiler plugin
>> to use the
>> proper JDK. I have projects with mixed JDK versions no problem.
>> I just
>> think setting up two different workspaces is more work than is really
>> necessary.
>>
>> Btw, I'm +1 on dumping the environment variable. I haven't been
>> using it
>> all for a while.
>>
>> --
>> Kevin
>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Aug 02 2006 - 17:19:42 EDT