Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of paulschein@gmail.com
 designates 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=qVe2iLDdduLdZHy8o5bUuaB6Gy8LeKsTNaHe/5BouovwMuXs2U7WkeqeYN/2aRvtFLbBEDcc1biKzLh/6JU4HHIdcaXdAPbWvHfx289JglL60/8p84LpEb4MnEIYtBB8XRD3a6lD3lzNU0DA8h1K6jDgOd90Pwx2wCazQwH9Ddc=
Message-ID: <ee3760eb0709141110q139be300r9cabcf25bc033c1c@mail.gmail.com>
Date: Fri, 14 Sep 2007 19:10:42 +0100
From: "Paulo Jesus" <paulschein@gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Derby 10.3.1.4 compiling problems
In-Reply-To: <46EAB6F8.8070801@sbcglobal.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ee3760eb0709140707p7a6bef45gc1ad18720afeb88e@mail.gmail.com>
	 <46EA9DAD.3040501@Sun.com>
	 <ee3760eb0709140810k6aa5dacdq1218dce8cd941c9e@mail.gmail.com>
	 <46EAB6F8.8070801@sbcglobal.net>

2007/9/14, Kathey Marsden <kmarsdenderby@sbcglobal.net>:
> Paulo Jesus wrote:
> > The problem seems to start after, or inside, the first run of "ant "...
> >
> >
> Derby does not have a dependency based build. I always do an ant clobber
> between builds.  If it builds cleanly after an "ant clobber" then that
> is good.
>
> The problem you reported with the scripts is likely because you are
> using  $DERBY_HOME/classes instead of jars. I don't know when/why
> network server was changed to require jars, but to run it these days I
> have to remove the old jars and build the jars, "ant buildjars" after
> ant all and of course change my CLASSPATH to point to the jar location.
> So short story...
>
> ant clobber
> ant all
> rm -rf jars/insane/*
> ant buildjars
>

Compiling this ways it works. Is like doing "ant clean" instead "ant clobber".
The second run of "ant "  or "ant all"   fails with the error i talked before.
This way I have trouble watching if there is errors on compiling,
because i can't run "ant "  again before doing a clean. This means
that i have many lines to analyze. Should be a better way to do this.

I have also errors generating javadoc of engine. It cat be related to
jars configuration. I will see this later.

Thanks


> change your classpath to point to the jars/insane location.
>
> Kathey
>
>
>