I have never needed to create a project like this, so I've never run into this specific problem myself nor have I dug through the Maven source code to find out what the absolute restrictions are.
In general, you should avoid naming artifacts with the same groupId and artifactId. That's it. If you require more absolute/specific information, the Maven source code is available, along with a variety of documentation in the Wiki, Maven website, archives of mailing lists, etc. Wayne On 5/30/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Wayne Fay ha scritto: > groupId + artifactId + versionId uniquely identifies artifacts in > Maven. Therefore multiple children with the same groupId and > artifactId in a given project is invalid. > > Change the artifactId of one of the offending children. There is no > other "solution" or "workaround". > > Wayne This is not coherent. You say groupId + artifactId + versionId uniquely identify an artifact. So I should be able to manage multiple versions of the same artifact in a single reactor build. What you say should only apply to 2 modules having all 3 values identical... Is this considered a limit of maven? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
