sure but each project should not do that and using standard OO principles i can encapsulate it in reusable artifacts
i average 5 deps per artifact and have (9 different) assemblies that result in about 84 jars each, with no dependency management sections and i have reproducible builds by factoring out common dependencies into reused artifacts I have isolated the efferent dependencies and stabilised them as a mental execise imagine that each class is a method and each artifact is a class, each group is a package, now refactor, you have read Martin Fowler of course... On Tue, 12 Feb 2008 13:17:09 Martijn Dashorst wrote: > On 2/12/08, Michael McCallum <[EMAIL PROTECTED]> wrote: > > You can change the tool to make a bad pom look good but at the end of the > > day > > there is something wrong if your declared dependency list looks like > > that... > > How come? To get reproducible builds, you need to specify the versions of > all your dependencies, including the transitive ones (e.g. to resolve > version conflicts). This makes the list of dependencies huge. > Martijn -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
