README is confusing wrt ENV_FILE

[slhck]

The readme mentions:

If a .env.template file exists, this plugin refer it to create a environemnt variable properties in the env extension.

However, this appears not to work with the most recent version. Would it be possible to update the README to reflect the current behavior?

[uzzu]

@slhck

What's a most recent version of Gradle? Is it 8.0 or any other versions?

Please try this https://github.com/uzzu/dotenv-gradle/tree/main/examples/basic then if you have any questions, Please reopen this issue and comment. 🙏

[slhck]

No, I meant your plugin's most recent version! It does not have that feature anymore but it is still mentioned in the documentation.

[slhck]

Or maybe I was mistaken, please ignore this issue for now. It appears the template function is still part of your plugin. When I posted this issue, it didn't work for me.

[uzzu]

@slhck
Thanks for clarifying.
I recognized that README is difficult.
The pull requests for the README are welcome, so if you have any suggestions, please let me know.

[slhck]

I now know what the problem is:

The README says:

Change a file to read instead of .env file.

If environment variable ENV_FILE is set, The plugin read a file specified ENV_FILE instead of .env file.

It links to an example, but there it says:

Please use dotenv.filename in gradle.properties instead of ENV_FILE.

So it seems like ENV_FILE no longer works?

[mkatrenik]

@slhck you can override gradle property through args
./gradlew test -P dotenv.filename=.env.local

[slhck]

@mkatrenik Yes, this is what it says in the example, and what I've quoted, but I wanted to point out that the readme is confusing and needs to be updated to not mention ENV_FILE if it doesn't work.