Skip to content

Conversation

@labkey-susanh
Copy link
Contributor

@labkey-susanh labkey-susanh commented Nov 4, 2024

Rationale

The stageModules task has been using a deprecated method for collecting the modules to be staged. This method is scheduled for removal in Gradle 9.0, so the main goal of this PR is to update that method to remove the use of said method.
I've also taken this opportunity to update more of the tasks to be compatible with the configuration cache and remove one task that is no longer very useful and not compatible with the cache.

Related Pull Requests

Changes

  • Remove checkModuleTasks tasks, added to get us through a transition from plugins being declared more centrally
  • Update stageModules to remove use of deprecated fileCollection method and make compatible with configuration cache
  • Remove StagingExtension
  • Make jsp2Java compatible with configuration cache
  • Update property in node plugin configuration for latest version
  • Mark copyExternalLibs task as not compatible with configuration cache for now
  • Update ServerSideJS task for configuration cache compatibility
  • Update DeployApp and relatives for better configuration cache compatibility
  • Update PickDb task for better configuration cache compatibility
  • Upgrade to Gradle 8.10.2

finally
{
if (writer != null)
writer.close()
Copy link
Contributor

Choose a reason for hiding this comment

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

Just curious: does Groovy have try-with-resources?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Last time I tried, it did not, but I can try again.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't really care, it just seems funny to see this pattern these days

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Seems like it is now supported. (The lag in language support is certainly one of the reasons I regret having chosen Groovy in the first place. Someday maybe we can make the switch to Java (which Gradle itself did a long time ago).)

Copy link
Contributor

Choose a reason for hiding this comment

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

I would certainly support that change! Could a Groovy --> Java migration happen incrementally? Or is it all or nothing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Pretty sure it's all or nothing, but I've not tried. IntelliJ offers an option to do the work for us, but not sure how well this works. Still, it's very tempting.

Screenshot 2024-11-04 at 10 03 45 AM

@labkey-susanh labkey-susanh merged commit d589113 into develop Nov 5, 2024
@labkey-susanh labkey-susanh deleted the fb_configCache2 branch November 5, 2024 18:57
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