You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Capsule project contains two build descriptors, one for Maven and one for Gradle. The former is out of sync and, e.g., does not cover recent features (cf. #35). In order to avoid feature disparity and the two descriptors getting out of sync, I suggest removing the Maven build descriptors in favor of Gradle.
Steps for sunsetting the Maven build descriptor:
Update GitHub Actions to use Gradle (i.e., test pipelines and release workflow)
Hi Michael; all of our builds are done with maven. We don't have any Gradle experience or expertise in the team. And we manage a number of our own maven plugins. So I would hesitate to switch to only Gradle. Could we do it the other way around?
The Capsule project contains two build descriptors, one for Maven and one for Gradle. The former is out of sync and, e.g., does not cover recent features (cf. #35). In order to avoid feature disparity and the two descriptors getting out of sync, I suggest removing the Maven build descriptors in favor of Gradle.
Steps for sunsetting the Maven build descriptor:
com.mycila:license-maven-plugin
The text was updated successfully, but these errors were encountered: