[ 
https://issues.apache.org/jira/browse/TAP5-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071075#comment-18071075
 ] 

Hudson commented on TAP5-2809:
------------------------------

FAILURE: Integrated in Jenkins build Tapestry » 
tapestry-javax-java-17-freestyle #120 (See 
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-javax-java-17-freestyle/120/])
TAP5-2809: jacoco 0.8.14, version guards removed (benw: rev 
031a833b05aa7c0b7c2c2ad0d423d25b1c99ab77)
* (edit) build.gradle
TAP5-2809: Apache commons dependencies updated (benw: rev 
b99d81eb6b3925fc63f2509b6b4d5b9c0b682052)
* (edit) gradle/libs.versions.toml
TAP5-2809: Gradle 8.14.4 (benw: rev 70825e084fbbbd3feccf7875d73ef720639112a0)
* (edit) gradle/wrapper/gradle-wrapper.properties


> Improve/Fix Gradle Setup
> ------------------------
>
>                 Key: TAP5-2809
>                 URL: https://issues.apache.org/jira/browse/TAP5-2809
>             Project: Tapestry 5
>          Issue Type: Task
>    Affects Versions: 5.9.1
>            Reporter: Ben Weidig
>            Assignee: Ben Weidig
>            Priority: Major
>
> The current Gradle setup has multiple issues:
>  * Pre-Java 8 remnants
>  * Incomplete upgrade to JUnit 5
>  * Incorrect testng.xml
>  * Misaligned dependency version between projects
>  
> To improve the situation, I suggest:
>  * Remove all pre-Java 8 options
>  * Create Gradle conventions for
>  ** Subproject setup
>  ** JUnit 5 (+Spock)
>  ** TestNG (and move testng.xml to default locations)
>  ** JUnit 4 for legacy reasons
>  * Introducing version catalogs for shared dependencies and a consistent 
> declaration of module-specific dependencies.
>  
> In a second step, more tasks, like Javadoc-related tasks or publishing, could 
> be done with conventions or build plugins, to make them easier to use and 
> maintain.
> The overall risk is breaking the build and breaking changes for Tapestry 
> users if a dependency is no longer exposed.
> However, choosing the right configuration so as not to accidentally export 
> dependencies is more critical, and the error messages should clearly state 
> why a build is no longer working.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to