| [cdt-dev] Eclipse Committer does not give me advantage |
|
Hi CDT and Eclipse guys Today I tried to used Eclipse Committer for everything I want to do including generating UMLet Eclipse plugin. Within UMLet package, there is a module called umlet-elements. Originally it does not need to access CDT function. Attached pom.xml is from UMLet GitHub site. Now I need to change umlet-element to access CDT function(s). Although I have all CDT code within the Committer, but maybe bcos I did not set correctly, now the compilation complains: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project umlet-elements: Compilation failure: Compilation failure: [ERROR] C:\Users\mcheng\FlexTrade\autoplugin\qfixsoden_old\umlet-elements\src\main\java\com\baselet\element\interfaces\GridElement.java:[15,36] package org.eclipse.cdt.core.dom.ast does not exist [ERROR] C:\Users\mcheng\FlexTrade\autoplugin\qfixsoden_old\umlet-elements\src\main\java\com\baselet\element\interfaces\GridElement.java:[88,9] cannot find symbol [ERROR] symbol: class IASTNode [ERROR] location: interface com.baselet.element.interfaces.GridElement If I used my ugly way to modify pom.xml to be pom.CDT.xml, and at the same time by adding the need jar file into my local maven repository, then the Committer is happy. Please guide how to make the whole thing elegant. Thanks. Sent from Mail for Windows 10 |
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> <modelVersion>4.0.0</modelVersion> <parent> <groupId>com.umlet</groupId> <artifactId>umlet-parent</artifactId> <version>14.4.0-SNAPSHOT</version> </parent> <artifactId>umlet-elements</artifactId> <properties> <javacc.gen.dir>${project.build.directory}/generated-sources/annotations</javacc.gen.dir> <!-- reuse the annotation-processing gendir to avoid too many separate src folders for eclipse plugin; perhaps it would be more correct to create a separate javacc subdir --> </properties> <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </dependency> <!-- during tests log with log4j --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <!-- generate javacc classes (it would be preferable to generate them into a separate target/generated-sources subdir, but this currently doesn't work with the way how source folders are linked in the umlet-eclipse-plugin project) --> <plugin> <groupId>com.helger.maven</groupId> <artifactId>ph-javacc-maven-plugin</artifactId> <version>2.8.0</version> <executions> <execution> <id>javacc</id> <phase>generate-sources</phase> <goals> <goal>javacc</goal> <!-- <goal>jjdoc</goal> --> </goals> <configuration> <javadocFriendlyComments>true</javadocFriendlyComments> <sourceDirectory>src/main/javacc</sourceDirectory> <outputDirectory>${javacc.gen.dir}</outputDirectory> </configuration> </execution> </executions> </plugin> <!-- add the generated sources to the build path --> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.7</version> <executions> <execution> <id>add-source</id> <phase>generate-sources</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <source>${javacc.gen.dir}</source> </sources> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> <modelVersion>4.0.0</modelVersion> <parent> <groupId>com.umlet</groupId> <artifactId>umlet-parent</artifactId> <version>14.4.0-SNAPSHOT</version> </parent> <artifactId>umlet-elements</artifactId> <properties> <javacc.gen.dir>${project.build.directory}/generated-sources/annotations</javacc.gen.dir> <!-- reuse the annotation-processing gendir to avoid too many separate src folders for eclipse plugin; perhaps it would be more correct to create a separate javacc subdir --> </properties> <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </dependency> <!-- during tests log with log4j --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.eclipse.cdt</groupId> <artifactId>core</artifactId> <version>6.8.0</version> </dependency> </dependencies> <build> <plugins> <!-- generate javacc classes (it would be preferable to generate them into a separate target/generated-sources subdir, but this currently doesn't work with the way how source folders are linked in the umlet-eclipse-plugin project) --> <plugin> <groupId>com.helger.maven</groupId> <artifactId>ph-javacc-maven-plugin</artifactId> <version>2.8.0</version> <executions> <execution> <id>javacc</id> <phase>generate-sources</phase> <goals> <goal>javacc</goal> <!-- <goal>jjdoc</goal> --> </goals> <configuration> <javadocFriendlyComments>true</javadocFriendlyComments> <sourceDirectory>src/main/javacc</sourceDirectory> <outputDirectory>${javacc.gen.dir}</outputDirectory> </configuration> </execution> </executions> </plugin> <!-- add the generated sources to the build path --> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.7</version> <executions> <execution> <id>add-source</id> <phase>generate-sources</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <source>${javacc.gen.dir}</source> </sources> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>