[
https://issues.apache.org/jira/browse/TAP5-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883506#comment-17883506
]
Hudson commented on TAP5-2785:
------------------------------
SUCCESS: Integrated in Jenkins build Tapestry ยป tapestry-javax-java-9-freestyle
#38 (See
[https://ci-builds.apache.org/job/Tapestry/job/tapestry-javax-java-9-freestyle/38/])
TAP5-2785: tapestry-beanvalidator also needs suffixed artifact (thiago: rev
7719677526b67589582ec2058f0582e049b812a5)
* (edit) build.gradle
> Change build so it generates separate artifacts for jakarta- and javax-based
> subprojects
> ----------------------------------------------------------------------------------------
>
> Key: TAP5-2785
> URL: https://issues.apache.org/jira/browse/TAP5-2785
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core, tapestry-http, tapestry-runner,
> tapestry-spring, tapestry-test
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Blocker
> Fix For: 5.9.0
>
>
> Given the 2 branch approach ({{master}} using {{jakarta.servlet}} and
> {{javax}} using {{javax.servlet}}) was decided, there should be separate
> artifacts for the projects using the Servlet API directly: tapestry-core,
> tapestry-http, tapestry-spring, tapestry-test and tapestry-runner.
> The {{jakarta}} ones need to be generated from the {{master}} branch and have
> the {{-jakarta}} suffix on their artifact ids/names.
> The {{javax}} ones need to be generated from the {{javax}} branch and keep
> the current artifact ids/names.
> The unaffected artifacts, such as Plastic and Tapestry-IoC, shall remain
> unchanged and generated from the {{master}} branch. The {{javax}} branch will
> only generate and publish the affected artifacts, thus avoiding duplication
> and possible mismatches between branches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
