Issue #13796: clarify AnnotationLocation same-line annotation precedence#18388
Conversation
127df61 to
683c4da
Compare
|
Hey @dhruv-38 , |
|
@vivek-0509 I have added to the Javadoc and then run the mvn clean site -Pno-validations but it does not change or generate the annotationlocation.xml |
run mvn clean verify after adding it in the AnnotationLocationCheck i tried it locally it will work. |
|
@dhruv-38 add this para to the class level javadoc around line 72 not to the field javadoc then run mvn clean verify , then check git status it will show three files changed , commit your changes and push after clean build. |
|
Please read and watch videos at Starting_Development. |
327ad4b to
f947c08
Compare
|
Now all the CI is green. Do i need to do any thing else? |
|
@dhruv-38 , please use commit prefix as |
|
GitHub, generate website |
|
all other is good. |
f947c08 to
252bb26
Compare
252bb26 to
55ea01c
Compare
|
@dhruv-38 , single commit please |
|
ok, should i create a new pr? |
|
@dhruv-38 You can refer to the following documentation for instructions on how to rebase: |
|
Please read and watch videos at Starting_Development. |
55ea01c to
c244605
Compare
|
@romani |
|
@vivek-0509 why its failing again? |
not related to your changes , just need to run the CI again. |

Fixes #13796
This PR clarifies the AnnotationLocation documentation by explaining that
allowSamelineMultipleAnnotations has a dominant effect over other same line
annotation properties.
Documentation only change. No logic changes.