You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andrew Green (JIRA)" <ji...@codehaus.org> on 2011/08/19 20:48:32 UTC

[jira] Created: (MNG-5161) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
------------------------------------------------------------------------------------------------------------------------------------

                 Key: MNG-5161
                 URL: https://jira.codehaus.org/browse/MNG-5161
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: Class Loading
    Affects Versions: 3.0.3
            Reporter: Andrew Green
            Priority: Minor


I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:

      <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>
          <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
        </configuration>
      </plugin>
      <plugin>
      	<groupId>org.codehaus.mojo</groupId>
      	<artifactId>build-helper-maven-plugin</artifactId>
      	<version>1.5</version>
      	<executions>
      		<execution>
      			<id>add-source</id>
      			<phase>generate-sources</phase>
      			<goals>
      				<goal>add-source</goal>
      			</goals>
      			<configuration>
      				<sources>
      					<source>${project.build.directory}/generated-sources/apt</source>
      				</sources>
      			</configuration>
      		</execution>
      	</executions>
      </plugin>

It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MCOMPILER-159) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MCOMPILER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298983#comment-298983 ] 

Mark Hobson commented on MCOMPILER-159:
---------------------------------------

Looks like a duplicate of MCOMPILER-157.
                
> generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-159
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-159
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>            Reporter: Andrew Green
>            Priority: Minor
>
> I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:
>       <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>
>           <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
>         </configuration>
>       </plugin>
>       <plugin>
>       	<groupId>org.codehaus.mojo</groupId>
>       	<artifactId>build-helper-maven-plugin</artifactId>
>       	<version>1.5</version>
>       	<executions>
>       		<execution>
>       			<id>add-source</id>
>       			<phase>generate-sources</phase>
>       			<goals>
>       				<goal>add-source</goal>
>       			</goals>
>       			<configuration>
>       				<sources>
>       					<source>${project.build.directory}/generated-sources/apt</source>
>       				</sources>
>       			</configuration>
>       		</execution>
>       	</executions>
>       </plugin>
> It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MCOMPILER-159) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MCOMPILER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MCOMPILER-159.
----------------------------------

       Resolution: Duplicate
    Fix Version/s: 3.0
         Assignee: Olivier Lamy

duplicate of MCOMPILER-157 
                
> generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-159
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-159
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>            Reporter: Andrew Green
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 3.0
>
>
> I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:
>       <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>
>           <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
>         </configuration>
>       </plugin>
>       <plugin>
>       	<groupId>org.codehaus.mojo</groupId>
>       	<artifactId>build-helper-maven-plugin</artifactId>
>       	<version>1.5</version>
>       	<executions>
>       		<execution>
>       			<id>add-source</id>
>       			<phase>generate-sources</phase>
>       			<goals>
>       				<goal>add-source</goal>
>       			</goals>
>       			<configuration>
>       				<sources>
>       					<source>${project.build.directory}/generated-sources/apt</source>
>       				</sources>
>       			</configuration>
>       		</execution>
>       	</executions>
>       </plugin>
> It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MCOMPILER-159) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MCOMPILER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reopened MCOMPILER-159:
------------------------------------


not yet fixed.
                
> generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-159
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-159
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>            Reporter: Andrew Green
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 3.1
>
>
> I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:
>       <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>
>           <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
>         </configuration>
>       </plugin>
>       <plugin>
>       	<groupId>org.codehaus.mojo</groupId>
>       	<artifactId>build-helper-maven-plugin</artifactId>
>       	<version>1.5</version>
>       	<executions>
>       		<execution>
>       			<id>add-source</id>
>       			<phase>generate-sources</phase>
>       			<goals>
>       				<goal>add-source</goal>
>       			</goals>
>       			<configuration>
>       				<sources>
>       					<source>${project.build.directory}/generated-sources/apt</source>
>       				</sources>
>       			</configuration>
>       		</execution>
>       	</executions>
>       </plugin>
> It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MCOMPILER-159) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MCOMPILER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MCOMPILER-159:
-----------------------------------

    Fix Version/s:     (was: 3.0)
                   3.1
    
> generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-159
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-159
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>            Reporter: Andrew Green
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 3.1
>
>
> I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:
>       <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>
>           <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
>         </configuration>
>       </plugin>
>       <plugin>
>       	<groupId>org.codehaus.mojo</groupId>
>       	<artifactId>build-helper-maven-plugin</artifactId>
>       	<version>1.5</version>
>       	<executions>
>       		<execution>
>       			<id>add-source</id>
>       			<phase>generate-sources</phase>
>       			<goals>
>       				<goal>add-source</goal>
>       			</goals>
>       			<configuration>
>       				<sources>
>       					<source>${project.build.directory}/generated-sources/apt</source>
>       				</sources>
>       			</configuration>
>       		</execution>
>       	</executions>
>       </plugin>
> It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Moved: (MCOMPILER-159) generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MCOMPILER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann moved MNG-5161 to MCOMPILER-159:
--------------------------------------------------

           Complexity:   (was: Intermediate)
          Component/s:     (was: Class Loading)
    Affects Version/s:     (was: 3.0.3)
                       2.3.2
                  Key: MCOMPILER-159  (was: MNG-5161)
              Project: Maven 2.x Compiler Plugin  (was: Maven 2 & 3)

> generatedSourcesDirectory should be included in list provided by org.apache.maven.project.MavenProject.getCompileClasspathElements()
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-159
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-159
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>            Reporter: Andrew Green
>            Priority: Minor
>
> I'm using a plugin (gwt-maven-plugin) that needs to know where all of my project's source code is, including generated sources. The standard compiler plugin (maven-compiler-plugin, v2.3.2) generates the sources correctly (from anntotations) and uses the generated code fine when compiling my project. But to get the gwt-maven-plugin to find the generated sources, I have to use the build-helper-maven-plugin to add the generated sources directory, as shown here:
>       <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>
>           <generatedSourcesDirectory>${project.build.directory}/generated-sources/apt</generatedSourcesDirectory>
>         </configuration>
>       </plugin>
>       <plugin>
>       	<groupId>org.codehaus.mojo</groupId>
>       	<artifactId>build-helper-maven-plugin</artifactId>
>       	<version>1.5</version>
>       	<executions>
>       		<execution>
>       			<id>add-source</id>
>       			<phase>generate-sources</phase>
>       			<goals>
>       				<goal>add-source</goal>
>       			</goals>
>       			<configuration>
>       				<sources>
>       					<source>${project.build.directory}/generated-sources/apt</source>
>       				</sources>
>       			</configuration>
>       		</execution>
>       	</executions>
>       </plugin>
> It shouldn't be necessary to use build-helper-maven-plugin here; the generated sources should automatically be on the classpath. As far as I can tell, this is a Maven issue, or perhaps a maven-compiler-plugin issue, and is not the fault of gwt-maven-plugin.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira