Maybe this could help:If you specify a parameter as always, but also add a setter for it, Plexus will call the setter.Use the setter to fill the JnlpConfig. -Robert > Date: Mon, 22 Aug 2011 13:35:50 +0200 > From: [email protected] > To: mojo.codehaus.org [email protected] > Subject: [mojo-dev] [DISCUSS] About MWEBSTART-168 > > Hi, > > I want to resolv this but I have a problem to do this. > > The ReportMojo use a simple property to obtain the jnlp file to use : > > /** > * Directory in the site directory where the jnlp artifacts and > jnlp sources files reside. > * > * @parameter expression="${jnlp.siteJnlpFile} > default-value="launch.jnlp" > * @required > */ > private String siteJnlpFile; > > but the JnlpMojo use a JnlpConfig class to stock the config of jnlp, > so impossible to use a common property for the report and jnlp mojo. > > I don't like the approach of using a separate object (the > JnlpConfig) in a mojo since wa can't have any documentation about the > format of the jnlpConfig configuration to produce (need to go and see > the class :(). > Moreover it is not possible then to use common stuff with other mojos... > > I would prefer to have a contract JnlpConfig and the mojo implements it. > In that way it would be possible to use common configuration properties > over different mojos. > > Any other ideas or point of view about this problematic ? > > thanks > > -- > Tony Chemit > -------------------- > tél: +33 (0) 2 40 50 29 28 > email: [email protected] > http://www.codelutin.com > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
