Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of davek1802@gmail.com
 designates 209.85.217.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALy+7Uk5usRFLhxLhWyCDAOMpGvWSUBVVOg72XNh1ovbc640OA@mail.gmail.com>
References: 
 <CAM0K-0CzKNaJ89zXuHAiEF1a3QYtybyXUjg0HPQrNVRWz-a9jQ@mail.gmail.com>
	<CALy+7Uk5usRFLhxLhWyCDAOMpGvWSUBVVOg72XNh1ovbc640OA@mail.gmail.com>
Date: Sat, 8 Mar 2014 11:34:00 -0800
Message-ID: 
 <CAM0K-0CbT2Bt_NXu5RjaL2cyWC=sR1qjeRghBGJJMvd+HaCKYg@mail.gmail.com>
Subject: Re: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is
 invalid
From: Dave Kennedy <davek1802@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a1133e308cd16ee04f41d73db

--001a1133e308cd16ee04f41d73db
Content-Type: text/plain; charset=ISO-8859-1

debug logging enabled
I updated the ojdbc6-11.2.0.1.pom file (see below) and the 'invalid'
message did not appear.

Now there is an error running JUnit tests: No suitable driver found for
oracle:thin:@dataserver.com:1521:dbname

I can PING the database in GlassFish Domain Admin Console and view the
Tables and data in Netbeans | Services | Databases

Error Log****************************************
. . .
[EL Info]: 2014-03-08
11:07:43.435--ServerSession(18008857)--Thread(Thread[main,5,main])--EclipseLink,
version: Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5
[EL Config]: connection: 2014-03-08
11:07:43.441--ServerSession(18008857)--Connection(32106576)--Thread(Thread[main,5,main])--connecting(DatabaseLogin(
    platform=>OraclePlatform
    user name=> ""
    connector=>JNDIConnector datasource name=>null
))
[EL Severe]: 2014-03-08
11:07:43.446--ServerSession(18008857)--Thread(Thread[main,5,main])--Exception
[EclipseLink-4002] (Eclipse Persistence Services -
2.5.1.v20130918-f2b9fc5):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: No suitable driver found for
oracle:thin:@dataserver.com:1521:dbname
Error Code: 0
[EL Severe]: ejb: 2014-03-08
11:07:43.448--ServerSession(18008857)--Thread(Thread[main,5,main])--Exception
[EclipseLink-4002] (Eclipse Persistence Services -
2.5.1.v20130918-f2b9fc5):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: No suitable driver found for
oracle:thin:@dataserver.com:1521:dbname
Error Code: 0
Mar 08, 2014 11:07:43 AM
org.springframework.test.context.TestContextManager beforeTestMethod
WARNING: Caught exception while allowing TestExecutionListener
[org.springframework.test.context.transaction.TransactionalTestExecutionListener@1f86671]
to process 'before' execution of test method [public void
dao.CustomerDaoTest.testFindAll() throws java.lang.Exception] for test
instance [dao.CustomerDaoTest@10dbe25]
org.springframework.transaction.CannotCreateTransactionException: Could not
open JPA EntityManager for transaction; nested exception is
javax.persistence.PersistenceException: Exception [EclipseLink-4002]
(Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: No suitable driver found for
oracle:thin:@dataserver.com:1521:dbname
Error Code: 0
    at
org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:428)
    at
org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:372)
    at
org.springframework.test.context.transaction.TransactionalTestExecutionListener$TransactionContext.startTransaction(TransactionalTestExecutionListener.java:583)
    at
org.springframework.test.context.transaction.TransactionalTestExecutionListener.startNewTransaction(TransactionalTestExecutionListener.java:276)
    at
org.springframework.test.context.transaction.TransactionalTestExecutionListener.beforeTestMethod(TransactionalTestExecutionListener.java:171)
    at
org.springframework.test.context.TestContextManager.beforeTestMethod(TestContextManager.java:348)
    at
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:73)
    at
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
    at
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
    at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
    at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
    at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
    at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
    at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
    at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
    at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
    at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
    at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159)
    at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87)
    at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
    at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
Caused by: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services -
2.5.1.v20130918-f2b9fc5):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: No suitable driver found for
oracle:thin:@dataserver.com:1521:dbname
Error Code: 0

.m2\repository\com\oracle\ojdbc6\11.2.0.1\ojdbc6-11.2.0.1.pom************************
<?xml version="1.0" encoding="UTF-8"?>

<project
    xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">

    <modelVersion>4.0.0</modelVersion>
    <groupId>com.oracle</groupId>
    <artifactId>ojdbc6</artifactId>
    <version>11.2.0.1.0</version>

    <name>Oracle JDBC Driver</name>
    <description>Oracle JDBC driver classes for use with
JDK1.7</description>
    <url>
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
</url>

    <licenses>
        <license>
            <name>Oracle Technology Network Development and Distribution
License Terms</name>
            <url>
http://www.oracle.com/technology/software/htdocs/distlic.html</url>
        </license>
    </licenses>

    <organization>
        <name>Oracle Corporation</name>
        <url>http://www.oracle.com</url>
    </organization>

</project>


On Thu, Mar 6, 2014 at 6:40 PM, Wayne Fay <waynefay@gmail.com> wrote:

> > "The POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid, transitive
> > dependencies (if any) will not be available, enable debug logging for
> more
> > details"
>
> Did you enable debug logging with -X to see more details? What does it say?
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001a1133e308cd16ee04f41d73db--