Sorry but I am quite annoyed by this. Trygve mentioned on the user list that the id element was deprecated some 3 years ago, that's 2 years before I joined the Maven team. I haven't been aware that it was deprecated until this recent thread on the user list. Apparently the docs patch by Dennis at MAVEN-1410 has never been applied. When I released the last version of the pom plugin, I spent quite some time getting the validation routines to work and I compiled a table of required elements [1]. That was about half a year ago, nobody complained since, nor during vote.
The main problem is that I'm not sure if some plugins don't still expect/use the id element, I'd have to check. Also, as pointed out at MAVEN-1410, we can't just change the POM-3 xsd, as it might break some existing builds. The consensus at MAVEN-1410 seems to have been to just document the deprecation, but not to change anything. The pom plugin only validates against a given xsd, so if an element is required by the xsd then it can hardly be considered a bug if the plugin complains.
My personal preference would be to keep the id element required by the xsd, but to document that it's actually not used anymore by the maven core (it might still be used by some plugins). WDYT?
[1] http://maven.apache.org/maven-1.x/plugins/pom/validation.html#Required_elements
Bug
Closed
Critical
Sorry but I am quite annoyed by this. Trygve mentioned on the user list that the id element was deprecated some 3 years ago, that's 2 years before I joined the Maven team. I haven't been aware that it was deprecated until this recent thread on the user list. Apparently the docs patch by Dennis at
MAVEN-1410has never been applied. When I released the last version of the pom plugin, I spent quite some time getting the validation routines to work and I compiled a table of required elements [1]. That was about half a year ago, nobody complained since, nor during vote.The main problem is that I'm not sure if some plugins don't still expect/use the id element, I'd have to check. Also, as pointed out at
MAVEN-1410, we can't just change the POM-3 xsd, as it might break some existing builds. The consensus atMAVEN-1410seems to have been to just document the deprecation, but not to change anything. The pom plugin only validates against a given xsd, so if an element is required by the xsd then it can hardly be considered a bug if the plugin complains.My personal preference would be to keep the id element required by the xsd, but to document that it's actually not used anymore by the maven core (it might still be used by some plugins). WDYT?
[1] http://maven.apache.org/maven-1.x/plugins/pom/validation.html#Required_elements
MAVEN-1410has never been applied. When I released the last version of the pom plugin, I spent quite some time getting the validation routines to work and I compiled a table of required elements [1]. That was about half a year ago, nobody complained since, nor during vote. The main problem is that I'm not sure if some plugins don't still expect/use the id element, I'd have to check. Also, as pointed out atMAVEN-1410, we can't just change the POM-3 xsd, as it might break some existing builds. The consensus atMAVEN-1410seems to have been to just document the deprecation, but not to change anything. The pom plugin only validates against a given xsd, so if an element is required by the xsd then it can hardly be considered a bug if the plugin complains. My personal preference would be to keep the id element required by the xsd, but to document that it's actually not used anymore by the maven core (it might still be used by some plugins). WDYT? [1] http://maven.apache.org/maven-1.x/plugins/pom/validation.html#Required_elements