-
Notifications
You must be signed in to change notification settings - Fork 150
[OPENJPA-2748] commons-collection is updated to most recent version #20
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
|
Thx @solomax - this PR looks good to me.
To me, you can add that here. @struberg / @rmannibucau would you please doublecheck? |
rmannibucau
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.
Looks ok to me (even adding a commit)
Side note: can be good to remove style/@OverRide changes since they are unrelated and take most of the diff
|
@rmannibucau I have this setting on by default in my IDE due to I had extremely bad experience of project migration without @OverRide being set. |
|
@solomax if possible it would be awesome to have this PR about commons-collection upgrade only and then if you want add override everywhere |
|
sure, will do |
|
Hopefully this diff will be easier to read :) |
|
Ok, I am going to merge this PR right now - but please don't forget to submit another for |
|
@ilgrosso this will break the build ... most probably |
|
@solomax let me check.. |
|
I'm afraid there no auto build :( Will send additional email regarding SNAPSHOT |
|
@solomax could you please rebase? |
|
@ilgrosso could you please guide me with rebase? |
|
I wrote another email regarding |
I mean something like as https://robots.thoughtbot.com/keeping-a-github-fork-updated |
617ebf5 to
58a397a
Compare
|
Just have tried to rebase but no luck :( |
yep, you should rebasing against |
58a397a to
30eaad0
Compare
|
OK, the trick was to use |
This could be fixed too, but it is not really a big issue since we are with SVN. |
|
Great :) |
|
ah, it seems you can merge this PR by yourself, when the commons-collection4 artifacts will be available ;-) |
|
Sure, will do :) |
I don't see any issue with that. |
|
Great, so will do the merge as soon as SNAPSHOT will be available |
|
Merged with 4709f38 |
Additionally I would like to remove
ReferenceMap.HARD, SOFT, WEAKin favor ofReferenceStrength.HARD, SOFT, WEAKshall I add another commit to this PR, or create another one?
this fix depends on commons-collections4 4.3-SNAPSHOT, will compile as soon as 4.3 will be released or SNAPSHOT will be uploaded