You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Xavier Toth <tx...@gmail.com> on 2006/03/10 22:36:17 UTC
plugin use in multiprojects seems broken
Maybe I'm missing something but the use of plugins in multiprojects seems
broken to me. I've got three projects that build rpms so I made a parent
projects to run them all. However unless I add the plugin into the parent as
in :
<modules>
<module>micro_proxy</module>
<module>socks</module>
<module>jwss</module>
</modules>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>rpm-maven-plugin</artifactId>
<version>1.0-alpha-2-SNAPSHOT</version>
<configuration>
<release>1</release>
<mappings>
</mappings>
</configuration>
</plugin>
</plugins>
</build>
the submodules won't build. I really don't want to run the plugin (rpm:rpm)
goal in the parent project. It seem to me that a mulitproject parent ought
to be able to ignore plugin goals that it doesn't have build information for
and simple pass them along to its submodules.
Xavier
Re: plugin use in multiprojects seems broken
Posted by Edwin Punzalan <ep...@exist.com>.
IIRC, plugins that behave like this should be updated instead. The
plugin should check the packaging of the project it is currently
building and if its "pom", then it should exit gracefully. Otherwise,
it proceeds as expected.
You can create an issue for the plugin so they can update it. Thanks.
Xavier Toth wrote:
> Maybe I'm missing something but the use of plugins in multiprojects seems
> broken to me. I've got three projects that build rpms so I made a parent
> projects to run them all. However unless I add the plugin into the parent as
> in :
> <modules>
> <module>micro_proxy</module>
> <module>socks</module>
> <module>jwss</module>
> </modules>
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>rpm-maven-plugin</artifactId>
> <version>1.0-alpha-2-SNAPSHOT</version>
> <configuration>
> <release>1</release>
> <mappings>
> </mappings>
>
> </configuration>
> </plugin>
> </plugins>
> </build>
>
> the submodules won't build. I really don't want to run the plugin (rpm:rpm)
> goal in the parent project. It seem to me that a mulitproject parent ought
> to be able to ignore plugin goals that it doesn't have build information for
> and simple pass them along to its submodules.
>
> Xavier
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin use in multiprojects seems broken
Posted by Brett Porter <br...@gmail.com>.
You'll need to provide more details. Why doesn't it work if you don't
put it in the parent? Where do you put it if not in the parent?
Regardless, it should work in the parent. It's a bug in the rpm plugin
if it attempts to produce an rpm for a pom - it should be testing the
packaging.
- Brett
On 3/11/06, Xavier Toth <tx...@gmail.com> wrote:
> Maybe I'm missing something but the use of plugins in multiprojects seems
> broken to me. I've got three projects that build rpms so I made a parent
> projects to run them all. However unless I add the plugin into the parent as
> in :
> <modules>
> <module>micro_proxy</module>
> <module>socks</module>
> <module>jwss</module>
> </modules>
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>rpm-maven-plugin</artifactId>
> <version>1.0-alpha-2-SNAPSHOT</version>
> <configuration>
> <release>1</release>
> <mappings>
> </mappings>
>
> </configuration>
> </plugin>
> </plugins>
> </build>
>
> the submodules won't build. I really don't want to run the plugin (rpm:rpm)
> goal in the parent project. It seem to me that a mulitproject parent ought
> to be able to ignore plugin goals that it doesn't have build information for
> and simple pass them along to its submodules.
>
> Xavier
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org