I think you have to mark the plugin as "inherited" in the child pom file also.
On Tue, Oct 30, 2012 at 2:48 AM, Dan Tran <[email protected]> wrote: > sorry, i meant maven-bundle-plugin. and your answer is exactly what I > am looking for > > big thanks > > -Dan > > On Mon, Oct 29, 2012 at 11:13 PM, Andreas Pieber <[email protected]> wrote: >> Hey Dan, >> >> Do you really mean the maven-plugin-plugin or the maven-bundle-plugin (as I >> assume since you referenced the Felix group). >> >> In case you mean the maven-bundle-plugin it depends which properties you >> mean. AFAIK different properties are merged, same properties are merged. >> E.g. if you define a package-export and bundle-import in the parent, but >> package-import and package-export in the client, the bundle-import will be >> taken from the parent, package-import and export from the child. >> >> Hope this helps. >> >> Kind regards, >> Andreas >> >> On Tue, Oct 30, 2012 at 6:26 AM, Dan Tran <[email protected]> wrote: >>> >>> Hi, >>> >>> This question should go to felix group, but I think we have experts >>> here who many be able to help me with this question >>> >>> Currently I have maven-plugin-plugin configure at the parent pom >>> outside of my projects. >>> >>> once a while I need to override the 'instructions' settings from sub >>> project. The question here should I just add/set the 'changed' portion >>> and assume maven-bundle-plugin would merge the 'changed' portion to >>> the one already defined at my parent pom? >>> >>> Thanks >>> >>> -Dan >> >>
