It is a multi-module, but CoreDataSource is not the module being built.
We have an Ant script that runs the Maven builds for a bunch of
interconnected modules to test the end-to-end build process for the
project.  CoreDataSource is one of the first modules built.  Later,
another module uses that JAR that is installed in the local repository
when running its tests.  So CoreDataSource isn't even involved in the
Maven build of the second module other than by being a dependency.

/
+-pom.xml
+-CoreDataSource/
+                +-core-datasource/
+                                 +-pom.xml
+-OtherModule/
+                +-other-module/
+                                 +-pom.xml

I dug around more yesterday and came across this JIRA:

http://jira.codehaus.org/browse/MNG-3542

It may be related to my issue, so I'm having the admin update the
version of maven on the server running Hudson.  As Wayne noted in the
last email, we are running an older Maven that has known issues, so I'll
reply back when he's done if it's still an issue.  Thanks!

-Ryan

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On
Behalf Of Justin Edelson
Sent: Friday, April 09, 2010 6:37 AM
To: Maven Users List
Subject: Re: JDBC error in test when run from Linux

Can you post the properties file you're referencing as well as the
resources section of the effective pom? This looks like a resource
filtering problem to me...

And when you say that "CoreDtaSource/core-datasource" is a separate
module in "the main build," do you mean that both
CoreDataSource/core-datasource and your application are both modules in
a multi-module build? If so, does this error only happen when your
application build is done within the context of a multi-module build or
both in multi-module and single-module builds?

i.e.

if your project structure is
/
+-pom.xml
+-CoreDataSource/
+                +-core-datasource/
+                                 +-pom.xml
+-app/
     +-pom.xml

do you get the error when running Maven from / and /app/ or just /?

Justin

On 4/8/10 7:04 PM, Shelley, Ryan wrote:
> We've been building our application on Maven 2.1 for awhile just fine.
> We build it manually and with a continuous integration tool (Hudson)
> without issue.  I moved Hudson from a Windows box to a Linux box, and
> suddenly we started getting this following error running the tests:
> 
>  
> 
> 2010-04-08 15:56:51,846 [main] ERROR
> org.hibernate.util.JDBCExceptionReporter - Cannot create JDBC driver
of
> class 'com.jnetdirect.jsql.JSQLDriver' for connect URL
> 'http://maven.apache.org/CoreDataSource/core-datasource
> <http://maven.apache.org/CoreDataSource/core-datasource> ' Cannot
create
> JDBC driver of class 'com.jnetdirect.jsql.JSQLDriver' for connect URL
> 'http://maven.apache.org/CoreDataSource/core-datasource
> <http://maven.apache.org/CoreDataSource/core-datasource> '
> java.sql.SQLException: No suitable driver
> 
>  
> 
> "CoreDataSource/core-datasource" is a separate custom Maven module
> dependency in the main build.  I'm not sure where it's picking up this
> value instead of using the one we have in our properties file,
> especially being that this works fine on Windows and Mac OSX.  Any
> ideas?
> 
>  
> 
> Thanks!
> 
>  
> 
> -Ryan
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to