Kunal Dabir

Warning in Multi-Module project with gradle 5.6

6

I am getting this with gradle 5.6.1 on a multi-module project ``` The configuration :myproject:mymodule:testCompileCopy was resolved without accessing the project in a safe manner. This may happen when a...

Distribution mechanisms (package managers)

1

Can consider something like `apt-get`, `brew`, `npm` etc. - [x] Homebrew - [ ] npm - [ ] apt-get

implement timeout

3

no idea how yet, but sbt gets stuck sometimes (may be it was trying to download the internet).

Publish only released versions to Gradle Plugin Portal

2

## What happened? Currently there are just too many intermediate version published to Gradle Plugin Portal.  This creates problem with tools like dependabot, which keep raising a new PR....

this way user of library can control logging in a standard way

Try compile time meta-programming instead of runtime meta-programming. Key benefit includes IDE support and compilation failures instead of runtime failures.

Currently one test is failing on jre11, possibly because of a Groovy Bug : https://issues.apache.org/jira/browse/GROOVY-8871 gstorm.GstormDataTypesTest > initializationError FAILED java.lang.IllegalAccessError at GstormDataTypesTest.groovy:-1 73 tests completed, 1 failed Try to update...

We need to try this out, so that different groovy version is not downloaded because of transitive dependencies. Gstorm is not used in Java projects, so it is assumed some...

Remove file based versioning. Can use https://github.com/allegro/axion-release-plugin

Can considering adding SQLite DB as it is very commonly used file based db.