-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gradle 3.2: resolutionStrategy question #29
Comments
Not a problem with the resolution strategy or related to Gradle, your grammar file has an error in it. Please see the logs:
|
No, the grammar has no error, the JavaCC 7.0 supports the generation of C++ code which I have extended for supporting list for the PARSER_INCLUDE option. The line 13 corresponds to the first '(' of the list of the PARSER_INCLUDE option. Typer.jj
compiles fine with
|
Sorry, but JavaCC outputs an error, that’s crystal clear from the logs, you should check that, as I am not supporting JavaCC itself :) Jonathan Martel Signature digitale: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x321163AE83A4068A
|
Sorry to insist, but this is not a request about JavaCC itself but on getting some help about the force resolutionStrategy on the buildscript ahead that does not work. The script is forcing to use the JavaCC 7.0 jar and the execution log shows that is JavaCC 6.1.2 that is used. Also, my previous message shows that JavaCC 7.0.0 compiles the grammar without error with the CLI. |
Where did you get the javacc:7.0 artifact, is it installed in maven local? Can't find it in maven central for sure... |
Can you provide a build script that I can try? Looks to me that the plugin is not using javacc 7.0 because it can't find it, which seems to be confirmed by the javacc output in the build log. |
I am a contributor of JavaCC and specialy for the C++ generation...The 7.0 is not officialy released to any maven repository (it is up to Sreeni to do that) but this version can be build from the GitHub master repo. Thus I put the javacc 7.0 artifact is in the Maven local repository with this script
and the command
here the build.gradle
|
Hi Running gradle compileJavaCC with debug produces a log where I found this snippet
gradle or the javacc plugin is looking for the 6.1.2 version in MavenLocal while it should used the 7.0.0 version. May be this could be a pointer to find out the problem? |
I will have a look over the weekend. I'll build JavaCC 7 and try to force using this version. Sorry, I am away for work right now and can't find the time to work on this issue. |
no problem..; I was thinking just to shorten the domain of research..thanks for taking care of this point. |
Can you point me on the right repo/branch for JavaCC, just to be sure I have the correct source? |
The master branch here is versionned at 7.0.0 |
Due to changes to the plugin publishing mechanism to the plugin portal, I need to reclaim the plugin with Gradle before being able to publish it to the plugin portal. The new version of the plugin is built and released and as soon as Gradle acknowledges my reclaim request, I will publish the new version to the plugin portal. This issue is now fixed. The default version used is It is as easy as declaring a dependency on javacc to customize the javacc version:
|
Hi
This is not really an issue but as there is no way to ask question about javaccPlugin on GitHub.
I am trying to use another version of JavaCC, the 7.0 to generate a C++ parser with
but that does not work. What I am missing?
The text was updated successfully, but these errors were encountered: