[castor-dev] Instruct maven to use local code instead of Snapshot-Version

Discussion:

Alexander Eibner

2009-02-07 16:46:06 UTC

Hi!

What we (the guys working on the JPA Support) are trying to do:

We wrote some scenario/functional tests for writing Data in a Derby DB
(Embedded Mode).
(for which we use the sql-maven-plugin to create the tables in the DB)

So we have some dependencies like
org.codehaus.castor spring-orm 1.3-SNAPSHOT
but as far as I can tell this dep. uses other castor modules in SNAPSHOT
Versions...
but I/we need to use our local code to persist JPA-annotated Classes -
else we get an NullPointerException.

So my question is: Is it possible to tell maven to use the local code
instead of the SNAPSHOT-Versions ?

Sorry to ask this question on the castor-list - but on the maven-list
and the IRC I didn't get a reply yet.

Hope you get my point.
Thanks for your time...

Best regards
Alexander

Caused by:
java.lang.NullPointerException

at
org.exolab.castor.persist.ClassMolderHelper.resolve(ClassMolderHelper.java:75)

at
org.exolab.castor.persist.LockEngine.<init>(LockEngine.java:174)

at
org.exolab.castor.persist.PersistenceEngineFactory.createEngine(PersistenceEngineFactory.java:74)

at
org.castor.jdo.engine.AbstractConnectionFactory.initializeEngine(AbstractConnectionFactory.java:218)

at
org.castor.jdo.engine.AbstractConnectionFactory.initialize(AbstractConnectionFactory.java:154)

at
org.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:188)

at
org.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:117)

at
org.exolab.castor.jdo.JDOManager.loadConfiguration(JDOManager.java:362)

at
org.castor.spring.orm.LocalCastorFactoryBean.createJDOManager(LocalCastorFactoryBean.java:180)

at
org.castor.spring.orm.LocalCastorFactoryBean.afterPropertiesSet(LocalCastorFactoryBean.java:151)

at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1368)

at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1334)

... 70 more

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Werner Guttmann

2009-02-07 23:12:47 UTC

Permalink

Sure. But it all depends. Basically, your question is about getting code
artefacts into your local Maven repositories, where they will be picked
up when executing the integration tests.

Well, in Maven this is easy to achieve: If you amend code of Castor ,
and those changes are required by your functional tests, simply execute a

mvn install

and all the JARs part of a Maven build for Castor will be created and
deployed to your local Maven repository.

I hope things are clearer now.

Werner

Hi!
We wrote some scenario/functional tests for writing Data in a Derby DB
(Embedded Mode).
(for which we use the sql-maven-plugin to create the tables in the DB)
So we have some dependencies like
org.codehaus.castor spring-orm 1.3-SNAPSHOT
but as far as I can tell this dep. uses other castor modules in SNAPSHOT
Versions...
but I/we need to use our local code to persist JPA-annotated Classes -
else we get an NullPointerException.
So my question is: Is it possible to tell maven to use the local code
instead of the SNAPSHOT-Versions ?
Sorry to ask this question on the castor-list - but on the maven-list
and the IRC I didn't get a reply yet.
Hope you get my point.
Thanks for your time...
Best regards
Alexander
java.lang.NullPointerException
at
org.exolab.castor.persist.ClassMolderHelper.resolve(ClassMolderHelper.java:75)
at
org.exolab.castor.persist.LockEngine.<init>(LockEngine.java:174)
at
org.exolab.castor.persist.PersistenceEngineFactory.createEngine(PersistenceEngineFactory.java:74)
at
org.castor.jdo.engine.AbstractConnectionFactory.initializeEngine(AbstractConnectionFactory.java:218)
at
org.castor.jdo.engine.AbstractConnectionFactory.initialize(AbstractConnectionFactory.java:154)
at
org.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:188)
at
org.castor.jdo.engine.DatabaseRegistry.loadDatabase(DatabaseRegistry.java:117)
at
org.exolab.castor.jdo.JDOManager.loadConfiguration(JDOManager.java:362)
at
org.castor.spring.orm.LocalCastorFactoryBean.createJDOManager(LocalCastorFactoryBean.java:180)
at
org.castor.spring.orm.LocalCastorFactoryBean.afterPropertiesSet(LocalCastorFactoryBean.java:151)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1368)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1334)
... 70 more
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Alexander Eibner

2009-02-08 11:37:26 UTC

Permalink

Thank you!

now it's clear. We always thought mvn install is for something else...

Best regards
Alexander

Post by Werner Guttmann
Sure. But it all depends. Basically, your question is about getting code
artefacts into your local Maven repositories, where they will be picked
up when executing the integration tests.
Well, in Maven this is easy to achieve: If you amend code of Castor ,
and those changes are required by your functional tests, simply execute a

mvn install

and all the JARs part of a Maven build for Castor will be created and
deployed to your local Maven repository.
I hope things are clearer now.
Werner

---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email