Activity for JavaCC Eclipse Plugin
-
Marc MAZAS modified ticket #92
1.6.0 project nature and builder not recognized
-
Eric Milles posted a comment on ticket #92
yes indeed On Fri, Dec 1, 2023 at 4:01 AM Marc MAZAS mmazas@users.sourceforge.net wrote: Hi Eric. Can I close the issue? TIA. [bugs:#92] https://sourceforge.net/p/eclipse-javacc/bugs/92/ 1.6.0 project nature and builder not recognized Status: open Group: v1.0 (example) Created: Tue Jul 18, 2023 02:25 PM UTC by Eric Milles Last Updated: Fri Sep 15, 2023 04:17 AM UTC Owner: Marc MAZAS The new JavaCC 1.6.0 release is not recognizing our project nature (sf.eclipse.javacc.javaccnature) or project builder...
-
Hi Eric. Can I close the issue? TIA.
-
Well: first the projects must be opened, and changes must be allowed. So I bet it will fail and log an error. But one has to try. How are you files locked? See * @param description the project description * @param monitor a progress monitor, or null if progress * reporting is not desired * @exception CoreException if this method fails. Reasons include: * * This project does not exist in the workspace. * This project is not open. * The location in the local file system corresponding to the project...
-
Thanks for that. Do you know what happens if the .project file is locked? Our source control system uses locked for no change pending (unlike git). On Wed, Sep 13, 2023 at 7:14 AM Marc MAZAS mmazas@users.sourceforge.net wrote: Hi Eric. I have published version 1.6.1, which on startup iterates on all workspace's projects and updates the old nature and builder ids to the new ones, without any user action ; info messages are logged in the Error Log. [bugs:#92] https://sourceforge.net/p/eclipse-javacc/bugs/92/...
-
Home
-
Home
-
Home
-
Hi Eric. I have published version 1.6.1, which on startup iterates on all workspace's projects and updates the old nature and builder ids to the new ones, without any user action ; info messages are logged in the Error Log.
-
JavaCC Eclipse Plugin updated /README_Site.md
-
Version 1.6.1
-
-
-
-
-
Version 1.6.1 initial commit
-
Error: Could not find or load main class javacc
-
Giacomo Cau posted a comment on ticket #93
Thanks Mark, it works!
-
Hi Giacomo The culprit is a change from version 1.5.x (Eclipse is asked not to unpack the jars - under /plugins). I'll fix it. You can use the following workaround : extract from \D:\Zip\Eclipse\eclipse\plugins\sf.eclipse.javacc.core_1.6.0.jar the jar javacc-7.0.12.jar (within subdirectory /jars) to any place in your file system, and use 'your test project' / Project / Properties / JavaCC / Global Options / JavaCC jar file, use the Browse (file)... button to browse to the extracted jar. Marc
-
Hi Giacomo The culprit is a change from version 1.5.x (Eclipse is asked not to unpack the jars - under /plugins). I'll fix it. You can use the following workaround : extract from \D:\Zip\Eclipse\eclipse\plugins\sf.eclipse.javacc.core_1.6.0.jar the jar javacc-7.0.12.jar (within subdirectory /jars) to any place in your file system, and use <your test="" project=""> / Project / Properties / JavaCC / Global Options / JavaCC jar file, use the Browse (file)... button to browse to the extracter jar.</y...
-
Error: Could not find or load main class javacc
-
Hi Eric Well, I found a way to iterate at startup on all workspace's projects and update the old nature and builder ids to the new ones, without any user action ; info messages are logged in the Error Log. I'll publish a 1.6.1 version in a few days.
-
Hi Eric I can propose the following improvement: when you have projects with the JavaCC 1.5.x nature: when you upgrade the plug-in to 1.6.x: in the Project / Properties / JavaCC / GlobalOptions, the checkbox "Automatically ... adds a project nature" becomes automatically unchecked (but the .project keeps the old nature and builder but does not have the new ones; you have a "missing builder" in the Project / Properties / Builders, and a warning on the nature in the .project) : when the user checks...
-
1.6.0 project nature and builder not recognized
-
Hi Eric The ids have changed, and people can simply change them in their .project files (sf.eclipse.javacc.core.javaccnature & sf.eclipse.javacc.core.javaccbuilder). This was anticipated and documented in https://sourceforge.net/projects/eclipse-javacc/files/ (README_Site.md), but probably it was not obvious to find it. The https://eclipse-javacc.sourceforge.net/ index file was inadequate, I changed it to point to the doc. If you have suggestions, feel free. I have not much yet understood the 1.5.33...
-
<is it="" possible="" to="" support="" both="" sets="" of="" ids="" for="" the="" nature="" and="" builder?=""> Well, I've checked another time, and I don't see how to do it. No way to get rid of the plugin-id (sf.eclipse.javacc.core - see the extension point reference), unless to revert back to the previous structure, which is not my goal. The JDT nature / builder are org.eclipse.jdt.core.javanature / javabuilder, so the JavaCC Plug-in is similar now in v1.6.0. Note that the id changes in the .project...
-
Is it possible to support both sets of ids for the nature and builder? It is not really feasible for us to make the id changes and get all (100s) of developers updated to 1.6+. We are sticking with 1.5.33 for now, which is how I ran into the update site errors for that version. Also, it was somewhat difficult to get from the update site (https://eclipse-javacc.sourceforge.net) or marketplace entry (https://marketplace.eclipse.org/content/javacc-eclipse-plug) to here or your docs. It looks like there...
-
About the composite .xml files: the content.xml and artifacts.xml files are generated by the Eclipse PDE build system; can the composite ones be also generated? If not, this will be an additional manual step, which I am relunctant to add...
-
Hi again. I extracted the plugins and features directories under the 1.5.33 directory; now this version update site should work, right ? Marc
-
-
Hi Richard The ids have changed, and people can simply change them in their .project files (sf.eclipse.javacc.core.javaccnature & sf.eclipse.javacc.core.javaccbuilder). This was anticipated and documented in https://sourceforge.net/projects/eclipse-javacc/files/ (README_Site.md), but probably it was not obvious to find it. The https://eclipse-javacc.sourceforge.net/ index file was inadequate, I changed it to point to the doc. If you have suggestions, feel free. I have not much yet understood the...
-
Hi Richard The ids have changed, and people can simply change them in their .project files (sf.eclipse.javacc.core.nature & sf.eclipse.javacc.core.builder). This was anticipated and documented in https://sourceforge.net/projects/eclipse-javacc/files/ (README_Site.md), but probably it was not obvious to find it. The https://eclipse-javacc.sourceforge.net/ index file was inadequate, I changed it to point to the doc. If you have suggestions, feel free. I have not much yet understood the 1.5.33 issue,...
-
1.6.0 project nature and builder not recognized
-
Version 1.6.0: other projects / folders restructurations; doc / READMEs
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Enable occurrences marking in editors
-
Done in 1.6.0 :-)
-
JJDoc does not handle spaces in file paths properly
-
Support of JavaCC 6.0
-
The plugin still currently has no support of C++ code (for which a character scanner has to be developped ...)
