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

JBTM-3273 -> Implemented code review comments #1600

Merged
merged 1 commit into from
Apr 17, 2020

Conversation

mayankkunwar
Copy link
Contributor

@mayankkunwar mayankkunwar commented Apr 16, 2020

This PR is to implement missed code review comments on another PR.

MAIN QA_JTA AS_TESTS

!TOMCAT !RTS !JACOCO !XTS !QA_JTS_JACORB !QA_JTS_JDKORB !QA_JTS_OPENJDKORB !BLACKTIE !PERF !LRA !NO_WIN !DB_TESTS !mysql !db2 !postgres !oracle

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

import com.arjuna.ats.jta.recovery.XAResourceOrphanFilter;
import com.arjuna.ats.jta.recovery.XAResourceRecovery;
import com.arjuna.ats.jta.recovery.XAResourceRecoveryHelper;
import com.arjuna.ats.jta.recovery.*;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can avoid the new RecoveryRequired class and just add an AtomicBoolean to this class instead.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a checkstyle plugin which is skipped by default because we have a lot of old files, that we don't want to change, which would fail the compilation. But on new code we do encourage/advise that it should follow our checkstyle rules.

To see if your code follows our style guide you have two options:

  1. Enable the checkstyle plugin via the pom file, or

  2. Reference the rule file from your IDE settings (for Intelij that would be Settings -> Other Settings -> Checkstyle) and we use the wildfly rule set.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can avoid the new RecoveryRequired class and just add an AtomicBoolean to this class instead.

Okay, I will remove the new RecoveryRequired class and add AtomicBoolean

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a checkstyle plugin which is skipped by default because we have a lot of old files, that we don't want to change, which would fail the compilation. But on new code we do encourage/advise that it should follow our checkstyle rules.

To see if your code follows our style guide you have two options:

  1. Enable the checkstyle plugin via the pom file, or
  2. Reference the rule file from your IDE settings (for Intelij that would be Settings -> Other Settings -> Checkstyle) and we use the wildfly rule set.

Maybe checkstyle changes can be done on separate PR?

Copy link
Contributor

@mmusgrov mmusgrov Apr 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The checkstyle issue I commented on was introduced as part of this PR so a separate PR would not make sense.

I admit that having to manually run the checkstyle plugin is not optimal. But I do not see an alternative to the reason I gave:

We have a checkstyle plugin which is skipped by default because we have a lot of old files, that we don't want to change, which would fail the compilation. But on new code we do encourage/advise that it should follow our checkstyle rules.

@ochaloup We have had this problem of skipping the checkstyle plugin on two PRs this week, it mainly affects new/occasional contributors. Do you have any thoughts on how we could improve it (other than fixing all of the historical code).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that your latest push has fixed the checkstyle problem I reported.
But I will not mark the conversation as resolved yet since I have an outstanding question for Ondra.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for not reacting this sooner I wanted but I haven't got to this. I can see the discussion was moved to chat. I replied there.

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

Copy link
Contributor

@ochaloup ochaloup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have few points about exposing the functionality (aka. opening the API) to the outer world. I'm not sure if it's really needed. Let me know your thoughts.

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

Copy link
Contributor

@ochaloup ochaloup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mayankkunwar! This seems good to me.
@mmusgrov would you have some more points on this or it could be considered as ready for merge?

@mmusgrov
Copy link
Contributor

Thanks @mayankkunwar! This seems good to me.
@mmusgrov would you have some more points on this or it could be considered as ready for merge?

I had a couple comments for Mayank. And there was one for you about our checkstyle plugin.

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@mmusgrov
Copy link
Contributor

Looks good. @ochaloup I will merge this one.

@mmusgrov mmusgrov merged commit cf8e1ab into jbosstm:master Apr 17, 2020
@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

@jbosstm-bot
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants