This is an automated email from the ASF dual-hosted git repository.

benw pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tapestry-5.git

commit 9d50d99979c0463fe7f38cc324045ecae32a5ce8
Author: Ben Weidig <[email protected]>
AuthorDate: Sat Feb 7 13:36:16 2026 +0100

    core: CronExpressionSpec serialization test re-enabled
    
    I don't see a reason in the code why CronExpression can't be serialized,
    the test passes.
    Most likely a stale comment.
---
 tapestry-ioc/src/test/groovy/ioc/specs/CronExpressionSpec.groovy | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/tapestry-ioc/src/test/groovy/ioc/specs/CronExpressionSpec.groovy 
b/tapestry-ioc/src/test/groovy/ioc/specs/CronExpressionSpec.groovy
index 91fdd6457..3d498f8a9 100644
--- a/tapestry-ioc/src/test/groovy/ioc/specs/CronExpressionSpec.groovy
+++ b/tapestry-ioc/src/test/groovy/ioc/specs/CronExpressionSpec.groovy
@@ -52,9 +52,6 @@ class CronExpressionSpec extends Specification {
     ois.readObject()
   }
 
-  // This test is in the original TestNG test but failed there (making me 
think that the test case was probably
-  // not being run). It's clear that CronExpressions do not deserialize 
correctly by looking at the source!
-  @Ignore
   def "check that CronExpressions serialize and deserialize"() {
 
     CronExpression original = new CronExpression("19 15 10 4 Apr ? ")
@@ -122,4 +119,4 @@ class CronExpressionSpec extends Specification {
   }
 
 
-}
\ No newline at end of file
+}

Reply via email to