Mojo's JSPC Maven Plugin
  1. Mojo's JSPC Maven Plugin
  2. MJSPC-45

The includeInProject property does not work

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0-alpha-1
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      (Actually, affects version 2.0-alpha-3, but that one is not in the list)

      Here's my plugin configuration:

      <plugin>
      <groupId>org.codehaus.mojo.jspc</groupId>
      <artifactId>jspc-maven-plugin</artifactId>
      <version>2.0-alpha-3</version>
      <configuration>
      <includeInProject>false</includeInProject>
      <source>1.5</source>
      <target>1.5</target>
      </configuration>
      <dependencies>
      <dependency>
      <!-- Use the Tomcat 6 JSP compiler -->
      <groupId>org.codehaus.mojo.jspc</groupId>
      <artifactId>jspc-compiler-tomcat6</artifactId>
      <version>2.0-alpha-3</version>
      </dependency>
      </dependencies>
      <executions>
      <execution>
      <goals>
      <goal>compile</goal>
      </goals>
      </execution>
      </executions>
      </plugin>

      with this configuration, I get the following message in the maven log:

      [WARNING] Compiled JSPs will not be added to the project and web.xml will not be modified, either because includeInProject is set to false or because
      the project's packaging is not 'war'.

      but in the packaged war, the WEB-INF\classes\jsp\ directory contains the compiled jsp classes!

        Activity

        Hide
        Milan Gerza added a comment -

        Setting

        <compile>false</compile>
        <includeInProject>false</includeInProject>

        worked for me - the jsp files were compiled anyway.

        Show
        Milan Gerza added a comment - Setting <compile>false</compile> <includeInProject>false</includeInProject> worked for me - the jsp files were compiled anyway.
        Hide
        yk added a comment -

        I am wondering how setting 'compile' to false can trigger the compilation, as this setting explicitly asks JSP compiler NOT TO COMPILE. At least in my configuration it works as excepted and documented - only Java sources are generated, they are not compiled.

        Could you please clarify how did you manage not to include compiled classes? I doubt the configuration you provided works as you describe.

        Show
        yk added a comment - I am wondering how setting 'compile' to false can trigger the compilation, as this setting explicitly asks JSP compiler NOT TO COMPILE. At least in my configuration it works as excepted and documented - only Java sources are generated, they are not compiled. Could you please clarify how did you manage not to include compiled classes? I doubt the configuration you provided works as you describe.

          People

          • Assignee:
            Unassigned
            Reporter:
            Morten Lauritsen Khodabocus
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: