Quoting Michal Maczka <[EMAIL PROTECTED]>: > I imagined that there will be always one parser in m2 for all possible > released pom v4 variants and it will hide all the complexivity > related to changes in POM structure. Exactly like it used to be for m1 > where for example we had dual support > for "id" and "groupId"/"artifactId' tags in dependency. > So if we will have something like maven2-model-v4-1.0.2.jar - it will > contain the only parser which users/developers want to use > to parse all known variants of pom v4. Once we will have pom v403 we > will release maven2-model-v4-1.0.3.jar > which support all previous versions and this new version. Isn't it > simple enough?
Sorry if I confused the issue. As Jason said, if there are just additions, converters won't be needed and upgrading a JAR will just work. So exactly what you are saying is how it works currently. However, the artifact ID would be maven-model-4.0.0, maven-model-4.0.1, etc. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
