2007/11/28, Carlos Sanchez <[EMAIL PROTECTED]>: > > On Nov 28, 2007 6:40 PM, Richard van Nieuwenhoven <[EMAIL PROTECTED]> wrote: > > The reason for me is that eclipse is the source of the jars and eclipse > > does repeat the group name in the jar name. > > > > It looks very strange to have 10 different jars in the classpath all > > called "resource.jar". And what would happen when you need to package > > the jars together in a directory (ear, war, standalone tool). What would > > the resulting MANIFEST.MF look like. > > plugins (war, ear,...) should support and even make it the default, to > package the jars using the full group+arifact id, because using just > the artifactId has limitations. What happens now if you have 2 jars > with same artifactId and version in a war? they overwrite each other > > This would be great in an ideal world. Lets consider the required changes :
- war plugin to create required WEB-INF/lib - jar/ear/ejb plugin to create the correct MANIFEST entries - assembly plugin to bundle dependencies Adn now, consider how many builds could be broken by such changes...
