-
Notifications
You must be signed in to change notification settings - Fork 210
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
NO_ISSUE: Copying resources directly to target
instead to src/main/resources
to keep module sources clean.
#3691
Conversation
a80dba2
to
27724bb
Compare
target
instead to src/main/resources
to keep module sources clean.target
instead to src/main/resources
to keep module sources clean.
@@ -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) |
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.
@gitgabrio looks like one of your Pr's introduced this and was breaking the build :S
@pefernan |
…/resources` to keep module sources clean.
016188f
to
6a063d4
Compare
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.
LGTM
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.
Thanks @pefernan - LGTM
target
instead to src/main/resources
to keep module sources clean.target
instead to src/main/resources
to keep module sources clean.
…/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
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:
Issue-XYZ Subject
[0.9.x] Issue-XYZ Subject
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.