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 <mu...@apache.org> on 2022/08/02 14:08:40 UTC
running tests on latest xalanj codebase
Hi all,
I'm happy to share that, I've been successful to run XalanJ smoke
tests on latest XalanJ codebase.
For this, I've used XalanJ codebase from branch xalan-j_2_7_1_maint
(repos xalan-java), and tests codebase from branch master (repos
xalan-test).
I've got the following, as my attempt of this tests run,
smoketest-notpass:
smoketest-pass:
[echo] [minitest] CONGRATULATIONS! The Smoketest passed!
I'm happy with these results.
It seems that, I've solved the running tests hurdle, for XalanJ.
Perhaps, we could put effort now on trying, releasing new version on
XalanJ. If yes, who should do that? Gary, Joseph, me, or anyone else?
I'm ready to volunteer, if provided permission.
Any comments are welcome.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: running tests on latest xalanj codebase
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Vladimir,
On Mon, Aug 8, 2022 at 2:56 PM Vladimir Sitnikov
<si...@gmail.com> wrote:
> Would you please rephrase? It looks like you mixed two thoughts into the same sentence.
> Did you just say "shall not be much beneficial to make a new release"?
I meant that, its beneficial to make a new XalanJ release sometime
soon. But it doesn't seem to me beneficial at this stage of XalanJ
development, to introduce CI/CD process.
> Would you please clarify when you could release it?
I'm not the only one, who could decide on this. XalanJ committers
needs to have consensus on the new XalanJ release schedule.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: running tests on latest xalanj codebase
Posted by Vladimir Sitnikov <si...@gmail.com>.
>I think that, it shall not be much beneficial to introduce CI/CD
>automation at this stage, of XalanJ development and to make a new
>release
Would you please rephrase? It looks like you mixed two thoughts into the
same sentence.
Did you just say "shall not be much beneficial to make a new release"?
Would you rather consider making a release that fixes
https://issues.apache.org/jira/browse/XALANJ-2636 ?
Would you please clarify when you could release it?
Vladimir
Re: running tests on latest xalanj codebase
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Vladimir,
my personal thoughts below, inline.
On Mon, Aug 8, 2022 at 8:56 AM Vladimir Sitnikov
<si...@gmail.com> wrote:
> Would you please configure GitHub Actions for Xalan-J, or merge https://github.com/apache/xalan-java/pull/2 ?
I think that, it shall not be much beneficial to introduce CI/CD
automation at this stage, of XalanJ development and to make a new
release. It seems to me that, there are not any critical codebase
changes (that'll change frequently during further development)
pending, for the next release of XalanJ. We can fairly easily manage
making the next XalanJ release, by doing manual steps via existing
XalanJ Ant build.
It also seems to me that, instead of merging your mentioned pull
request as it is, we can take best points from your pull request and
do them manually via existing XalanJ Ant build.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: running tests on latest xalanj codebase
Posted by Vladimir Sitnikov <si...@gmail.com>.
Great it works for you.
Would you please configure GitHub Actions for Xalan-J, or merge
https://github.com/apache/xalan-java/pull/2 ?
Vladimir
Re: running tests on latest xalanj codebase
Posted by Mukul Gandhi <mu...@apache.org>.
Hi Vladimir,
On Tue, Aug 2, 2022 at 8:00 PM Vladimir Sitnikov
<si...@gmail.com> wrote:
> Could you please clarify which modifications have you put to make it run?
> Do you execute the tests in CI?
Following are the steps on the windows platform, that I've followed to
run XalanJ smoketests,
1) create folder D:\xalanj2.7.3_jardir,
and place following jars in it : xalan.jar (that has to be tested),
xercesImpl.jar, xml-apis.jar, serializer.jar, Tidy.jar
for the xalan-test repos, do following,
2) set JAVA_HOME and ANT_HOME environment variables
3) set JARDIR environment variable, pointing to D:\xalanj2.7.3_jardir
4) build.bat distclean
5) build.bat jar
(this shall produce, testxsl.jar)
Copy the file testxsl.jar, to folder D:\xalanj2.7.3_jardir
6) build.bat smoketest
I haven't executed these tests, from CI. I've done that, using ant
build provided by XalanJ tests repos.
--
Regards,
Mukul Gandhi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: running tests on latest xalanj codebase
Posted by Gary Gregory <ga...@gmail.com>.
I do not think there is a repository for CVE details, you usually have to
follow the bouncing ball back to some source report, like a Jira ticket or
a security list thread.
Gary
On Wed, Aug 3, 2022, 03:14 Joseph Kesselman <ke...@alum.mit.edu> wrote:
> Quick q, since I've been away from this so long: Where/how does one get
> specifics on CVE reports? I can understand if access is restricted to avoid
> making vulnerabilities too easy to exploit, but presumably there is some
> way to get the analysis so one can isolate/fix/test...
>
> (Feel free to lmgtfy me if I'm missing the obvious. It _is_ 3AM here.)
>
> /_ Joe Kesselman (he/him/his)
> -/ _) My Alexa skill for New Music/New Sounds fans:
> / https://www.amazon.com/dp/B09WJ3H657/
>
> () Plaintext Ribbon Campaign
> /\ Stamp out HTML mail!
>
> On Aug 2, 2022 10:29 AM, Vladimir Sitnikov <si...@gmail.com>
> wrote:
>
> > I'm happy to share that, I've been successful to run XalanJ smoke
> >tests on latest XalanJ codebase.
>
> Nice to hear that.
>
> >It seems that, I've solved the running tests hurdle, for XalanJ.
>
> Could you please clarify which modifications have you put to make it run?
> Do you execute the tests in CI?
>
> >releasing new version on XalanJ
>
> It is worth releasing an updated version to fix BCEL CVE.
>
> Vladimir
>
>
>
Re: running tests on latest xalanj codebase
Posted by Joseph Kesselman <ke...@alum.mit.edu>.
Quick q, since I've been away from this so long: Where/how does one get
specifics on CVE reports? I can understand if access is restricted to avoid
making vulnerabilities too easy to exploit, but presumably there is some way
to get the analysis so one can isolate/fix/test...
(Feel free to lmgtfy me if I'm missing the obvious. It _is_ 3AM here.)
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
On Aug 2, 2022 10:29 AM, Vladimir Sitnikov <si...@gmail.com>
wrote:
> > I'm happy to share that, I've been successful to run XalanJ smoke
>
> >tests on latest XalanJ codebase.
>
>
>
>
> Nice to hear that.
>
>
>
>
> >It seems that, I've solved the running tests hurdle, for XalanJ.
>
>
>
>
> Could you please clarify which modifications have you put to make it run?
>
> Do you execute the tests in CI?
>
>
>
>
> >releasing new version on XalanJ
>
>
>
>
> It is worth releasing an updated version to fix BCEL CVE.
>
>
>
>
> Vladimir
>
>
>
Re: running tests on latest xalanj codebase
Posted by Vladimir Sitnikov <si...@gmail.com>.
> I'm happy to share that, I've been successful to run XalanJ smoke
>tests on latest XalanJ codebase.
Nice to hear that.
>It seems that, I've solved the running tests hurdle, for XalanJ.
Could you please clarify which modifications have you put to make it run?
Do you execute the tests in CI?
>releasing new version on XalanJ
It is worth releasing an updated version to fix BCEL CVE.
Vladimir