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

optimize: build the frontend at the same time as the maven build #6246

Merged
merged 5 commits into from
Jan 17, 2024

Conversation

liuqiufeng
Copy link
Contributor

  • I have registered the PR changes.

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

@codecov-commenter
Copy link

codecov-commenter commented Jan 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a59a39a) 51.05% compared to head (8d6676b) 51.08%.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##                2.x    #6246      +/-   ##
============================================
+ Coverage     51.05%   51.08%   +0.03%     
- Complexity     5093     5098       +5     
============================================
  Files           918      918              
  Lines         32031    32031              
  Branches       3865     3865              
============================================
+ Hits          16353    16363      +10     
+ Misses        14101    14095       -6     
+ Partials       1577     1573       -4     

see 5 files with indirect coverage changes

@slievrly slievrly self-requested a review January 7, 2024 14:46
.gitignore Show resolved Hide resolved
console/pom.xml Outdated Show resolved Hide resolved
Copy link
Member

@slievrly slievrly left a comment

Choose a reason for hiding this comment

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

Need to consider the independent deployment of console.

@liuqiufeng
Copy link
Contributor Author

Need to consider the independent deployment of console.

None of these changes affect the separate packaging of the console front-end

slievrly
slievrly previously approved these changes Jan 16, 2024
Copy link
Member

@slievrly slievrly left a comment

Choose a reason for hiding this comment

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

LGTM

@slievrly slievrly changed the title optimize: Build the frontend at the same time as the maven build optimize: build the frontend at the same time as the maven build Jan 16, 2024
<configuration>
<workingDirectory>src/main/resources/static/console-fe</workingDirectory>
</configuration>
<executions>
Copy link
Member

Choose a reason for hiding this comment

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

any phase here ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

any phase here ?

Added phase here.

# Conflicts:
#	changes/en-us/2.x.md
#	changes/zh-cn/2.x.md
@@ -166,6 +169,7 @@
<goals>
<goal>npm</goal>
</goals>
<phase>generate-resources</phase>
Copy link
Member

Choose a reason for hiding this comment

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

it is unreasonable to set it in the generate-resources phase.

Copy link
Member

Choose a reason for hiding this comment

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

Considering online IDE debugging, maintain the status quo.

Copy link
Member

@slievrly slievrly left a comment

Choose a reason for hiding this comment

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

LGTM

@slievrly slievrly merged commit 3351fcf into apache:2.x Jan 17, 2024
6 checks passed
@liuqiufeng liuqiufeng deleted the 2.x_build_frontend branch January 24, 2024 03:42
@slievrly slievrly added this to the 2.1.0 milestone Feb 16, 2024
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