Re: Problems building cayenne-src-1.1M3.tar.gz from source and unexpected error using prebuilt jar

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Tue Mar 02 2004 - 17:26:03 EST

  • Next message: Mike Kienenberger: "[SOLUTION?] Problems building cayenne-src-1.1M3.tar.gz from source unexpected error using prebuilt jar"

    On Mar 2, 2004, at 4:52 PM, Mike Kienenberger wrote:
    > I've been using Commons Collections 2.1 since that's what's required
    > for
    > Struts 1.1, but it looks like you've upgraded cayenne to 3.0 with this
    > release (at least, I haven't noticed the problem yet in my
    > couple-weeks-old
    > cvs pull of cayenne).

    Yes, I've upgraded commons-collections to 3.0. My bad, I should've
    posted an announcement. The reason I did that was that there were some
    bugs with chained iterators (something I am planning to use) in 2.1. If
    this creates unbearable problems with Struts (does it? I think 3.0 is
    fully backwards compatible, though old classes are deprecated), we can
    roll back.

    > The build problem is this. I decided to add in the fix to use
    > getTime/getDate/getTimestamp in DateUtilType so Oracle Timestamps would
    > work.
    > =============================================
    > E:\java\cayenne-1.1M3\src> %ANT_HOME%\bin\ant
    > [...]
    > [javac]
    > E:\java\cayenne
    > -1.1M3\src\cayenne\org\objectstyle\cayenne\dataview\DataView.java:64:
    > package org.jdom does not exist
    > [...]
    > [javac]
    > E:\java\cayenne
    > -1.1M3\src\cayenne\org\objectstyle\cayenne\event\JavaGroupsBridge.java:
    > 61:
    > package org.javagroups does not exist
    > [...]
    > =============================================

    True, jdom that is only used by dataview package is not bundled with
    cayenne.jar. The thing is, "cayenne.jar" is growing out of proportion
    now. The original nice idea of keeping everything in one jar has
    outgrown itself, so we have to make concessions... With Java Groups it
    is a different story. It is distributed under LGPL, so there is a
    sensitive license compatibility issues with that. It is not bundled
    intentionally.

    However this raises an issue of whether we should even continue
    maintaining the build.xml script as a part of the distribution. Having
    two independent build systems (one for developers and one for users) is
    becoming a maintenance nightmare. I have a very strong opinion that we
    should stop shipping the build script and tell users who build Cayenne
    on their own to use anonymous CVS (or CVS snapshots from the website).
    CVS includes all the jars and is guaranteed to build without glitches.
    Besides it should be very easy to find a particular date or a release
    label.

    I am sure there will be complaints, but if you think of it everybody
    wins from the consistency we get from this.

    Andrus



    This archive was generated by hypermail 2.0.0 : Tue Mar 02 2004 - 17:26:08 EST