Skip to content

Commit

Permalink
Release v0.4.0
Browse files Browse the repository at this point in the history
  • Loading branch information
Clashsoft committed Apr 17, 2020
1 parent 4a89699 commit 0a25476
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 1 deletion.
17 changes: 17 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,3 +17,20 @@

+ Added the `ScenariosTask.copyTo` methods that allow converting them to debuggable `JavaExec` tasks.
* The plugin is now implemented with Java instead of Groovy.

# Fulib Gradle v0.4.0

## New Features

+ The plugin now creates the `gen` and `testGen` source sets.
+ Added support for Decorators with the `--decorator-classes` fulibScenarios compiler option. #7
> It is not required to set the option manually.
> The decorator classes are automatically determined from the source files in the `gen` and `testGen` source sets.
+ Added support for the `--tables` and `--dry-run` options of the fulibScenarios compiler. #8

## Known Issues

- The `generateScenarioSource` task fails if the `src/main/scenarios` directory does not exist.
W/A: Create the directory (it can be empty).
- The `generateTestScenarioSource` task fails if the `src/test/scenarios` directory does not exist.
W/A: Create the directory (it can be empty).
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,16 @@ and can be installed via the `plugins` DSL in `build.gradle`:
plugins {
// ...
id 'java'
id 'org.fulib.fulibGradle' version '0.3.0'
id 'org.fulib.fulibGradle' version '0.4.0'
// ...
}
```

See the [Fulib Scenarios README](https://github.com/fujaba/fulibScenarios/blob/master/README.md)
for instructions on how to use the tool.

> ⚠︎ In v0.4.0, there is a known issue that causes the build to fail
> if the `src/main/scenarios` and `src/test/scenarios` directories do not exist.
> The workaround is to create these directories.
> You can leave them empty, but it is advisable to create an empty `.gitkeep` file within them.
> This also avoids build failures on CI/CD systems like Travis CI.

0 comments on commit 0a25476

Please sign in to comment.