2.7.3

Fixed issue - #198 - mlNewProject wasn't using updated properties like mlAppName when generating scaffolding.

Skipped 2.7.2 because accidentally published this version of ml-gradle before finishing fixing 198.

2.7.1

Fixed #197 - "mlNewProject" was generating a build.gradle file with ml-gradle applied before the properties plugin.

2.7.0

Issues: https://github.com/marklogic-community/ml-gradle/issues?q=is%3Aclosed+milestone%3A2.7.0

Highlights:

• mlNewProject for quickly starting a new project - see https://github.com/marklogic-community/ml-gradle/wiki/Getting-started#using-the-new-project-wizard
• mlExportResources for exporting Manage API resources to files - see https://github.com/marklogic-community/ml-gradle/wiki/Exporting-resources
• Fixed bug with loading schemas when Gradle runs in daemon mode
• ml-app-deployer improvements: https://github.com/marklogic-community/ml-app-deployer/releases/tag/2.7.0

2.6.0

Highlights of issues resolved in this release:

• Databases with replica forests are now deleted correctly during mlUndeploy in all cases - #167
• Server-side JavaScript resources and transforms can be generated - #165 - and see https://github.com/rjrudin/ml-gradle/wiki/Common-tasks#create-a-new-resource
• Schema modules can be loaded from child directories - #160
• Schema modules can be assigned to custom collections, e.g. for redaction rulesets in ML9 - #158 - and see https://github.com/rjrudin/ml-javaclient-util/wiki/Loading-files#specifying-collections-and-permissions
• Scheduled tasks can be assigned to specific groups easily - #157
• MLCP output can be easily written to a document in MarkLogic - #151 - and see https://github.com/rjrudin/ml-gradle/wiki/Content-Pump-and-Gradle#writing-log-output-to-marklogic
• Hosts can be easily added to and removed from a cluster - #143 and #144
• And includes issues resolved in ml-app-deployer 2.6.0

2.5.0

Highlights:

1. Improved grooysh integration
2. Support for generating Entity Services artifacts (requires ML9)
3. Support for static checking while loading modules
4. Incorporates ml-app-deployer 2.5.0 and its improvements
5. Full set of issues

2.4.0

See issues at https://github.com/rjrudin/ml-gradle/issues?q=is%3Aclosed+milestone%3A2.4.0

Highlights:

• New tasks for importing/exporting qconsole workspaces
• New task for waiting for a task server to be empty
• New task for deleting a collection
• Amps can now be properly undeployed
• Scaffolding provides a more comprehensive set of roles

Also see the following issues for the dependent libraries:

• ml-app-deployer 2.4.0 - https://github.com/rjrudin/ml-app-deployer/issues?q=is%3Aclosed+milestone%3A2.4.0
• ml-javaclient-util 2.10.0 - https://github.com/rjrudin/ml-javaclient-util/issues?q=is%3Aclosed+milestone%3A2.10.0

2.3.4

No changes to ml-gradle, just depending on version 2.3.1 of ml-app-deployer, which addresses the following issues:

https://github.com/rjrudin/ml-app-deployer/issues?q=is%3Aclosed+milestone%3A2.3.1

2.3.3

Patch release that updates support for mlcp and corb2:

• #122 All mlcp arguments supported by MlcpBean can now be set as Gradle task properties
• #125 Now supports CoRB 2.3.2

2.3.2

Issues:

• #116 mlDeploy now processes all database files under ml-config/databases

2.3.1

Issues:

• #119 Finally figured out how to quiet down Jersey logging that shows up when loading modules with info-level logging on. Not a bug in ml-gradle, but worth a new release.