On Mon, Nov 24, 2008 at 12:00 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> > A big +1. Changing the published poms format is very impacting. Not > only for the maven client, but for all tools that are using the > repository as a server (ivy, buildr, maven proxies & repository > managers, etc...). It may be impacting but these tools should be transforming poms to a format that they internally understand and need, not directly relying on the pom format itself, as that design will make it nearly impossible to upgrade versions. For Java based clients, a lot of the transform work is already done for them in maven-shared-model. They just need to create a transformer for transforming from the canonical format to their internal format. That should give a start. And none of this would occur overnight. For maven 2.0.x, it is not trivial to make the changes. So this is more of a long-term thing that other tool developers need to start putting some brain-cycles into. Shane
