Add 2026 to the list of valid apichanges years

[slachiewicz]

apichanges.dtd lists every allowed year value, and the list ends at 2025. Modules whose build validates apichanges.xml, such as java/maven.embedder, fail on any entry dated 2026:

[xmlvalidate] java/maven.embedder/apichanges.xml:90:51: Attribute "year" with value "2026" must have a value from the list "1998 ... 2025"

The same one-line change was made for 2018 in d2d2213.

Verified: ant -f java/maven.embedder build with a 2026 entry → BUILD FAILED on master, BUILD SUCCESSFUL with this change.

Assisted-by: Claude Opus 5.5

[mbien]

i forgot why we can't change this. But there is an updated apichanges-1.1.dtd in the same folder with more years on it.

[matthiasblaesing]

i forgot why we can't change this. But there is an updated apichanges-1.1.dtd in the same folder with more years on it.

dtds are a contract between multiple parties. Consider a code generator that builds a parser based on the grammar. When you change the list of accepted values the parser will suddenly fail at point it should not even be able to reach. You can think of a dtd as in interface the document have to implement.

The solution as rightly pointed out is to create a new revision of the DTD and use that. That way users can opt in to the change.