On Fri, Nov 27, 2009 at 9:11 PM, Eric Malotaux <[email protected]> wrote:
> > > 2009/11/27 Milos Kleint <[email protected]> > > >> >> On Fri, Nov 27, 2009 at 5:05 PM, Eric Malotaux <[email protected]>wrote: >> >>> Hi, >>> >>> I'm not sure I interpret the section "Maven Dependency vs NetBeans >>> runtime dependency" in http://mojo.codehaus.org/nbm-maven-plugin/ right. >>> Does it mean that maven transitive nbm dependencies are transformed into >>> direct NetBeans module dependencies in the manifest file? >>> >> >> quite opposite. Only direct module dependencies are translated into a NB >> runtime dependency. >> > > Does this mean that all transitive dependencies on Netbeans modules must be > included as direct dependencies in the pom? Because, if I don't, the classes > in the transitive modules are not available at runtime? > yes, since 3.0 nbm-maven-plugin, there is a sort of used classes checker that shall warn you of this at compile time. It's not bulletproof though. In any case the non-direct netbeans module deps don't get included in an entry in the manifest and will fail at runtime. in maven 3.0+ we might be able to properly model the netbeans runtime dependencies within maven. I haven't really examined that option yet.. Milos > >> Milos >> >> >> >>> >>> I have a nbm application that depends on a netbeans module that in turn >>> depends on a netbeans library wrapper module. I expected that this would >>> work, but the nbm-manifest goal gives an error without listing the offending >>> class, i.e. the class that was not found in a netbeans module dependency. >>> >>> I include a simple test setup as attachment. >>> >>> -- >>> Eric Jan Malotaux >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> > > > -- > Eric Jan Malotaux >
