Open coderChase opened 10 years ago
Hi, ADLParser is generated after performing maven install. please follow the installation instructions and do:
java-libs/mvn clean install
if you are going to open it using eclipse, you can also do:
java-libs/mvn eclipse:eclipse
cheers.
iago
Hi, icorbal Now I know this project uses the javacc maven plugin. So after the generate source phrase, the source codes are generated to target/generated-sources. For that, before I import this project into eclipse, I should run "mvn eclipse:eclipse" first.(is that right?)After I try this, I can view the code of ADLParser in eclipse, but there is an anothor question. Another error occurs:
An internal error occurred during: "Importing Maven projects".
Unsupported IClasspathEntry kind=4
And here is the reason I found:
The problem is caused by the fact that the STS (the Spring IDE/Eclipse) uses the m2e(clipse) plugin but that
eclipse:eclipse has been probably been run on the project. When m2e encounters a "var" .classpath entry, it throws
this error.
So I have to run "mvn eclipse:clean" to avoid this problem, but in this way, ADLParser cannot be resolved to a type again. My eclipse edition is "Eclipse IDE for Java EE Developers", is it that I use the wrong edition, or there are other reasons?
cheers.
chase
Hi Chase, you can always try to add the generated-sources folder into your build path. That way eclipse will also use the source code generated from javacc. You will have to do this for adl-parser and dadl-parser projects. Right click on the project, Properties, Java Build Path, Add Folder..., select target/generated-sources/javacc .
cheers,
iago
2013/12/17 coderChase notifications@github.com
Hi, icorbal Now I know this project uses the javacc maven plugin. So after the generate source phrase, the source codes are generated to target/generated-sources. For that, before I import this project into eclipse, I should run "mvn eclipse:eclipse" first.(is that right?)After I try this, I can view the code of ADLParser in eclipse, but there is an anothor question. Another error occurs:
An internal error occurred during: "Importing Maven projects". Unsupported IClasspathEntry kind=4
And here is the reason I found:
The problem is caused by the fact that the STS (the Spring IDE/Eclipse) uses the m2e(clipse) plugin but that eclipse:eclipse has been probably been run on the project. When m2e encounters a "var" .classpath entry, it throws this error.
So I have to run "mvn eclipse:clean" to avoid this problem, but in this way, ADLParser cannot be resolved to a type again. My eclipse edition is "Eclipse IDE for Java EE Developers", is it that I use the wrong edition, or there are other reasons?
cheers.
chase
— Reply to this email directly or view it on GitHubhttps://github.com/openEHR/java-libs/issues/10#issuecomment-30732166 .
Hi Iago, It's very nice of you to solve my problem. Thank you very much!
cheers,
chase
I just cannot find the class ADLParser. I can test adl-parser in command line, but after I import the project to eclipse using m2e, there are errors showing that ADLParser cannot be resolved to a type.