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

multiple server restart issue fix for maven #927

Conversation

arunvenmany-ibm
Copy link
Contributor

@arunvenmany-ibm arunvenmany-ibm commented Dec 23, 2024

adding constructor parameter with emptymap for ci.gradle

@arunvenmany-ibm
Copy link
Contributor Author

arunvenmany-ibm commented Dec 23, 2024

Application multi restart is reported in Maven, Gradle has task state check, which will not trigger recompile, unless there is any dependency change.
We are passing map as empty, to trigger the recompile logic always, and let gradle handle the dirty check

https://docs.gradle.org/current/userguide/more_about_tasks.html

@arunvenmany-ibm arunvenmany-ibm changed the title multiple server restart issue fix for maven. adding constructor para… multiple server restart issue fix for maven Jan 1, 2025
@@ -387,6 +387,7 @@ class DevTask extends AbstractFeatureTask {
true /* useBuildRecompile */, true /* gradle */, pollingTest, container, containerfile, containerBuildContext, containerRunOpts, containerBuildTimeout, skipDefaultPorts,
null /* compileOptions not needed since useBuildRecompile is true */, keepTempContainerfile, mavenCacheLocation, projectModuleList /* multi module upstream projects */,
projectModuleList.size() > 0 /* recompileDependencies as true for multi module */, packagingType, buildFile, parentBuildGradle /* parent build files */, generateFeatures, null /* compileArtifactPaths */, null /* testArtifactPaths */, webResourceDirs /* webResources */
,Collections.emptyMap() /*ignored for gradle*/
Copy link
Member

Choose a reason for hiding this comment

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

This PR would be unnecessary if you provided a constructor that did not take this new Map since it is not needed for Gradle. That constructor could then just turn around and call the other one passing an empty Map, but in ci.common instead of ci.gradle.

@arunvenmany-ibm
Copy link
Contributor Author

Closing PR after adding a new constructor in ci.common DevUtil() for ci.maven, hence common changes will not affect ci.gradle

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.

2 participants