Apache JDO Project - [jira] Commented: (JDO-313) ERROR 08001: No suitable driver on

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > February 2006 > [jira] Commented: (JDO-313) ERROR 08001: No suitable driver on





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (JDO-313) ERROR 08001: No suitable driver on
Michael Bouschen (JIRA)

2006-02-23, 5:45 pm

[ http://issues.apache.org/jira/brows...action_12367578 ]

Michael Bouschen commented on JDO-313:
--------------------------------------

I renamed my .maven directory and did a maven tck20.build in the trunk. It works! It regenerated the plugin cache, downloaded tons of jars, including derby and then started to install the schema successfully.

Michael

> ERROR 08001: No suitable driver on connection attempt to install schema
> -----------------------------------------------------------------------
>
> Key: JDO-313
> URL: http://issues.apache.org/jira/browse/JDO-313
> Project: JDO
> Type: Bug
> Components: tck20
> Versions: JDO 2 rc1
> Reporter: Michelle Caisse
> Fix For: JDO 2 rc1


>
> I moved my old local maven repository to test that all the automatic downloads work properly. The build failed on schema installation with a "No suitable driver" message. As we formerly had the derby jars in a directory called derby in the local maven r

epository, then changed it to org.apache.derby, perhaps some dependency on the old location remains in maven.xml.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Michelle Caisse

2006-02-23, 5:45 pm

Hi Michael,

I would reply on the JIRA, but down. This is good news, but it doesn't
quite prove that the TCK20 rc1 distribution works. There is no such
thing as a maven tck20.build in the distributions. Nevertheless, I will
fiddle around with my system some more and see if I can figure out what
my/the problem is.

-- Michelle

Michael Bouschen (JIRA) wrote:

> [ http://issues.apache.org/jira/brows...action_12367578 ]
>
>Michael Bouschen commented on JDO-313:
>--------------------------------------
>
>I renamed my .maven directory and did a maven tck20.build in the trunk. It works! It regenerated the plugin cache, downloaded tons of jars, including derby and then started to install the schema successfully.
>
>Michael
>
>
>
>
>
>
epository, then changed it to org.apache.derby, perhaps some dependency on the old location remains in maven.xml.[vbcol=seagreen]
>
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com