That's my understanding of its intent. If it's not updated when a
new version of the API is released, it just becomes another form of
@since.
Scott Stark wrote on 7/18/19 1:00 PM:
Can’t this just be generated then? Your saying this needs to match
the pom.xml version?
@version is
supposed to be the current version of the API, so it needs
to be updated for each release, and thus should have the
new API name. (If you don't update it, it degenerates to
being the same as @since.)
Richard Monson-Haefel wrote
on 7/18/19 8:45 AM:
Hi Scott,
this line tripped me up "
- Leave
existing "@since XYZ 1.x" uses alone. These refer
to the old JCP version. Future additions should
use the Jakarta project name.
Can you add another line about leaving the @version
the same as well? That's where I went wrong.
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
|
