ERROR 08001: No suitable driver on connection attempt to install schema

• Key: JDO-313
• Type: Bug
• Status: Resolved
• Resolution: Cannot Reproduce
• Priority: Major
• Assignee: Unassigned
• Reporter: Michelle Caisse
• Component/s: tck2
• Affects Version/s: JDO 2 rc1
• Fix Version/s: JDO 2 rc1

Description

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.

Comments

[Craig Russell]

The dependency in rc1 hasn't changed. In the project.xml for both the trunk and branches/2.0-rc1:

        <dependency>
            <groupId>org.apache.derby</groupId>
            <artifactId>derby</artifactId>
            <version>10.1.1.0</version>
        </dependency>
        <dependency>
            <groupId>org.apache.derby</groupId>
            <artifactId>derbytools</artifactId>
            <version>10.1.1.0</version>
        </dependency>

It works fine for me.

Did the maven build download the derby jars?

[Michelle Caisse]

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.

[Michael Bouschen]

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

[Michelle Caisse]

Just me. When I deleted derby.jar from the maven repository and let it download again, the problem went away. Thanks for your help, Michael and Craig.