Hey Ralf, Ralf Joachim schrieb: > Hi Lukas, > > build automation makes sense in my opinion but should depend on > SNAPSHOT/GA releases of JDO and not on source. With the dependecy on > SNAPSHOT/GA we will not see problems with error propagation. >
I can see your point. But let me explain something: Most of the JPA features are/will be added to Castor JDO, as there unfortunately is no other way to do so at the moment. I think, Castor persistence is not abstract enough to operate on an enclosed meta model. When implementing JPA functionality, changes in the Castor JDO module must be propagated to the JPA module. Waiting for a minor or patch release of the JDO module to integrate new functionality into the JPA module is not really an option (at least for my GSoC project). I fully agree, that both major and minor releases of Castor JPA should only depend on Castor JDO releases and not on snapshot versions. For development reasons I don't see any other ways to do so at the moment. Do you? Any other thoughts on that? Lukas > Regards > Ralf > > Lukas Lang schrieb: >> Hello, >> >> I was just wondering, whether we can also introduce build automation for >> the JPA project? >> >> One the one hand, this would give a nice view on the health-status of >> the module, as JPA functionality increases since a few weeks. And on the >> other hand, this would show error propagation due to transitive >> dependency to Castor JDO. >> >> What do you think? >> >> Regards, >> Lukas >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
