#20 Allow direct Maven plugin configuration

open
nobody
None
5
2007-08-06
2007-08-06
No

Jeremy Copernic writes:

I would prefer using a full maven-macker-plugin without any ant tasks and build.xml files.

I think it could be great if we could define all the macker.xml's rules directly into the pom.xml of the maven project, or simply specify the location of the macker.xml file like the JettyConfig file style. Something like that:

<plugin>
<groupId>maven-plugins</groupId>
<artifactId>maven-macker-plugin</artifactId>
<version>0.4.2</version>
<configuration>
<mackerConfig>${basedir}src/test/macker.xml</mackerConfig>
</configuration>

</plugin>

or

<plugin>
<groupId>maven-plugins</groupId>
<artifactId>maven-macker-plugin</artifactId>
<version>0.4.2</version>
<configuration>
<rulesets>
<ruleSet>
<accessRule>
<from>myClass</from>
<to>someJavaClass</to>
</accessRule>
</ruleSet>
</ruleSets>
.....
</configuration>

</plugin>

Discussion


Log in to post a comment.