Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes the example codes in AttributeOverrides javadoc #386

Merged
merged 1 commit into from
Oct 24, 2022

Conversation

hantsy
Copy link
Contributor

@hantsy hantsy commented Oct 22, 2022

Add missing name attribute to the example codes in AttributeOverrides javadoc.

@hantsy hantsy marked this pull request as ready for review October 22, 2022 03:13
@dmatej
Copy link
Contributor

dmatej commented Oct 24, 2022

Interesting, it was correct in AttributeOverride, but the name was missing in AttributeOverrides annotation.

@dmatej dmatej merged commit 6ec8afc into jakartaee:master Oct 24, 2022
@lukasj
Copy link
Contributor

lukasj commented Oct 31, 2022

would the one merging this mind to fix the build? See https://www.eclipse.org/lists/jpa-dev/msg00160.html for details. Thanks

@hantsy
Copy link
Contributor Author

hantsy commented Nov 1, 2022

@lukasj It seems to need to update the copyright year.

@lukasj
Copy link
Contributor

lukasj commented Nov 1, 2022

right. I'd expect either the author of this PR or the person who merged this to fix it (read as "provides the PR fixing this").

@dmatej
Copy link
Contributor

dmatej commented Nov 3, 2022

right. I'd expect either the author of this PR or the person who merged this to fix it (read as "provides the PR fixing this").

I hear you, that always happens when I believe it is a sure simple thing so I don't need to run the build locally :-D
Or better build system should verify pull requests ...
EDIT: Build system does it now.

@hantsy
Copy link
Contributor Author

hantsy commented Nov 3, 2022

@dmatej Why not consider Github actions to build the project, thus it will forbid PR to merge if there are build error in the build workflow.

@dmatej
Copy link
Contributor

dmatej commented Nov 3, 2022

@dmatej Why not consider Github actions to build the project, thus it will forbid PR to merge if there are build error in the build workflow.

It seems that it is already configured, but as you were not a committer of the project, the build did not start automatically and nothing warned me before the merge that I should have initiated the build.
For my pr it started automatically.
Next time we will do that better 🙂

@lukasj
Copy link
Contributor

lukasj commented Nov 3, 2022

the problem is in a way the gh action - the checkout part there in particular - does work. The GF copyright plugin sees all files as modified in a year at which the checkout has been done, even those unchanged by the recent commit. To avoid this false alarms, there is -Dcopyright.ignoreyear=true option in the GH action build for now. Unfortunately I haven't found a way to get around this problem (yet?).

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.

3 participants