Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Date: Wed, 24 Sep 2003 16:09:32 -0400
Subject: Re: CVS Build problems.
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Brian McCallister <mccallister@forthillcompany.com>
To: "OJB Developers List" <ojb-dev@db.apache.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <3F71F8C2.2020205@web.de>
Message-Id: <02F5EC37-EECB-11D7-AB02-000A95782782@forthillcompany.com>

We might want to consider using the cglib proxy implementation all the  
time instead of the preprocessor. i haven't tested myself, but by  
reports it is faster than the 1.4 proxy anyway.

-Brian

On Wednesday, September 24, 2003, at 04:04 PM, Thomas Mahler wrote:

> Hi Charles,
>
> thanks for your patience ...
>
> Charles Anthony wrote:
>> I've just done a clean CVS update. If I do a bin\build.bat, I have  
>> two problems.
>> 1) I need to stick with JDK13; the preprocessor flags in  
>> SQLTypeHelper are
>> incorrect. I'm afraid I don't understand *how* the pre-processor is  
>> supposed
>> to work - I'm guessing that if -JDBC30, it should comment out  
>> everything
>> between a //#ifdef JDB30 and //#endif. It doesn't seem to be doing  
>> this.
>> I've just manually commented out those sections, and it compiles.  
>> Thomas (or
>> someone), could you explain how the CodeSwitcher works, and how it  
>> should be
>> used.
>
> some time ago i put it those //#ifdefs and checked that everything  
> works under JDK 1.3 and 1.2.
> Unfortunately the preprocessor is quite stupid. I only recognizes  
> these statements if they start directly in the first positio of a > line.
> In the course of some reformatting of the code the //#ifdefs got  
> indented and the preprocessor does simply ignore them...
>
> I've just fixed it in CVS and did a full JDK1.3 Junit run. everything  
> should be fine now (at least until the next code formatting...)
>
>> 2) target check-jdo-classes is not the depends of "main", and yet
>> org.apache.ojb.jdo depends upon the JDO classes, and is part of the  
>> main
>> source code. So, instead of getting a nice "go and get JDO.jar"  
>> message, I
>> get a load of compile fails.
>
> fixed in CVS now!
>
> thanks,
> Thomas
>
>> Attached is the fixed build file.
>> Cheers,
>> Charles.
>> This email and any attachments are strictly confidential and are  
>> intended
>> solely for the addressee. If you are not the intended recipient you  
>> must
>> not disclose, forward, copy or take any action in reliance on this  
>> message
>> or its attachments. If you have received this email in error please  
>> notify
>> the sender as soon as possible and delete it from your computer  
>> systems.
>> Any views or opinions presented are solely those of the author and do  
>> not
>> necessarily reflect those of HPD Software Limited or its affiliates.
>>  At present the integrity of email across the internet cannot be  
>> guaranteed
>> and messages sent via this medium are potentially at risk.  All  
>> liability
>> is excluded to the extent permitted by law for any claims arising as  
>> a re-
>> sult of the use of this medium to transmit information by or to HPD  
>> Software Limited or its affiliates.
>>    
>> ---------------------------------------------------------------------- 
>> --
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org