When working on a maven plugin, I noticed that two attached artifacts can have the same name and overwrite each other when they are deployed. Is this by design? Maybe the artifacts attached to a project should be a set instead of a list, and a warning should be generated when one artifact replaces another. An easy way to reproduce this is to define the maven source plugin with two different execution ids. When the deploy plugin is run, the source jar is deployed twice, with the second overwriting the first. Changing the attached artifacts from a List to a Set would probably break a bunch of existing code, but it might be something for a maven 3.0 release.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
