[
http://jira.codehaus.org/browse/MGROOVY-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161174#action_161174
]
Rob van Maris edited comment on MGROOVY-181 at 1/16/09 7:12 AM:
----------------------------------------------------------------
Jason, you're right. It can actually be configured. What I wanted is to use the
Maven default project layout, but with the Groovy code in the same directories
as the Java code (instead of in a separate groovy directory hierarchy). Based
on your feedback I created the configuration below and it works.
{code:xml}<plugin>
<groupId>org.codehaus.groovy.maven</groupId>
<artifactId>gmaven-plugin</artifactId>
<executions>
<execution>
<id>compile-time</id>
<goals>
<goal>generateStubs</goal>
<goal>compile</goal>
</goals>
<configuration>
<sources>
<fileset>
<directory>${pom.basedir}/src/main/java</directory>
<includes>
<include>**/*.groovy</include>
</includes>
</fileset>
</sources>
</configuration>
</execution>
<execution>
<id>test-time</id>
<goals>
<goal>generateTestStubs</goal>
<goal>testCompile</goal>
</goals>
<configuration>
<sources>
<fileset>
<directory>${pom.basedir}/src/test/java</directory>
<includes>
<include>**/*.groovy</include>
</includes>
</fileset>
</sources>
</configuration>
</execution>
</executions>
</plugin>code}
You might want to add this to the documentation as an example. Anyway, thanks
for the help!
was (Author: robvanmaris):
Jason, you're right. It can actually be configured. What I wanted is use
the Maven default project layout, but with the Groovy code in the same
directories as the Java code. Based on your feedback I created the
configuration below and it works.
{code:xml}
<plugin>
<groupId>org.codehaus.groovy.maven</groupId>
<artifactId>gmaven-plugin</artifactId>
<executions>
<execution>
<id>compile-time</id>
<goals>
<goal>generateStubs</goal>
<goal>compile</goal>
</goals>
<configuration>
<sources>
<fileset>
<directory>${pom.basedir}/src/main/java</directory>
<includes>
<include>**/*.groovy</include>
</includes>
</fileset>
</sources>
</configuration>
</execution>
<execution>
<id>test-time</id>
<goals>
<goal>generateTestStubs</goal>
<goal>testCompile</goal>
</goals>
<configuration>
<sources>
<fileset>
<directory>${pom.basedir}/src/test/java</directory>
<includes>
<include>**/*.groovy</include>
</includes>
</fileset>
</sources>
</configuration>
</execution>
</executions>
</plugin>
{code}
You might want to add this to the documentation as an example. Anyway, thanks
for the help!
> Allow configuration of other location for test sources.
> -------------------------------------------------------
>
> Key: MGROOVY-181
> URL: http://jira.codehaus.org/browse/MGROOVY-181
> Project: GMaven
> Issue Type: Improvement
> Components: testCompile
> Affects Versions: 1.0-rc-3
> Reporter: Rob van Maris
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: 1.0-rc-5
>
>
> The GMaven documentation describes how to change the location for the groovy
> sources, using the configuration/sources element in the plugin configuration.
> I would expect a similar option for changing the location of the
> test-sources, but there does not seem to be any. This is needed if one would
> want to keep the same subdirectories in both src/main and src/test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
