-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there,
just to give my feedback on the thread: +1 for NOT overloading 2.1 When it is about further versions and long term future of maven: - -infinity for artifact="org.apache.maven:maven-project:2.0.8" How do you want to express versions ranges then? Mix it all together? With XML it is possible to still "understand" the content even if a new attribute or element has been added that you do not know yet. when you have colon separated lists this is NOT possible. Further the unfamiliar reader has NO idea what the of the n.th segment is cause it is NOT named. He might not even know if the separator is "." or ":". If you see groupId="foo" you can google for "groupId" and you might find what you are looking for. +1 for more readable POMs I personally like the idea of the attributes because it makes it a lot easier to write the POMs, cause you do not have to open and <tag> close a tag </tag> and may end in <groupId>foo</artifactId> copy and paste mistakes. However when I scanned the big example <http://svn.apache.org/viewvc/maven/archiva/trunk/pom-4.1.0.xml?content-type=text%2Fplain&view=co> I did not get the impression, that it is really easier to read, since your eyes get overdosed by the dominating pattern <dependency groupId="org.apache.maven.archiva" artifactId= so you miss the important things even though it is more compact. +1 for <dependency ...> <excludeAll/> </dependency> but for the very long run. I think there are more such feature requests, that users would love to see. Simple have a look at the exclude and include parameters of the dependency-plugin. However it would still be possible for the install/deployment to transform the <excludeAll/> to a maven 2.0.4 compatible syntax automatically - just calculate the transitive dependencies and generate individual excludes for it. File a JIRA wish ticket for it... But not for 2.1. Is there a smart way to make it possible to allow feature-compatible syntax changes by having a plugin so people with "older versions" but at least maven x.y (>2.1) would NOT be lost? Best regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHveSYmPuec2Dcv/8RAku7AJ9ETwe1+d45tvGUjeEC5MKqJB9ivACeO9az z09KdsDNWX31DGI/NT25b30= =7A3v -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
