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

NO_ISSUE: Copying resources directly to target instead to src/main/resources to keep module sources clean. #3691

Merged
merged 4 commits into from
Oct 4, 2024

Conversation

pefernan
Copy link
Contributor

@pefernan pefernan commented Oct 2, 2024

This has been a bad config we've been spreading around for some time, with this change we copy static resources directly to target, so they'll be bundled in the .jar but keeping the sources clean.

Ensemble:
#3691
apache/incubator-kie-kogito-apps#2106

Many thanks for submitting your Pull Request ❤️!

Closes/Fixes/Resolves #ISSUE-NUMBER

Description:

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to this configuration
  • Pull Request title is properly formatted: Issue-XYZ Subject
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Issue-XYZ Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

@pefernan pefernan force-pushed the no_issue_copy_resources_cleanup branch from a80dba2 to 27724bb Compare October 2, 2024 20:14
@pefernan pefernan changed the title NO_ISSUE: Copying resources directly to target instead to src/main/resources to keep module sources clean. [WIP] NO_ISSUE: Copying resources directly to target instead to src/main/resources to keep module sources clean. Oct 2, 2024
@@ -73,7 +73,7 @@ public class DecisionCodegen extends AbstractGenerator {
public static final String GENERATOR_NAME = "decisions";

/**
* (boolean) generate java classes to support strongly typed input (default false)
* (boolean) generate java classes to support strongly typed input (default false)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@gitgabrio looks like one of your Pr's introduced this and was breaking the build :S

@gitgabrio
Copy link
Contributor

gitgabrio commented Oct 3, 2024

@pefernan
Thanks for the PR, I really appreciate.
Here and in the other one I found minor details to be fixed, IINW.

@pefernan pefernan force-pushed the no_issue_copy_resources_cleanup branch from 016188f to 6a063d4 Compare October 3, 2024 11:31
Copy link
Contributor

@elguardian elguardian left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@gitgabrio gitgabrio left a comment

Choose a reason for hiding this comment

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

Thanks @pefernan - LGTM

@pefernan pefernan changed the title [WIP] NO_ISSUE: Copying resources directly to target instead to src/main/resources to keep module sources clean. NO_ISSUE: Copying resources directly to target instead to src/main/resources to keep module sources clean. Oct 4, 2024
@pefernan pefernan merged commit e7d1be4 into apache:main Oct 4, 2024
6 checks passed
@pefernan pefernan deleted the no_issue_copy_resources_cleanup branch October 4, 2024 13:56
@pefernan pefernan restored the no_issue_copy_resources_cleanup branch October 7, 2024 07:42
@pefernan pefernan deleted the no_issue_copy_resources_cleanup branch October 7, 2024 07:42
rgdoliveira pushed a commit to rgdoliveira/kogito-runtimes that referenced this pull request Oct 10, 2024
…/resources` to keep module sources clean. (apache#3691)

* NO_ISSUE: Copying resources directly to `target` instead to `src/main/resources` to keep module sources clean.

* - fix formatting

* - renamed path variables

* - format
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.

4 participants