The field metadata when creating plugins is read from source files, so
is not available when the original source is not. The metadata is
available in the plugin in {{META-INF/maven/plugin.xml}}, but at this
point there is no way to incorporate it when building a new plugin.We currently recommend building your plugins using composition instead of inheritence. Cheers, Brett On 11/25/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote: > hi, > > i am planning to develop a plugin similar to the assembly:directory > goal so i am looking at extending the AbstractAssemblyMojo to re-use > some of its properties and code. the configuration is similar to that > of the assemblies but we would like to rewrite and add some more > project features. my problem is that the properties in the parent > class is not being initialized properly in our custom classes. as an > example the descriptor variable is always set to null, but the > configuration properties that we added are initialized properly. > > anybody have a clue what we missed? i am looking at the > DirectoryMojo source code and it is implemented the same way. thanks. > > ciao! > > -- > > "Programming, an artform that fights back" > > Anuerin G. Diaz > Registered Linux User #246176 > Friendly Linux Board @ http://mandrivausers.org/index.php > http://capsule.ramfree17.org , when you absolutely have nothing else > better to do > > --------------------------------------------------------------------- > 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]
