-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/28/10 13:16 , Wildam Martin wrote: > > Convinced - yes, I also use the * quite never and yes, it would be too > verbose and somwhat not "normalized". > > OK, alternative: extra statement, maybe above the list of imports > where you can declare it by package. At this point, the proper place could be the package itself. I mean, a module is composed of one or more packages; but you can usually identify the "main" package (OSGi and NB Platform actually designate the module by means of its main package name). Once we get to the package, we could use an annotation. And probably Lombok could be just used to translate the annotation in the proper underlying artifacts (I can see it working for the NBPlatform and eventually Maven - even though I'm a bit puzzled about the idea of the code to modify the POM...).
There are still problems, though. With Maven, a very convenient way to declare dependencies is with a global (= master POM) dependencyManagement section, so you're sure you're using consistent dependency versions for the whole project. This approach clashes with the idea of declaring dependency versions at module level. - -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people fabrizio.giud...@tidalwave.it -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwohv8ACgkQeDweFqgUGxdzvACcCq0GnXAHiiMN/UzyKbkWj+RZ I1gAoIFhdaxrRoxqWsZ/cZazi1r0aLWM =qCbl -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
