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

[ISSUE 92] Centralized rules repository #178

Conversation

jycr
Copy link
Contributor

@jycr jycr commented Apr 14, 2023

Implements #92

@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from 4addb30 to ca999ad Compare April 14, 2023 17:50
@sonarcloud
Copy link

sonarcloud bot commented Apr 14, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 35 Code Smells

61.5% 61.5% Coverage
17.4% 17.4% Duplication

@dedece35 dedece35 added 🚀 enhancement New feature or request 🏗️ refactoring refactoring for best practices __PRIO_LOW__ labels May 9, 2023
@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from ca999ad to f4264fb Compare June 9, 2023 10:09
@jycr jycr force-pushed the feature/92--centralized-rules-repository branch 10 times, most recently from 9190b11 to af26f6c Compare June 16, 2023 00:35
ecocode-rules-specifications/pom.xml Show resolved Hide resolved
ecocode-rules-specifications/pom.xml Outdated Show resolved Hide resolved
ecocode-rules-specifications/pom.xml Show resolved Hide resolved
ecocode-rules-specifications/pom.xml Show resolved Hide resolved
java-plugin/pom.xml Show resolved Hide resolved
python-plugin/pom.xml Outdated Show resolved Hide resolved
python-plugin/pom.xml Show resolved Hide resolved
python-plugin/pom.xml Show resolved Hide resolved
python-plugin/pom.xml Outdated Show resolved Hide resolved
python-plugin/pom.xml Show resolved Hide resolved
@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from af26f6c to 36268bf Compare June 20, 2023 00:38
Copy link
Contributor Author

@jycr jycr left a comment

Choose a reason for hiding this comment

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

I fixed/answered all of @dedece35 's feedbacks

@jycr jycr requested a review from dedece35 June 20, 2023 00:42
@dedece35
Copy link
Member

dedece35 commented Jun 23, 2023

@jycr, as mentioned during friday meeting, please wait #188 (just done) and #201 before merging this one

Copy link
Member

@dedece35 dedece35 left a comment

Choose a reason for hiding this comment

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

review OK now.
but after merging main branch on your branch (after #187 and #201 ), I would like to test myself and check if I see some problems on my local machine, please.
tell me when merges are ok on your branch.

@dedece35
Copy link
Member

@jycr
2 waiting PRs has just been merged (#187 and #201)
you can now get main code on your branch
I can help you if you have problems on conflicts.

@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from 36268bf to dbf04ab Compare June 27, 2023 13:51
@jycr jycr requested a review from utarwyn June 27, 2023 14:01
@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from dbf04ab to e71038c Compare June 28, 2023 22:38
Copy link
Member

@dedece35 dedece35 left a comment

Choose a reason for hiding this comment

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

Hi @jycr
first quick review : first of all, please correct 21 code smells

@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from e71038c to e988c1a Compare June 29, 2023 16:52
@jycr jycr requested a review from dedece35 June 29, 2023 16:53
@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from e988c1a to 93d476b Compare July 3, 2023 22:56
@jycr jycr requested a review from dedece35 July 3, 2023 22:57
@jycr jycr requested a review from utarwyn July 5, 2023 22:44
utarwyn
utarwyn previously approved these changes Jul 6, 2023
Copy link
Member

@utarwyn utarwyn left a comment

Choose a reason for hiding this comment

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

LGTM in my opinion 💯
Maybe wait for another validation before merging to be sure?

@jycr jycr force-pushed the feature/92--centralized-rules-repository branch from c39832d to 7d3683b Compare July 9, 2023 22:23
@sonarcloud
Copy link

sonarcloud bot commented Jul 9, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@dedece35
Copy link
Member

Hi @jycr,
last check in my local machine before merging :p

my tests are ok and now ok for merge.
I've just done it by myself but several things to correct in main branch please :

  • when I launch tool_build.sh there are several WARNINGs that we did'nt have before in main branch
    • each plugin build generates a WARNING regarding shade plugin : see maven-shade-plugin has detected that some files are ... warning message
    • asciidoctor plugin generates several warning with message starting with [WARNING] Duplicated destination found: overwriting file: ...
  • did you write a process to publish a new version of ecocode-rules-specifications module into maven central ? as I understand, in the near future, there will be only the content of ecocode-rules-specifications module in ecocode repository. But for now, there is also other languages, thus we have to publish this module differently than the final way, isn't it ?

@dedece35 dedece35 merged commit cb9ba96 into green-code-initiative:main Jul 10, 2023
3 checks passed
@jycr
Copy link
Contributor Author

jycr commented Jul 10, 2023

Hi @jycr, last check in my local machine before merging :p

my tests are ok and now ok for merge. I've just done it by myself but several things to correct in main branch please :

  • when I launch tool_build.sh there are several WARNINGs that we did'nt have before in main branch

    • each plugin build generates a WARNING regarding shade plugin : see maven-shade-plugin has detected that some files are ... warning message
    • asciidoctor plugin generates several warning with message starting with [WARNING] Duplicated destination found: overwriting file: ...
  • did you write a process to publish a new version of ecocode-rules-specifications module into maven central ? as I understand, in the near future, there will be only the content of ecocode-rules-specifications module in ecocode repository. But for now, there is also other languages, thus we have to publish this module differently than the final way, isn't it ?

I will check those points on my local to find fixes and propose a new PR.

Regarding publishing in Maven central, I will check that point in few days

@jycr jycr deleted the feature/92--centralized-rules-repository branch July 21, 2023 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏗️ refactoring refactoring for best practices 🚀 enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants