> > > > On 5/12/2010 00:43, Marshall Schor wrote: > > For the various distributions, we package "immediate" dependencies. In > > the past, I think that we have not included transitive dependencies, > > because many components we depend on have lots of dependencies of their > > own, which are not used and not needed for our particular use. > > > > The new build system is continuing this tradition; if there is a > > dependency of a dependency that you need, you would need to declare it > > as a "direct" dependency of your POM being packaged. > > > > One "advantage" of this is that it makes explicit in the POM what is > > being included, which helps in reviewing Licenses and Notice > > requirements that could flow from these dependencies. > > > > Does this seem reasonable? >
+1 for me too 2010/5/12 Thilo Götz <[email protected]> > > IMO, we should explicitly list the dependencies we ship. > Otherwise every release we'll have a lot of work checking > that our packages don't contain any unwanted libraries. > > I am +1, how would you suggest to do that? Apart from the POM dependencies list would you put them inside (for example) the README file or something else? Cheers. Tommaso
