You can already configure plugins from settings.xml using profiles. The catch is that they must be used as part of the lifecycle (http://jira.codehaus.org/browse/MNG-860)
I recently changed jar:sign so that this is the case, and I assume it is for webstart. The other alternative is to use <properties> and use expressions in the individual poms. - Brett jerome lacoste wrote: > Hi, > > I think I've asked that in IRC only, but I don't remember seing an answer. > > Today the jar:sign and webstart:jnlp goals provide a way for the user > to sign jars. To perform this operation, some sensitive information is > required (mostly some passwords, maybe a user specific file path). > This information can be provided in the pom, or on the command line. > > I like the way the settings.xml works, so I am wondering if there's a > way for us plugin writers to let the user put plugin specific > information in there. > > One way I could see it, to make it generic, is to provide a sort of > template mecanism: > > in settings.xml: > > <pluginConfiguration> > <pluginConfigId></pluginConfigId> > <configuration> > <key>defaultValue</key> > </configuration> > </pluginConfiguration> > > then in my pom: > > <pluginConfigId></pluginConfigId> > <configuration> > ... > </configuration> > > That way we could just use the values defined in the settings.xml as > default, overriden is necessary. That would work for every plugin. > > Comments? > > Jerome > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
