derby.jar,
>> derbyclient.jar
>> ,
>> >> derbynet.jar, derbytools.jar
>> >>
>> >> When I look into the properties of my project under Java Build Path I
>> can
>> >> see the derby jar-files are available. I can also see
gt; >> dependencies include these jar-files.
> >>
> >> The error log says also the project cannot be built until build path
> >> errors
> >> are resolved .
> >>
> >> I tried afterwards the same thing but now I did not use a link file b
guration manager using add extension location, the problem
>> remains.
>>
>> When I add the plugins to the Eclipse plugin directory there is no
>> problem.
>>
>> What is wrong here and what is the best approach to follow ?
>>
>>
>> regards,
>
> product configuration manager using add extension location, the problem
> remains.
>
> When I add the plugins to the Eclipse plugin directory there is no
> problem.
>
> What is wrong here and what is the best approach to follow ?
>
>
> regards,
> Danny
>
>
>
Hi,
Let me try to answer two of the three questions, even though I have no
experience with the Derby Eclipse plugin...
danga wrote:
1) Since I also have the javaDB installed (Java 1.6) why should I use the
plug-in ?
I notice that the same jar files are available ?
Well, I would assume that th
blem.
What is wrong here and what is the best approach to follow ?
regards,
Danny
--
View this message in context:
http://www.nabble.com/Derby-Eclipse-Plug-in-versus-JavaDB-or-Apache-Derby-tf4532739.html#a12935407
Sent from the Apache Derby Users mailing list archive at Nabble.com.
