John Casey wrote:
To me, all of this points to a dire need to separate dependency metadata from the POM that all of these derivative artifacts shares.
I could imagine this would also ease long-term interoperability of different Maven versions with the repository. Imagine the day when the POM evolves to the next model version which to my knowledge will prevent any Maven 2.0.x from reading such a POM, failing the build. Those projects that employ Maven 2.1+ will populate the repo with these new POMs. It would be quite frustrating for a Maven 2.0.x user that he cannot use the artifacts built by Maven 2.1+ as dependencies just because the POM format has changed. If the artifact metadata is separated from the POM, the POM could more freely evolve without the risk of breaking consumers of a dependency as long as only the artifact metadata model is compatible.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
