Andrus, can you comment on the impact this is going to have on cayenne
committers? Do I now need to have a 1.5 JDK installed to work on the
project?
On 11/4/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
> I am ready to go ahead with this change. I will temporarily disable
> CVS notifications to avoid email flood. Also if you were planning to
> check in new code, it is wise to it hold off until further notice.
>
> I decided to go with a split-project approach. Currently Cayenne maps
> to a single Eclipse project; once the change is done it will become
> an Eclipse workspace with multiple projects. Workspace will have a
> single set of Ant scripts.
>
> Here is the planned root folder structure:
>
> /build*.xml
> /README-eclipse.txt
>
> /cayenne-java/ /* Main project with JDK 1.4 source */
> lib/ /* Moved from current '/otherlib' */
> src/ /* Moved from current '/src' */
> .classpath
> .project
>
> /cayenne-java-1.5/ /* New Java 1.5 project */
> src/
> .classpath
> .project
>
> /cayenne-third-party-src/ /* currently under cayenne-otherlib-src */
> .project
>
> /cayenne-docs/
> doc/
> xdocs/
> .project
>
>
> Andrus
>
>
>
>
> On Nov 3, 2005, at 3:45 PM, Andrus Adamchik wrote:
>
> > Thanks Cris!
> >
> > I am planning to do this reorg ASAP - there is so much new stuff
> > that I want to post M7 build within a few days. And merging JDK1.5
> > features in the main build is a prerequisite of M7.
> >
> > Andrus
> >
> >
> > On Nov 2, 2005, at 7:36 PM, Cris Daniluk wrote:
> >
> >
> >
> >> Since nobody else wants to take this one, I'll bite... you can fairly
> >> cleanly tailor the warnings that Eclipse spits out on the
> >> project-level, so you can avoid the warning problem. I think its
> >> not a
> >> bad idea anyway... the generics warnings are totally ridiculous and
> >> non-third-party-library friendly.
> >>
> >> Then, use source/target in the ant build for the stuff that needs to
> >> be 1.4-compliant. For what its worth, I'm yet to have a problem using
> >> the 1.5 compiler to generate 1.4 source-level code.
> >>
> >> Incidentally, I've been meaning to add a bug report to add
> >> source/target to all javac ant tasks anyway. It really should be
> >> required by Ant... it bugs me that it isn't. Cayenne won't compile
> >> under 1.5 without it.
> >>
> >> Cris
> >>
> >> On 10/24/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
> >>
> >>
> >>
> >>> If you are on cayenne-cvs, you've seen lots of recent notification
> >>> emails with comments about JDK 1.5 extensions. I checked in a new
> >>> contrib/jdk-ext/cayenne-java-1.5 folder that currently has support
> >>> for Enum ExtendedType.
> >>>
> >>> "contrib/jdk-ext/cayenne-java-1.5" is essentially a standalone
> >>> Eclipse project, thus allowing me to set Eclipse compiler compliance
> >>> level to 1.4 for Cayenne and to 1.5 for the extension. That's pretty
> >>> messy though...
> >>>
> >>> I was wondering if anyone have ideas on how to improve it and still
> >>> ensure the right source and binary compliance levels? The easiest
> >>> way
> >>> is to force the whole Eclipse project to be 1.5, while perform split
> >>> compile of different folders with Ant. This would work, but will
> >>> generate literally thousands of 1.5 warnings for the 1.4 code...
> >>> Maybe we should move the root of the main Eclipse project from
> >>> "cayenne" to a subdirectory, so that multiple projects could co-
> >>> exist
> >>> in the same root directory?
> >>>
> >>> Andrus
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Fri Nov 04 2005 - 11:32:29 EST