Open albert-github opened 3 years ago
You are right... will have a look sooner or later
The problem with 7.0.10 looks like to be resolved though I now see on the release notes page (https://javacc.github.io/javacc/release-notes.html) that there should be a version 7.0.11 but nowhere a a jar file or sources to be found.
#193
, it would be nice that this was through a link to the GitHub issue / pull request (like #193 or https://github.com/javacc/javacc/issues/193
)@albert-github I just released the JavaCC 7.0.11 version embedding the #193 fix. Let 24h before MAven central be updated. By the way, you can get it from Sonatype Thank for checking it is ok for you.
Strangely enough I don't see the version at https://github.com/javacc/javacc/releases or https://github.com/javacc/javacc
Release added from automatic tag generation. The release is build by mvn release, which does not update the Github tags
Looks like a continuing story, version 7.0.12 is the latest release but e.g. in https://javacc.github.io/javacc/release-notes.html there is a reference to 7.0.11 as newest and at https://javacc.github.io/javacc/ 7.0.10 is the newest.
Fixed
We probably have to wait a little while to get everything deployed, how long will that approximately be?
No idea, this is a Github process
For doxygen there is also a process for uploading the internal development documentation (i.e. documentation based on the used files) to http://doxygen.github.io/doxygen/index.html and here we see the results immediately after the deployment process has been completed. So strange that for javaCC this is not the case.
Sorry I'm just joining the thread. Albert, can you quickly summarize what the issue is?Thanks!On Sep 12, 2022 6:57 AM, albert-github @.***> wrote: For doxygen there is also a process for uploading the internal development documentation (i.e. documentation based on the used files) to http://doxygen.github.io/doxygen/index.html and here we see the results immediately after the deployment process has been completed. So strange that for javaCC this is not the case.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
The javaCC like pages https://javacc.github.io/javacc/release-notes.html and https://javacc.github.io/javacc/ are not updated although the deployment process should have run (they still show old versions).
I gave the example regarding doxygen where the github.io pages is immediately updated after the deployment.
Sorry I'm not familiar with that. If you want to update it, let me know and I can give you permissions to fix it up.On Sep 12, 2022 7:31 AM, albert-github @.***> wrote: The javaCC like pages https://javacc.github.io/javacc/release-notes.html and https://javacc.github.io/javacc/ are not updated although the deployment process should have run (they still show old versions). I gave the example regarding doxygen where the github.io pages is immediately updated after the deployment.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
I think it is an automated process that should take of it and the changes @zosrothko made should automatically be updated when a merge is made. The deployment process looks like to have succeeded but no update visible at the github.io pages.
From my side I just noted the problems and reported them.
Gents,
contributing to JSQLParser, I heavily rely on JavaCC. Pardon me to speak frank: currently its a mess. Website states 7.0.10 as latest version, while Gradle pulls 7.0.12, while Issue response points out there may be a 8.0 version we should switch too.
Maintaining the JSQLParser documentation too, I would happily volunteer with the fixing the documentation and deployment process. We want to attract users and contributors -- or else all our effort was mood.
Please give me a go-ahead, when interested. Cheers Andreas
Hi Andrea
The javacc.org website is out of sync because the generation by GitBub of https://javacc.github.io/javacc/ does not work and I have no time to checkout why? Moreover, I remove this So the issue seems more be on GitHub side than on the JavaCC owner. I just pushed a noop change on the master branch and the https://javacc.github.io/javacc/ did not regenerate. ('it is still 7.0.10 while it should be 7.0.12)
Francis
Le 21/12/2022 à 09:32, manticore-projects a écrit :
Gents,
contributing to JSQLParser, I heavily rely on JavaCC. Pardon me to speak frank: currently its a mess. Website states 7.0.10 as latest version, while Gradle pulls 7.0.12, while Issue response points out there may be a 8.0 version we should switch too.
Maintaining the JSQLParser documentation too, I would happily volunteer with the fixing the documentation and deployment process. We want to attract users and contributors -- or else all our effort was mood.
Please give me a go-ahead, when interested. Cheers Andreas
— Reply to this email directly, view it on GitHub https://github.com/javacc/javacc/issues/198#issuecomment-1361005945, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXNDAPUJEPHT4RVZEOEHXDWOK6BJANCNFSM43VKPNEQ. You are receiving this because you were mentioned.Message ID: @.***>
Hi Andreas,Thank you for this offer! Let me know what you need in terms of permissions and I can fix it.One big issue is the maven build and release working with sonatype and Francis s is not actively working on this stuff anymore. Let me know if you can help with that.Thanks!On Dec 21, 2022 12:32 AM, manticore-projects @.***> wrote: Gents, contributing to JSQLParser, I heavily rely on JavaCC. Pardon me to speak frank: currently its a mess. Website states 7.0.10 as latest version, while Gradle pulls 7.0.12, while Issue response points out there may be a 8.0 version we should switch too. Maintaining the JSQLParser documentation too, I would happily volunteer with the fixing the documentation and deployment process. We want to attract users and contributors -- or else all our effort was mood. Please give me a go-ahead, when interested. Cheers Andreas
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the prompt feedback. I will pick it up from here, clone, fix and test and come back with PRs.
Thank you! Also related to your main project, I actually have a 100% spec complaint SQL 2016 standard grammar in oss:https://github.com/prestodb/sqlI actually extracted it from the spec pdf using some unix tools and did some vi magic :) to convert to javacc. Check it out if youa are interested.On Dec 21, 2022 7:55 AM, manticore-projects @.***> wrote: Thanks for the prompt feedback. I will pick it up from here, clone, fix and test and come back with PRs.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
have a 100% spec complaint SQL 2016 standard grammar
That's awesome! Now I only need to find any 100% SQL:2016 compliant RDBMS for it :-D On the more serious side: I definitely will have a look at it. JSQLParser is great but struggles with complex nested expressions and I am very keen to learn how you have sorted this out.
Cheers!
Any progress on updating the web site as it is still on 7.0.10.
Also it would be nice to have in the Release section on GitHub besides the code zip / tar.gz files also the compiler jar files.
On the javacc.org there are still quite a few references to version 7.0.9 though I think this should be 7.0.10.
(Unfortunately I could not reopen the issue #122)