thanx for the hint.
This actually solved the invalid char problem, but the code generated did
not work with my existing parts.

Found a configuration that works for me.

     <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>javacc-maven-plugin</artifactId>
        <version>2.4</version>
             <dependencies> 
       <dependency> 
         <groupId>net.java.dev.javacc</groupId> 
         <artifactId>javacc</artifactId> 
         <version>4.2</version> 
       </dependency> 
     </dependencies>
         <executions>
          <execution>
            <phase>generate-sources</phase>
           <id>jjtree-javacc</id>
            <goals>
              <goal>jjtree-javacc</goal>
            </goals>
            <configuration>
              <isStatic>false</isStatic>
              <nodeUsesParser>true</nodeUsesParser>
              <sourceDirectory>${basedir}/src/main/javacc</sourceDirectory>
             
<outputDirectory>${project.build.sourceDirectory}</outputDirectory>
            </configuration>
          </execution>
        </executions>
      </plugin>

thank u
Bertram



Benjamin Bentmann wrote:
> 
> Bertram wrote:
> 
>> When using the maven plugin (see below the pom.xml snip) the plugin
>> creates
>> an invalid jj-file.
>> 
>> [...9
>> 
>> All the javacc jars I found on my machine are v4.1
> 
> As listed in the "Project Dependencies" [0], the javacc-maven-plugin:2.5 
> uses javacc 4.1 as well. You can try downgrading to 
> javacc-maven-plugin:2.4.1 which uses javacc 4.0 or upgrading to javacc 
> 4.2 by adding the snippet
> 
>    <plugin>
>      <groupId>org.codehaus.mojo</groupId>
>      <artifactId>javacc-maven-plugin</artifactId>
>      <version>2.5</version>
>      <!-- override default plugin dependency -->
>      <dependencies>
>        <dependency>
>          <groupId>net.java.dev.javacc</groupId>
>          <artifactId>javacc</artifactId>
>          <version>4.2</version>
>        </dependency>
>      </dependencies>
>      ...
>    </plugin>
> 
> to your POM.
> 
> Since the actual code generation is the responsibility of the javacc 
> library and not the wrapping Maven plugin, you would need to report this 
> issue to the javacc developer team if it persists in their latest release.
> 
> 
> Benjamin
> 
> 
> [0] http://mojo.codehaus.org/javacc-maven-plugin/dependencies.html
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/javacc-maven-plugin-creates-invalid-jj-file-from-jjt-file-tp22845508p22906753.html
Sent from the mojo - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to