On Thu, Jun 30, 2005 at 11:51:26AM +1000, Dion Gillard wrote: > On 6/30/05, Incze Lajos <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 30, 2005 at 10:00:58AM +1000, Dion Gillard wrote: > > > Sharing the jelly scripts means that the shared code should be in a > > > separate plugin so that at run time it can be found. > > > > > > Extending the base plugin pom and properties is just a build time issue, > > > right? > > > > > > > If I define a dependency in the parent POM, then it won't > > be available when the plugin runs. E.g.: > > > > master > > declares dependency commons-jelly-tags-log > > plugin1 > > extends master POM and shoud use e.g. the commons-jelly-tags-log > > plugin2 > > extends master POM and shoud use e.g. the commons-jelly-tags-log > > ... > > > > The dependency is available at build time tests but not after > > plugin:install. > > > > Am I missing something? > > Nope, you're not missing anything. The extended (master in your case) > pom isn't 'installed' when plugin:install is invoked. > > Depending on where the master pom is relative to the child, you could > copy it over as part of the install, but that's very non-standard. > > It would be better if the install process generated a complete pom for > you, but it doesn't.
Many thanks. incze --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
