Well I could built with applying the patch on the development trunk,
and didn't get problems.

Also didn't do these changes you mention.

Try checking out afresh and follow the process.

thanks,
Amit

Okundaye, Derrick wrote:

Actually the problem started when l first tried to build the derby client and 
there was a compile error in org.apache.derby.client.am.Configuration.java line 
237 - ProductGenusNames.DNC_INFO because it had not been created in 
ProductGenusNames.

I initially changed it to DBMS_INFO hence the nullpointerexception because it 
could not find the majorversion number.

When l added the following lines to 
org.apache.derby.iapi.services.info.ProductGenusName:

       /**Genus name for dnc products.*/
       public static String DNC = "dnc";
       public static String DNC_INFO = "/org/apache/derby/info/dnc.properties";

it worked superbly.

Derrick

________________________________

From: Sunitha Kambhampati [mailto:[EMAIL PROTECTED]
Sent: Sat 23/04/2005 20:52
To: Derby Development
Subject: Re: Derby Client - Problem is using the driver



Sunitha Kambhampati wrote:



Okundaye, Derrick wrote:



Hi,

I built derby version 10.0.2.1 with the derby client successfully.




I think you should build it on the trunk version..   (which is  10.1.0.0
alpha )  and use it with those classes.

Also the functional spec says this  in the packaging& versioning section
-- ." The Derby network client will assume the version of the Derby
release in which it is offered (currently thought to be 10.1). "

Could you try to build on the trunk version and see if that solves your
problem.

Thanks,
Sunitha.





This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.





Reply via email to