Skip to content

Conversation

@Clashsoft
Copy link
Contributor

@Clashsoft Clashsoft commented Jan 18, 2020

Re-enables the Revapi Maven plugin.

I tried to fix the problem that it breaks when releasing a new version by explicitly setting the oldVersion it should compare against.

I believe all that needs to be done next time is update this to the version number of the newly released version. E.g., after releasing v4.4, change <oldVersion>4.3</oldVersion> to <oldVersion>4.4</oldVersion> in a new commit. The important part is the new version needs to be available on Maven by the time this commit is made.

Update: don't have to do anything any more.

@Clashsoft Clashsoft requested a review from parrt January 18, 2020 12:35
@parrt
Copy link
Member

parrt commented Jan 18, 2020

Will this happen at each release? If so, i'm opposed to its use ;)

Also added an ignore rule for ST.VERSION which obviously changes its constant value with every release, and Compiler.subtemplateCount which changed type in 4.2.
@Clashsoft
Copy link
Contributor Author

I updated the oldVersion so that it now always compares against v4.1. You no longer have to change anything after releasing!

@parrt parrt merged commit c90e4b9 into antlr:master Jan 19, 2020
@parrt parrt added this to the 4.3.1 milestone Jun 23, 2020
@Clashsoft Clashsoft deleted the revapi-fix branch June 30, 2020 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants