-
-
Notifications
You must be signed in to change notification settings - Fork 78
rename ALL CAPS method name to camelCase #124
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
Conversation
keilw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I recall this was a rather static and constant instance, therefore the uppercase. @freeman0432 Are you a JCP member already? Especially for the API we can only merge PRs by JCP members.
|
Sorry, I am not JCP member. @keilw ,I didn't expect to bother you. |
|
@freeman0432 Sorry to hear, you could join as Associate Member if you like, it is not hard to join and every membership (even for companies) is free, see https://jcp.org/en/participation/membership. |
|
@keilw if the project have such limitation then it should be noted in CONTRIBUTE.md file |
|
@stokito This is more or less common knowledge by all JSRs. As Jakarta EE with the former Java EE JSRs moves a large portion away, there are fewer "traditional" JSRs but e.g. https://github.com/jsr107/jsr107spec also does not have a HOWTO. We could create such document for a new release, right now the MR has other priorities. |
It is |
|
We also made exceptions where a method represents a constant value e.g. |
|
Then let's close this one, @marschall or @stokito both of you are JCP members already, would you be able to propose another PR that fixes #90 completely? |
|
@marschall Thanks, will check it out soon. Is there a behavioral change the BP might also need? The internals like uppercase I would not call so tragic there, but if it changes anything, that should also be backported. |
|
There is no behavioral change. These are private methods and do not impact any user. There might be slightly less |
|
Ok thanks, then it may be less relevant to backport them. |
|
@keilw, thank you for your advice. I have joined the JCP |
|
@freeman0432 Thanks a lot, we'll ask the PMO to add contributors who helped with the JSR until the MR1, if you want and your name is already listed in https://jcp.org/en/participation/members/ (it usually takes a bit after you submitted everything) we could also ask to add contributors. Otherwise everyone is welcom to join a follow-up JSR where contributors can also self-nominate (right now in Maintenance phase this is only possible by asking the PMO) |
|
@keilw, excuse me! I have submitted my profile for a few days. But the note is "Profile information in JCP DB is updated after JCP PMO review." What should I do? |
|
They will take a bit of time, no worries. Especially in Summer |
|
@keilw, thanks a lot. |
|
@keilw Help me.I send email to admin@jcp.org, no one reply me. |
|
They seem to be on vacation, we submitted everything to finalize JSR 385 a little over a week ago and there was also no response. Plus Oracle does its house conference in less than a month, so probably not much activity before then ;-/ |
|
It turned out to be the case, thank you very much. Then I will wait for their holiday to end. |
|
@keilw |
|
The PR is closed and has been done (the relevant parts) by others like @thodorisbais I believe. |
|
If it hasn't could you forward the mail from PMO to werner@javamoney.org please? |
|
Sorry, my expression is a bit problematic. I mean, can I submit a new RP the next time I contribute code? |
|
Yes, if they have you in their system, it should be OK. |
fixes #90
This change is