OK, I checked out 4 new Eclipse projects/workareas last night. When I
run Ant from the terminal in cayenne-ant now, I get this:
Compile:
[javac] Compiling 4 source files to
/Users/mrg/Projects/eclipse/workspace/cayenne-ant/build/cayenne-1_5/clas
ses
[javac] javac: invalid target release: 1.5
[javac] Usage: javac <options> <source files>
[javac] where possible options include:
[javac] -g Generate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source} Generate only some debugging
info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the
compiler is doing
[javac] -deprecation Output source locations where
deprecated APIs are used
[javac] -classpath <path> Specify where to find user class
files
[javac] -sourcepath <path> Specify where to find input
source files
[javac] -bootclasspath <path> Override location of bootstrap
class files
[javac] -extdirs <dirs> Override location of installed
extensions
[javac] -d <directory> Specify where to place generated
class files
[javac] -encoding <encoding> Specify character encoding used
by source files
[javac] -source <release> Provide source compatibility
with specified release
[javac] -target <release> Generate class files for
specific VM version
[javac] -help Print a synopsis of standard
options
BUILD FAILED
/Users/mrg/Projects/eclipse/workspace/cayenne-ant/build.xml:108: The
following error occurred while executing this line:
/Users/mrg/Projects/eclipse/workspace/cayenne-ant/ant/cayenne-java.xml:5
3: The following error occurred while executing this line:
/Users/mrg/Projects/eclipse/workspace/cayenne-ant/ant/import/macros.xml:
67: Compile failed; see the compiler error output for details.
My guess is it is using the 1.4 compiler instead of the 1.5 compiler?
Any suggestions?
Thanks,
/dev/mrg
-----Original Message-----
From: Andrus Adamchik [mailto:andru..bjectstyle.org]
Sent: Wednesday, November 30, 2005 9:32 AM
To: cayenne-deve..bjectstyle.org
Subject: Re: Eclipse Setup
Well, 1.4/1.5 split was one of the main reasons I had to split the
source into 4 Eclipse projects, meaning you can no longer treat
Cayenne source tree as a single Eclipse project - this won't work.
You have two options - either (1) checkout "cayenne" module from CVS
as a whole using command line and then import 4 projects from the
local folder to Eclipse or (2) checkout each of the 4 CVS modules
individually via Eclipse.
Andrus
On Nov 30, 2005, at 5:24 PM, Gentry, Michael ((Contractor)) wrote:
> Well, I meant workarea in the CVS sense, but I checked the workarea
> out
> originally using Eclipse into an Eclipse project (so they were kind of
> one and the same at that point).
>
> I guess I'll go back tonight and try again. It seemed to me the
> 1.4/1.5
> thing was really throwing Eclipse for a loop in the same project (I
> didn't see a way to specify which compiler to use on a per-source
> directory level).
>
> Thanks!
>
> /dev/mrg
>
>
> -----Original Message-----
> From: Andrus Adamchik [mailto:andru..bjectstyle.org]
> Sent: Wednesday, November 30, 2005 9:21 AM
> To: cayenne-deve..bjectstyle.org
> Subject: Re: Eclipse Setup
>
>
> When you say "workarea", I assume you meant a "project" in Eclipse
> terms (as there is also a concept of Eclipse "workspace" which is a
> combination of projects).
>
> Yeah, I guess the best thing to do is to delete an old "cayenne"
> project from Eclipse (right-click on the project and select "Delete"
> menu item), and then check out four new projects.
>
> Andrus
>
>
> On Nov 30, 2005, at 5:00 PM, Gentry, Michael ((Contractor)) wrote:
>
>> OK, stupid question ...
>>
>> I updated my 1.2 workarea last night (through Eclipse) and now
>> everything is broken. My assumption at this point is I need to
>> release
>> the old workarea and then check out four new workareas. Does this
>> sound
>> correct?
>>
>> Thanks!
>>
>> /dev/mrg
>>
>>
>> -----Original Message-----
>> From: Andrus Adamchik [mailto:andru..bjectstyle.org]
>> Sent: Sunday, November 06, 2005 4:27 AM
>> To: cayenne-deve..bjectstyle.org
>> Subject: Eclipse Setup
>>
>>
>> I think I finally figured out safe (though a little kludgy) Eclipse
>> setup:
>>
>> http://objectstyle.org/confluence/display/CAY/Eclipse
>>
>> In short - use JVM 1.4 as default for the workspace; define
>> JRE_LIB_15 variable to point to JDK 1.5 lib. Also since we now have
>> per-project settings in CVS, I checked in code templates from the
>> "contrib" folder to each project.
>>
>> Andrus
>>
>>
>> On Nov 5, 2005, at 4:11 PM, Andrus Adamchik wrote:
>>
>>> This sounded too simple, and this is because I was wrong. Building
>>> with JDK 1.5 and setting compiler level to 1.4 correctly reports a
>>> problem with this code:
>>>
>>> List<String> list = new ArrayList<String>();
>>>
>>> but not this code:
>>>
>>> StringBuilder b = new StringBuilder();
>>>
>>> So I had to introduce "test-1_4" build target to the main build
>>> file. Its main purpose is to allow nightly build script to do an
>>> extra regression pass using JDK 1.4, detecting bad code, before
>>> creating a final build with JDK 1.5. But of course this target can
>>> be used in development as well.
>>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Thu Dec 01 2005 - 10:04:13 EST