Sorry, I never got these emails in my inbox... dunno why.  So I haven't just
been ignoring you ;-)

Anyways, looks like a bug in the Groovy descriptor extractor.  I've filled
an issue here:

    http://jira.codehaus.org/browse/MGROOVY-40

Will try to get that fixed asap.

--jason



Andrew Perepelytsya wrote:
> 
> In a nice tradition of answering one's own questions... ;)
> 
> Jason't other thread about site goal and similar symptoms gave me another
> idea, which finally shaped into a solution. This could be included in the
> Groovy m2 plugins development guide, smth under 'Building Groovy m2
> plugins in a reactor/multi-module project'.
> 
> Full poms are available at the above mentioned SVN locations, I'll post
> snippets here only.
> 
> Parent:
> =======
> <build>
>         <plugins>
>             <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-plugin-plugin</artifactId>
>                 <configuration>
>                     <!--
>                         *MUST* override the extractors to disable
> everything
>                         except java, as groovy can handle both java and
> groovy files.
>                         Duplicate processing chokes maven.
>                         Java is the default for plugin implementation
> language,
>                         overridable in individual projects.
>                     -->
>                     <extractors>
>                         <extractor>java</extractor>
>                         <!-- add custom default extractors here if needed
> -->
>                         <!-- extractor>bsh</extractor -->
>                     </extractors>
>                 </configuration>
>                 <dependencies>
>                     <dependency>
>                         <groupId>org.codehaus.mojo</groupId>
>                         <artifactId>groovy-mojo-tools</artifactId>
>                         <version>1.0-alpha-3-SNAPSHOT</version>
>                     </dependency>
>                 </dependencies>
>             </plugin>
>         </plugins>
>     </build>
> 
> 
> The key here is the dependency of the plugin AND extractor configuration.
> It's critical to not enable groovy extractor for plugins implemented in
> Java, as maven will try to process them with both java and groovy and
> fail.
> 
> Child m2 plugin project implemented in groovy (the same build/plugins
> section):
> ===============================
>             <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-plugin-plugin</artifactId>
>                 <configuration>
>                     <extractors>
>                         <!--
>                             *MUST* override the extractors to disable
> everything
>                             except groovy, as groovy can handle both java
> and groovy files.
>                             Duplicate processing chokes maven.
>                             The rest of the config is inherited.
>                         -->
>                         <extractor>groovy</extractor>
>                     </extractors>
>                 </configuration>
>             </plugin>
> 
> Hope it saves much pain to others. And the best part is those settings are
> available in released m2 plugins, which lessens the snapshot pain.
> 
> Cheers!
> Andrew
> 

-- 
View this message in context: 
http://www.nabble.com/-groovy-user--Let-your-Mojo%27s-be-Groovy-baby%21-tf3529339s177.html#a10689632
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to