Herve, Just a proposal: Maven could loosen its parsing rules when it detects versions greater than it is configured to accept. This can't be without limits, of course, perhaps in the range of a single point release: 4.0 <= 4.0.x < 4.1. But perhaps within the 4.0.x series, it would accept undeclared elements instead of strict parsing against the XSD. So if a 4.0.0 parser is given a 4.0.1 POM, it must at least match 4.0.0 but also accepts undeclared elements.
Forward compatibility would be nice. Paul On Tue, Apr 8, 2008 at 4:16 PM, Hervé BOUTEMY <[EMAIL PROTECTED]> wrote: > Le mardi 08 avril 2008, Paul Benedict a écrit : > > In Commons Validator, we updated the DTD even in point releases. I don't > > see the harm in doing the same here. After all, if the POM is 4.0.0, why > > not create a 4.0.1? It sounds like Maven 2.1 will have a 4.1 version. > > > > Paul > because if you use 4.0.1 for your project, and upload your component to a > repository, everybody depending on your component will need to support > 4.0.1 > or they'll get a failure parsing a 4.0.1 pom with their Maven runtime > supporting only 4.0.0 pom > > to support a 4.1 version, I imagine there will be some trick to implement > to > upload simultaneously the original 4.1 pom version to the repository and a > generated 4.0.0 for compatibility with Maven 2.0.x > > Hervé > >
