Jedi
  1. Jedi
  2. JEDI-31

Add or link to a description of how to set Annotation processor options for Maven/IDE

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Number of attachments :
      0

      Description

      I miss documentation at the project home page, on how to set annotation processor options for Maven and Eclipse.

        Activity

        Hide
        Christian Semrau added a comment -

        For Eclipse, this is fairly obvious:
        In the "Java Compiler / Annotation Processing" page of the project properties, add the desired key (e.g. jediSuppressSuffixes), with an empty value.

        For Maven, I pass the options directly as compiler arguments, as described here:
        http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html

        Add the following line to the maven-compiler-plugin's configuration element:
        <compilerArgument>-AjediSuppressSuffixes</compilerArgument>

        Show
        Christian Semrau added a comment - For Eclipse, this is fairly obvious: In the "Java Compiler / Annotation Processing" page of the project properties, add the desired key (e.g. jediSuppressSuffixes), with an empty value. For Maven, I pass the options directly as compiler arguments, as described here: http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html Add the following line to the maven-compiler-plugin's configuration element: <compilerArgument>-AjediSuppressSuffixes</compilerArgument>
        Hide
        Christian Semrau added a comment -

        Now that I've read at MCOMPILER-62 that multiple arguments cannot be passed in the <compilerArgument> element (despite the documentation saying otherwise), I opt for the map-like syntax and add the following to my POM:

        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>2.3.2</version>
          <configuration>
            <source>1.6</source>
            <target>1.6</target>
            <compilerArguments>
              <AjediSuppressSuffixes/>
            </compilerArguments>
          </configuration>
        </plugin>
        

        (Actually, I just switched to AjediSuppressClosureTypeSuffix, because I found overloading the functor factory and the corresponding proxy functor factory confusing.)

        It is fortunate that Jedi does not require values for its annotation processor options, because those could not be forwarded from Maven to javac as long as MCOMPILER-135 is unsolved.

        Show
        Christian Semrau added a comment - Now that I've read at MCOMPILER-62 that multiple arguments cannot be passed in the <compilerArgument> element (despite the documentation saying otherwise), I opt for the map-like syntax and add the following to my POM: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.6</source> <target>1.6</target> <compilerArguments> <AjediSuppressSuffixes/> </compilerArguments> </configuration> </plugin> (Actually, I just switched to AjediSuppressClosureTypeSuffix, because I found overloading the functor factory and the corresponding proxy functor factory confusing.) It is fortunate that Jedi does not require values for its annotation processor options, because those could not be forwarded from Maven to javac as long as MCOMPILER-135 is unsolved.

          People

          • Assignee:
            Lance Walton
            Reporter:
            Christian Semrau
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: