Hi,
I am thinking about writing a m2 plugin for Cargo
(http://cargo.codehaus.org). Here's what a typical configuration for such a
plugin could be:
<configuration>
<containers>
<container>
<key>resin3x</key>
<homeDir>c:/apps/resin-3.0.9</homeDir> |
<zipUrlInstaller>
<url>http://www.caucho.com/download/resin-3.0.9.zip</url>
<installDir>${basedir}/target/install</installDir>
</zipUrlInstaller>
<output>${basedir}/target/resin-cargo.log</output>
<append>false</append>
<log>${basedir}/target/resin-log.log</log>
<configuration>
<hint>standalone</hint>
<dir>${basedir}/target/resin</dir>
<properties>
<property>
<name>cargo.servlet.port</name>
<value>8080</value>
</property>
<property>
<name>cargo.logging</name>
<value>high</value>
</property>
</properties>
</configuration>
</container>
</containers>
</configuration>
As you can see there are at least 2 properties (and possibly more) that
depends on the machine the build is executing: <homeDir> and the port to use
(8080 in the example).
What is the mechanism to let users define these properties so that they are
not checked-in the SCM?
Is there a mechanism to extend the settings.xml file and have plugins
automatically get properties from there (something like the direct
equivalent of the <plugins><plugin><configuration> entries in the POM)?
Thanks
-Vincent
_________________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
