You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Mukul Gandhi (Jira)" <ji...@apache.org> on 2026/02/28 14:51:00 UTC
[jira] [Updated] (XALANJ-2790) implement repos branch for migrating XSL 3 ant build to maven
[ https://issues.apache.org/jira/browse/XALANJ-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Gandhi updated XALANJ-2790:
---------------------------------
Fix Version/s: xslt3.0_alpha1
> implement repos branch for migrating XSL 3 ant build to maven
> -------------------------------------------------------------
>
> Key: XALANJ-2790
> URL: https://issues.apache.org/jira/browse/XALANJ-2790
> Project: XalanJ2
> Issue Type: New Feature
> Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects. Anybody can view the issue.)
> Components: Build, Xalan
> Affects Versions: The Latest Development Code
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Fix For: xslt3.0_alpha1
>
>
> There's a consensus within Xalan-J team to migrate from Ant build to Maven. This has already been done for Xalan-J XSLT 1.0 master branch. The same needs to be done for branch xalan-j_xslt3.0 as well.
> I think, a good way to do this is to create a new branch from the branch xalan-j_xslt3.0, and then doing Maven migration on that new XSL 3 code branch. Parallelly, any new XSL 3 changes to code may be done on branch xalan-j_xslt3.0 with an existing Ant build, allowing quicker resolutions to Xalan-J's XSL 3 implementation issues till the time Xalan-J's new XSL 3 Maven branch gets stable.
> I'm creating this jira issue, to track creating a new Xalan-J XSL 3 Maven branch and implementing Maven build on that with XSL 3 implementation code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org