Re: Generate DDL with Maven2, Spring2 and Hibernate3
Hi, We also have to duplicate the information in the hibernate.cfg.xml file in order to generate the ddl. I'd be interested to know how you manage to avoid having one? For e.g. how does the hibernate3-maven-plugin know which domain objects to generate the ddl for? Also where do you define the data source settings? thanks Sufyan On Friday 06 July 2007 13:37:15 animedj wrote: > Hello Jonas > > But if the classes that you need to load are in your classpath, it should > load it automatically and you shouldn't need a > hibernate.cfg.xmlconfiguration file. But recommended is to have one. > > Regards > > Johann Reyes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse dependency on non multi module projects
> Technically spoken, yes, but you might not have much fun releasing from it > ;-) That's a fair point. I was trying to get away from having to maintain two pom.xml files as i use the dependency management section in the parent pom for defining dependency version numbers once and adding a dummy pom.xml would mean that information would have to be kept synchronised between the two poms. thanks Sufyan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse dependency on non multi module projects
Thanks very much, that's an excellent trick and means refactoring in eclipse can work across all the projects in the workspace. I could just as easily add the infrastructure as a module to the original pom.xml, Is there a specific reason for using the dummy pom.xml? thanks Sufyan > Project interdepednencies within Eclipse are only generated for projects > that share the same multi-module call. However you can use a dummy pom to > link all the projects with an appropriate modules section. > > dummy.pom: > > > path to parent > path to infrastructure > > > mvn -f dummy.pom eclipse:eclipse > > - Jörg > > > - > 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]
Re: Eclipse dependency on non multi module projects
Hi, Does anyone know if this is possible? Or even if they could point me to an another answer on the forum then I would really appreciate it. Please help. thanks Sufyan On Wednesday 27 June 2007 11:38:06 Sufyan Arif wrote: > Hi, > > I have a project set up in the classic form > > > Parent > > child1 > child2 > child3 > > > When I run mvn eclipse:eclipse at the parent level then the dependancies to > the children project are created correctly as eclipse project dependancies. > > However I also have another project called Infrastructure which does not > sit within the Parent project. Currently my child projects have a binary > dependancy on the infrastructure jar and I would like to replace that with > dependancy on the Infrastructure eclipse project which also sits in my > eclipse workspace. > > Is there a way of doing this *without* moving Infrastructure into the > Parent project? I know in M1 you could just define a property on the > dependancy to say it was a eclipse project dependancy. Anything in M2 which > is similar. > > > Thanks, > > > Sufyan > > - > 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]
Eclipse dependency on non multi module projects
Hi, I have a project set up in the classic form Parent | child1 child2 child3 When I run mvn eclipse:eclipse at the parent level then the dependancies to the children project are created correctly as eclipse project dependancies. However I also have another project called Infrastructure which does not sit within the Parent project. Currently my child projects have a binary dependancy on the infrastructure jar and I would like to replace that with dependancy on the Infrastructure eclipse project which also sits in my eclipse workspace. Is there a way of doing this *without* moving Infrastructure into the Parent project? I know in M1 you could just define a property on the dependancy to say it was a eclipse project dependancy. Anything in M2 which is similar. Thanks, Sufyan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help, accidentally destroyed the maven app logs dir
Hi, I'm in need of some major help. We were running continuum on a machine with only 8gb and to recover some disk space one of our developers deleted the contents of /continuum-1.0.3/apps/continuum/build-output-directory. Now when we try to restart the continuum server we get a dirty big exception in the logs. 3734 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - Failed initialising database. Please check that your database JDBC driver is accessible, and the database URL and username/password are correct. Exception : Failed to start database 'D:\java\continuum-1.0.3\bin\win32\..\..\apps\continuum/database', see the next exception for details. SQL Exception: Failed to start database 'D:\java\continuum-1.0.3\bin\win32\..\..\apps\continuum/database', see the next exception for details. Recovery failed unexpected problem log record is Not first but transaction is not in transaction table : 803445. ERROR XSLAO: Recovery failed unexpected problem log record is Not first but transaction is not in transaction table : 803445. Is their any way I can recover from this? I really don't want to go through installing it from scratch. I have looked in the mailing list and can't find anything appropriate. If anyone can point me in the right direction then I would be very grateful. Thanks Sufyan PS - The dirty big exception in full 242542 [Thread-0] ERROR JPOX.RDBMS.SCHEMA - Failed initialising database. Please check that your database JDBC driver is accessible, and the database URL and username/password are correct. Exception : Failed to start database 'D:\java\continuum-1.0.3\bin\win32\..\..\apps\continuum/database', see the next exception for details. SQL Exception: Failed to start database 'D:\java\continuum-1.0.3\bin\win32\..\..\apps\continuum/database', see the next exception for details. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection30.(Unknown Source) at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.jpox.DriverManagerDataSource.getConnection(DriverManagerDataSource.j ava:82) at org.jpox.util.FailoverUtils.getConnection(FailoverUtils.java:62) at org.jpox.store.rdbms.RDBMSManager.(RDBMSManager.java:214) at org.jpox.store.rdbms.RDBMSManagerFactory.getStoreManager(RDBMSManagerFac tory.java:59) at org.jpox.AbstractPersistenceManager.(AbstractPersistenceManager.ja va:222) at org.jpox.PersistenceManagerImpl.(PersistenceManagerImpl.java:34) at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persistence ManagerFactoryImpl.java:916) at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persistence ManagerFactoryImpl.java:891) at org.apache.maven.continuum.store.JdoContinuumStore.getPersistenceManager (JdoContinuumStore.java:1295) at org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoConti nuumStore.java:598) at org.apache.maven.continuum.store.JdoContinuumStore.updateSystemConfigura tion(JdoContinuumStore.java:1045) at org.apache.maven.continuum.configuration.DefaultConfigurationService.sto re(DefaultConfigurationService.java:272) at org.apache.maven.continuum.DefaultContinuum.stopContinuum(DefaultContinu um.java:2047) at org.apache.maven.continuum.DefaultContinuum$1.run(DefaultContinuum.java: 167) Recovery failed unexpected problem log record is Not first but transaction is not in transaction table : 803445. ERROR XSLAO: Recovery failed unexpected problem log record is Not first but transaction is not in transaction table : 803445. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.log.FileLogger.redo(Unknown Source) at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source) at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source) at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source) at org.apache.d
