Hi all,
I've taken latest git pull just now, from xalan-java repos's master
branch and xalan-test repos's master branch.
With this, I'm able to see that, xalan-test smoketest build is
failing. I've run this XalanJ smoketest build on windows.
For this, I can see within XalanJ smoketest log, tha
Tangent: We should enable GitHub Actions builds to build the master branch
and PRs, this will avoid merging broken PRs. This failure could be my fault
since I did not run local builds before merging the recent PR. Switching
our build to Maven will make this much easier. I personally would not
bothe
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722472#comment-17722472
]
Elliotte Rusty Harold commented on XALANJ-2649:
---
No need to wait for a Mav
On Sun, May 14, 2023 at 10:37 AM Gary Gregory wrote:
>
> Tangent: We should enable GitHub Actions builds to build the master branch
> and PRs, this will avoid merging broken PRs. This failure could be my fault
> since I did not run local builds before merging the recent PR. Switching our
> buil
Hi Elliotte,
On Sun, May 14, 2023 at 4:48 PM Elliotte Rusty Harold
wrote:
> The 2.7.3 release is broken and unusable without more manual effort by each
> project to patch the pom.xml.
I've checked following sometime ago today,
I've downloaded the currently published XalanJ 2.7.3 src distribut
> Job 0: Pushing a functional release to Maven Central
> Job 1: getting everything into a single Github repo
+1. That is indeed biting the users.
> Job 287: Migrating build to Maven
Elliotte, the current "source" release for Xalan contains **a lot** of
compiled binaries in the source package.
Ac
Mukul > IMHO, I therefore disagree with what you've written above as, 'The
Mukul > 2.7.3 release is broken and unusable'.
There are severe issues with artifacts on Maven Central:
1) https://issues.apache.org/jira/browse/XALANJ-2649
Xalan 2.7.3 is missing dependencies
It means the users have to do
Hi Vladimir,
On Sun, May 14, 2023 at 5:32 PM Vladimir Sitnikov
wrote:
> the current "source" release for Xalan contains **a lot** of compiled
> binaries in the source package.
> According to
> https://www.apache.org/legal/release-policy.html#source-packages, a release
> SHOULD not contain com
Dear xalan contributors,
Our legacy code depends on xalan 2.7.2 and since the update on Maven Central
our builds fail:
Anting /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build
/users/gdadmin/2022hf/project/toolworks/JDK/jdk-17.0.1/linux/bin/java \
-Dant.home=/users/gdadmin/
Quick note, for me: Maven yes, Gradle NEVER.
Gary
On Sun, May 14, 2023, 08:02 Vladimir Sitnikov
wrote:
> > Job 0: Pushing a functional release to Maven Central
> > Job 1: getting everything into a single Github repo
>
> +1. That is indeed biting the users.
>
> > Job 287: Migrating build to Mave
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory reassigned XALANJ-2649:
---
Assignee: (was: Gary D. Gregory)
> Xalan 2.7.3 is missing dependencies (Regress
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722474#comment-17722474
]
Gary D. Gregory commented on XALANJ-2649:
-
[~mus@gmail.com]
Do NOT assign
Hello Alexander,
It sounds like your build does not set a version for xalan:xalan, in which
case your build system might be choosing for you to use whatever is the
latest version.
Gary
On Sun, May 14, 2023, 08:38 Tarnopolsky, Alexander
wrote:
> Dear xalan contributors,
>
>
>
> Our legacy code
Mukul > If I may, I'd like to refer to following document :
See https://lists.apache.org/thread/otx07h6vbjrsqd9r9sqpcpjscvjwtmfc
They use SHOULD since there are (unclear) edge cases:
https://lists.apache.org/thread/83cqlqggyxt50f3ccbzog2j27v1h2h08
However, it is not clear what makes binaries in Xa
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722478#comment-17722478
]
Vladimir Sitnikov commented on XALANJ-2649:
---
Gary, I am afraid the assignment
Gary> It sounds like your build does not set a version for xalan:xalan
Gary, the build failure ends with "Failed to collect dependencies at
xalan:xalan:jar:[2.7.2]",
so it looks like they do look for a specific 2.7.2 version.
It might be indeed a bit strange that the resolver checks
xalan/xalan/m
Sun, 14 May 2023 17:12:11 +0300, /Vladimir Sitnikov/:
Gary> It sounds like your build does not set a version for xalan:xalan
Gary, the build failure ends with "Failed to collect dependencies at
xalan:xalan:jar:[2.7.2]",
so it looks like they do look for a specific 2.7.2 version.
https://rep
https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml
Stanimir> Currently
I see that 2.7.2 is not listed there, and I think it is an issue.
Vladimir
--
Vladimir
Just a reminder: You do not need to be a committee to contribute to the Xalan
project. As I've just demonstrated, you can work on a fork rather than a
branch, then submit a pull request against that fork for the
committers/approvers to evaluate.
So if Maven build is your top priority, _you_ can
On Sun, May 14, 2023 at 11:38 AM Mukul Gandhi wrote:
>
> Hi Elliotte,
>
> On Sun, May 14, 2023 at 4:48 PM Elliotte Rusty Harold
> wrote:
>
> > The 2.7.3 release is broken and unusable without more manual effort by each
> > project to patch the pom.xml.
>
> I've checked following sometime ago tod
We should indeed make sure the Apache web page is up to date. Who has access?
I don't understand the publication process well enough myself, right now. Not
that I have the authorizations to turn that crank, as far as I know.
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Musi
I think my last two items were also automagically assigned to Gary. I don't
know by what; I certainly didn't intend to do so. Not sure where to go looking
for the offending code.
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.co
Oh, well, no big deal I guess. I don't see a way to change the default if
that's what is happening. I suppose than when one creates a ticket, one
needs to make sure the assignment makes sense.
Gary
On Sun, May 14, 2023, 14:40 Joseph Kesselman wrote:
> I think my last two items were also automag
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722610#comment-17722610
]
Joe Kesselman commented on XALANJ-2649:
---
Websearch for "default Jira assign" finds
[
https://issues.apache.org/jira/browse/XALANJ-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722644#comment-17722644
]
Vladimir Sitnikov commented on XALANJ-2649:
---
PMC members can definitely edit p
Joseph> Just a reminder:
Thank you for the reminder, however, it looks like you have responded to
the wrong thread.
The issue Alexander is facing right now does not involve Maven.
The issue involves Apache Ivy which fails to resolve Xalan 2.7.2 dependency.
External contributors are in a position
@Mukul,
Here are some more violations:
xalan-j_2_7_3/lib/brazil-2.1.jar is licensed under SPL 1.0
xalan-j_2_7_3/lib/rhino-1.7.14.jar is licensed under MPL 2.0
Both these licenses are under "binary-only inclusion condition", so the
files must be removed from a source release package:
https://www.
27 matches
Mail list logo
