Hi Gary & all,
    The fixes for the following major issue, as written by you within
an earlier mail have been done (and have been committed to, XalanJ
repos as well),

<quote>
    The important thing here is that if an environment variable like
ANT_HOME is already set, it should *not* be overwritten.
</quote>

I hope to publish XalanJ 2.7.3 RC8 very soon, and shall intimate on
XalanJ lists, for review.

On Sat, Dec 24, 2022 at 11:42 PM Gary D. Gregory <ggreg...@apache.org> wrote:
>
> Thank you for your continued efforts Mukul.
>
> I'm sorry to keep putting this RC attempts down but I keep on thinking about 
> this from a potential contributor's POV:
>
> I don't think I can endorse this RC because it cannot be tested without 
> editing the instructions, not to say anything of xalan-test/build.bat which 
> is not usable at all. I suppose we got away with not testing RCs in the past 
> in a normal way, I don't think this is acceptable anymore and we've made the 
> first step by adding the xalan-test dir to the src zip but it is not in the 
> xalan-java repo which is (1) confusing and (2) makes it too hard to write and 
> use a readme that works from a xalan-test repo AND the xalan-test folder. 
> Also, don't touch ANT_HOME. IMO there should be:
>
> - ONE repo: xalan-java. The repo xalan-test should be retired.
> - Validating an RC must be as 'simple' as: download the src zip, unzip it and 
> depend on the user's preset ANT_HOME, JAVA_HOME, and JARDIR environment 
> variables, and a README that matches.
>
> TY again for your patience and work here,
> Gary


-- 
Regards,
Mukul Gandhi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to