Discussion:
[castor-dev] Automated tests for JPA Project
Lukas Lang
2009-07-28 16:08:30 UTC
Permalink
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
Ralf Joachim
2009-07-28 17:23:28 UTC
Permalink
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.

Regards
Ralf
Post by Lukas Lang
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
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
--
Syscon Ingenieurbüro für Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
72127 Kusterdingen
Germany

Tel. +49 7071 3690 52
Mobil: +49 173 9630135
Fax +49 7071 3690 98

Internet: www.syscon.eu
E-Mail: ***@syscon.eu

Sitz der Gesellschaft: D-72127 Kusterdingen
Registereintrag: Amtsgericht Stuttgart, HRB 382295
Geschäftsleitung: Jens Joachim, Ralf Joachim


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

http://xircles.codehaus.org/manage_email
Lukas Lang
2009-07-28 20:28:16 UTC
Permalink
Hey Ralf,
Post by Ralf Joachim
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
Post by Ralf Joachim
Regards
Ralf
Post by Lukas Lang
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
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Ralf Joachim
2009-07-28 20:41:03 UTC
Permalink
Lukas,

I'm fine with dependency on JDO source during your GSoC project. Let's
discuss how we handle this for long term at the end or after your GSoC
project.

Regards
Ralf
Post by Lukas Lang
Hey Ralf,
Post by Ralf Joachim
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.
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
Post by Ralf Joachim
Regards
Ralf
Post by Lukas Lang
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
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
--
Syscon Ingenieurbüro für Meß- und Datentechnik GmbH
Ralf Joachim
Raiffeisenstraße 11
72127 Kusterdingen
Germany

Tel. +49 7071 3690 52
Mobil: +49 173 9630135
Fax +49 7071 3690 98

Internet: www.syscon.eu
E-Mail: ***@syscon.eu

Sitz der Gesellschaft: D-72127 Kusterdingen
Registereintrag: Amtsgericht Stuttgart, HRB 382295
Geschäftsleitung: Jens Joachim, Ralf Joachim




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

http://xircles.codehaus.org/manage_email
Werner Guttmann
2009-07-28 18:17:15 UTC
Permalink
Lukas,

can I take it that you are talking about a test plan for Bamboo ?

lG.
Werner
Post by Lukas Lang
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
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Lukas Lang
2009-07-28 20:16:11 UTC
Permalink
Hey Werner,
Post by Ralf Joachim
Lukas,
can I take it that you are talking about a test plan for Bamboo ?
exactly. I just created a new plan.

Lukas
Post by Ralf Joachim
lG.
Werner
Post by Lukas Lang
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
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

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