Skip to content

Conversation

@ctubbsii
Copy link
Member

@ctubbsii ctubbsii commented Nov 3, 2020

No description provided.

@ctubbsii ctubbsii added enhancement This issue describes a new feature, improvement, or optimization. build labels Nov 3, 2020
@ctubbsii ctubbsii self-assigned this Nov 3, 2020
@ctubbsii
Copy link
Member Author

ctubbsii commented Nov 3, 2020

I was hoping to get this pushed before @keith-turner pushed 0168e8f to see if I could get it to fail the build, but I didn't make it in time. I'm confident this works, though, because I can simulate it locally.

@ctubbsii ctubbsii merged commit de7b42f into apache:main Nov 3, 2020
@ctubbsii ctubbsii deleted the validate-formatting-in-ci branch November 3, 2020 23:58
@keith-turner
Copy link
Contributor

So if someone submits a PR that requires formatting changes, then it should now fail CI? If so thats kinda awesome.

@ctubbsii
Copy link
Member Author

ctubbsii commented Nov 6, 2020

So if someone submits a PR that requires formatting changes, then it should now fail CI? If so thats kinda awesome.

Yep. 😺

asfgit pushed a commit that referenced this pull request Nov 6, 2020
Minor fixup of #1767

* Remove redundant execution of sortpom verification that existed before
  the verifyformat profile was created in PR #1767 and keep the original
  execution phase and execution ID
* Deconflict execution IDs for other plugins in the verifyformat
  profile, so plugin execution definitions don't clobber each other if
  both verifyformat and autoformat profiles are active
asfgit pushed a commit that referenced this pull request Nov 26, 2020
* Show rat output in console (partial backport to 1.x from #1767)
* Don't skip enforcer when skipQA profile is active, because it is
  necessary for enforcing build requirements (and isn't costly to run)
* Enforce the JDK version to less than 15 for Accumulo 1.x, because
  Concurrent Mark and Sweep garbage collector options were removed from
  JDK 15, which Accumulo 1.x uses in its scripts and in Mini. While
  Accumulo 1.x can still compile and build in JDK 15, it will not be
  able to run as-is, including running tests, resulting in hard-to-track
  and confusing errors for developers. It is easier to enforce the JDK
  version to being at least 11, and strictly less than 15, during
  development.
@ctubbsii ctubbsii added this to the 2.1.0 milestone Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build enhancement This issue describes a new feature, improvement, or optimization.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants