You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Grant Ingersoll <gs...@apache.org> on 2007/11/08 22:15:33 UTC

Plugins and Multiple projects

I have several subprojects of a project, plus another project that is  
not controlled by Maven.  I would like to setup the antrun plugin to  
run ANT on just the subproject that is not controlled by Maven (and I  
don't have the power to change this).  When I put the plugin  
definition into the lifecycle via:
<plugin>
         <artifactId>maven-antrun-plugin</artifactId>
         <executions>
           <execution>
             <id>Solr Build</id>
             <phase>compile</phase>
             <inherited>false</inherited>

             <configuration>
               <tasks if="">
                 <ant antfile="build.xml" dir="other-project"  
target="dist"/>
               </tasks>
             </configuration>
             <goals>
               <goal>run</goal>
             </goals>
           </execution>
         </executions>
       </plugin>

Maven tries to run this plugin on all of my modules and thus fails b/c  
the build.xml doesn't exist in any of the modules directories.  Is  
there some way to tell it to only run this plugin once, at the top  
level, but still execute the compile phase?

Thanks,
Grant


--------------------------
Grant Ingersoll
http://lucene.grantingersoll.com

Lucene Boot Camp Training:
ApacheCon Atlanta, Nov. 12, 2007.  Sign up now!  http://www.apachecon.com

Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Plugins and Multiple projects

Posted by Roland Asmann <Ro...@cfc.at>.
Seeing that you build the 'other-project' as well, wouldn't it be easier
to just throw in a pom.xml in that directory and configure the ant-run
there? That way your project 'is' a Maven-project from now on! ;-)

I believe that's the easiest solution, because a pom-type-project
(parent-project) doesn't execute the compile-phase. You could try to
configure it in another phase that IS run by the pom-lifecycle, but I
still believe the 'small conversion' I suggested would be the easiest way
to go...


> I have several subprojects of a project, plus another project that is
> not controlled by Maven.  I would like to setup the antrun plugin to
> run ANT on just the subproject that is not controlled by Maven (and I
> don't have the power to change this).  When I put the plugin
> definition into the lifecycle via:
> <plugin>
>          <artifactId>maven-antrun-plugin</artifactId>
>          <executions>
>            <execution>
>              <id>Solr Build</id>
>              <phase>compile</phase>
>              <inherited>false</inherited>
>
>              <configuration>
>                <tasks if="">
>                  <ant antfile="build.xml" dir="other-project"
> target="dist"/>
>                </tasks>
>              </configuration>
>              <goals>
>                <goal>run</goal>
>              </goals>
>            </execution>
>          </executions>
>        </plugin>
>
> Maven tries to run this plugin on all of my modules and thus fails b/c
> the build.xml doesn't exist in any of the modules directories.  Is
> there some way to tell it to only run this plugin once, at the top
> level, but still execute the compile phase?
>
> Thanks,
> Grant
>
>
> --------------------------
> Grant Ingersoll
> http://lucene.grantingersoll.com
>
> Lucene Boot Camp Training:
> ApacheCon Atlanta, Nov. 12, 2007.  Sign up now!  http://www.apachecon.com
>
> Lucene Helpful Hints:
> http://wiki.apache.org/lucene-java/BasicsOfPerformance
> http://wiki.apache.org/lucene-java/LuceneFAQ
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Plugins and Multiple projects

Posted by gsingers <gr...@yahoo.com>.
This is my understanding, too, but it doesn't seem to be working.  Is this a
bug?

And also, I am trying to build a project that is checked out via SVN
external and I have no say in their build process.  

Jim Sellers wrote:
> 
> I'm not 100% sure, but I think that you can put
> <plugin>
> <inherited>false</inherited>
> ....
> 
> HTH
> Jim
> 
> 
> On Nov 8, 2007 4:15 PM, Grant Ingersoll <gs...@apache.org> wrote:
> 
>> I have several subprojects of a project, plus another project that is
>> not controlled by Maven.  I would like to setup the antrun plugin to
>> run ANT on just the subproject that is not controlled by Maven (and I
>> don't have the power to change this).  When I put the plugin
>> definition into the lifecycle via:
>> <plugin>
>>         <artifactId>maven-antrun-plugin</artifactId>
>>         <executions>
>>           <execution>
>>             <id>Solr Build</id>
>>             <phase>compile</phase>
>>             <inherited>false</inherited>
>>
>>             <configuration>
>>               <tasks if="">
>>                 <ant antfile="build.xml" dir="other-project"
>> target="dist"/>
>>               </tasks>
>>             </configuration>
>>             <goals>
>>               <goal>run</goal>
>>             </goals>
>>           </execution>
>>         </executions>
>>       </plugin>
>>
>> Maven tries to run this plugin on all of my modules and thus fails b/c
>> the build.xml doesn't exist in any of the modules directories.  Is
>> there some way to tell it to only run this plugin once, at the top
>> level, but still execute the compile phase?
>>
>> Thanks,
>> Grant
>>
>>
>> --------------------------
>> Grant Ingersoll
>> http://lucene.grantingersoll.com
>>
>> Lucene Boot Camp Training:
>> ApacheCon Atlanta, Nov. 12, 2007.  Sign up now!  http://www.apachecon.com
>>
>> Lucene Helpful Hints:
>> http://wiki.apache.org/lucene-java/BasicsOfPerformance
>> http://wiki.apache.org/lucene-java/LuceneFAQ
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Plugins-and-Multiple-projects-tf4773704s177.html#a13736073
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Plugins and Multiple projects

Posted by Jim Sellers <ji...@gmail.com>.
I'm not 100% sure, but I think that you can put
<plugin>
<inherited>false</inherited>
....

HTH
Jim


On Nov 8, 2007 4:15 PM, Grant Ingersoll <gs...@apache.org> wrote:

> I have several subprojects of a project, plus another project that is
> not controlled by Maven.  I would like to setup the antrun plugin to
> run ANT on just the subproject that is not controlled by Maven (and I
> don't have the power to change this).  When I put the plugin
> definition into the lifecycle via:
> <plugin>
>         <artifactId>maven-antrun-plugin</artifactId>
>         <executions>
>           <execution>
>             <id>Solr Build</id>
>             <phase>compile</phase>
>             <inherited>false</inherited>
>
>             <configuration>
>               <tasks if="">
>                 <ant antfile="build.xml" dir="other-project"
> target="dist"/>
>               </tasks>
>             </configuration>
>             <goals>
>               <goal>run</goal>
>             </goals>
>           </execution>
>         </executions>
>       </plugin>
>
> Maven tries to run this plugin on all of my modules and thus fails b/c
> the build.xml doesn't exist in any of the modules directories.  Is
> there some way to tell it to only run this plugin once, at the top
> level, but still execute the compile phase?
>
> Thanks,
> Grant
>
>
> --------------------------
> Grant Ingersoll
> http://lucene.grantingersoll.com
>
> Lucene Boot Camp Training:
> ApacheCon Atlanta, Nov. 12, 2007.  Sign up now!  http://www.apachecon.com
>
> Lucene Helpful Hints:
> http://wiki.apache.org/lucene-java/BasicsOfPerformance
> http://wiki.apache.org/lucene-java/LuceneFAQ
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>