The only thing preventing changing the groupId/ArtifactId is that if you do, it breaks dependency resolution and hence the maven model. That is pretty serious.
Now, ... perhaps if there were some sort of alias facility so that dependency resolution could be told that two different Artifact coordinate sets were really the same up to version number ? Until then - all you have is version number to play with. Stan -----Original Message----- From: Paul Gier [mailto:[email protected]] Sent: Thursday, July 09, 2009 11:54 AM To: Maven Developers List Subject: Re: Depending on Artifacts not in central [stuff deleted ... ] So I don't really know if/how this can work with also making it easy for users of our projects to depend on our artifacts without using our repository. I would be fine with changing the groupId (maybe prefixing org.jboss) for rebuilt jars if there was an easier way to sync with the original groupId in the dependency tree. --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
