You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2024/08/18 13:54:00 UTC

[jira] [Created] (TAP5-2785) Change build so it generates separate artifacts for jakarta- and javax-based subprojects

Thiago Henrique De Paula Figueiredo created TAP5-2785:
---------------------------------------------------------

             Summary: 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


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)