db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-313) ERROR 08001: No suitable driver on connection attempt to install schema
Date Thu, 23 Feb 2006 19:06:37 GMT
    [ http://issues.apache.org/jira/browse/JDO-313?page=comments#action_12367567 ] 

Michelle Caisse commented on JDO-313:

The dependency did not change recently; it changed long ago.

Maven did download the derby jars, no problem there.  When you tried it, did you clean your
old repository?  My hypothesis is that legacy stuff that we all have in our existing repositories
is allowing this to work.  But maybe it's just me... It would be good if someone else could
nuke their local repository (non-destructively by renaming ~/.maven/repository to ~/.maven/repository_save,
for example) and try this.

> 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 repository, 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:
For more information on JIRA, see:

View raw message