I share these doubts.
Why wrapping a Maven plugin with a Maven Plugin? I haven't watched the
code, but to make it work, you probably need to reuse pluginManagement
from Maven Core. This will make it unnecessary complex.
I'd prefer to fix it in the target plugin.
Also keep in mind that for instance the maven-release-plugin doesn't
analyse plugin configuration, so if you use a SNAPSHOT as plugin-version,
the result will be unstable after release.
Maybe I'm misunderstanding the examples, but both can be done without the
iterator-plugin and with less xml.
I'm wondering which issue you hit when writing this plugin, maybe there's
another solution to the core problem.
Robert
On Sun, 31 Mar 2013 16:16:39 +0200, Stephen Connolly
<[email protected]> wrote:
I have concerns that the plugin would either interact poorly with the
reactor, or encourage patterns of use where poor interaction with the
reactor is encouraged.
Additionally, the primary use cases, from what I can see, are all about
configuring things for specific environments, which is an anti-pattern
in my experience.
Having said that, I'm not going to block people pursuing this line, just
that I worry it will create a support burden that we may find difficult
to meet given our current inability (to my mind) to meet the
requirements existing plugins need.
My view is we should concentrate on maven's core competences and make
life easier for users within that sphere... So for example the
templating maven plugin makes it very easy to do something that many
people want to do (and given the JavaEE annotations requiring JNDI names
that include the jar name... This is a real problem even if we might
view as an anti-pattern)
Similarly the non-maven-jar plugin I released from my GitHub account
last week addresses issues a lot of people hit, but in a way that is as
close to best practice as possible.
From what I can see, I don't see a way of using this that isn't at least
2-3 anti- patterns at the same time... Perhaps you can enlighten me to
the contrary
Sent from my iPhone
On 31 Mar 2013, at 14:40, Karl Heinz Marbaise <[email protected]> wrote:
Hi to all developers,
i wan't to know what Maven developers think about this plugin...
Based on the name it can iterate through a list of values and with the
values it can call other plugins or a separate maven instance
(currently not very well documented I'm working on that).
The plugin code can be found here:
https://github.com/khmarbaise/iterator-maven-plugin
You can do things like this
(http://khmarbaise.github.com/iterator-maven-plugin/executor-overview.html):
<plugin>
<groupId>com.soebes.maven.plugins</groupId>
<artifactId>iterator-maven-plugin</artifactId>
<version>0.1.0</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>executor</goal>
</goals>
<configuration>
<items>
<item>test</item>
<item>prod</item>
<item>dev</item>
</items>
<pluginExecutors>
<pluginExecutor>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.4</version>
</plugin>
<goal>single</goal>
<configuration>
<descriptors>
<descriptor>${project.basedir}/@[email protected]</descriptor>
</descriptors>
</configuration>
</pluginExecutor>
</pluginExecutors>
</configuration>
</execution>
</executions>
</plugin>
and other things.
An example for invoking a Maven instance can be looked at an
integration test:
https://github.com/khmarbaise/iterator-maven-plugin/blob/master/src/it/invokerBasicTest/pom.xml
Do you have some ideas related to this plugin? Suggestions? etc. ?
Many thanks in advance...
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
