-
-
Notifications
You must be signed in to change notification settings - Fork 489
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
release module build workflow improvements / fixes #7619
release module build workflow improvements / fixes #7619
Conversation
Signed-off-by: Jody Garnett <[email protected]>
… modules) are compiled and tested during QA Signed-off-by: Jody Garnett <[email protected]>
…and handling of jetty folder Signed-off-by: Jody Garnett <[email protected]>
e6eec09
to
9496579
Compare
Why are you removing /web/src/main/webapp/doc/api? It is required by swagger pages? |
Sigh - yep managing generated content in a live src folder caught me out again (I am going to have to clean that up one of these days). I will fix, thanks for the review. |
72f244c
to
3523aa9
Compare
Signed-off-by: Jody Garnett <[email protected]>
3523aa9
to
1412915
Compare
@josegar74 the build changes required for stable module order are starting to overlap with other pull-requests. Please accept this change (needed for automated builds to include release profile) which should keep things stable. aside: We should plan to sit down and figure out what is where when so I do not repeat the same work in multiple PRs. |
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.
Tested. LGTM.
* schemas now uses `SNAPSHOTS`, no longer to manage schemas `3.8` explicitly. * Remember to include `-Drelease` flag so that all modules (even optional modules) are compiled and tested during QA. * Troubleshoot release module order of execution and profile activation and handling of jetty folder. * Web profile with-doc profile needs dependency to build docs first. --------- Signed-off-by: Jody Garnett <[email protected]>
@jodygarnett I've backported this to https://github.com/geonetwork/core-geonetwork/actions/runs/7540881617/job/20526403544 |
@juanluisrp I a confused about procedure / policy here. The instructions say to do commits with a single purpose clearly described, which makes back porting easier.
What is a good approach to get main / 4.2.x / 3.12.x on the same page? |
AFAIK we squash and merge into |
The CONTIRBUTING guide has:
I guess I should have specified what was needed :) |
-Drelease
flag so that optional modules are compiled and verified during QAChecklist
main
branch, backports managed with labelREADME.md
filespom.xml
dependency management. Update build documentation with intended library use and library tutorials or documentationFunded by GeoCat BV by way of GeoNetwork Enterprise product (thank you customers!)