Implement custom tasks about gretty

[akhikhl]

Custom tasks implemented on branch "grettyTasks", not merged to master yet, not documented.

[akhikhl]

Custom tasks merged to master, documented in wiki pages.

[akhikhl]

Gretty task classes were substantially reworked, now they should be much more useful. See documentation: https://github.com/akhikhl/gretty/wiki/Gretty-task-classes

There is one new feature that you might like: afterEvaluate handlers for gretty and farm extensions.
Syntax:

gretty {
  afterEvaluate {
    tasks.jettyRun.with {
      port = ...
      dependsOn ...
    }
  }
}

afterEvaluate handler is executed in afterEvaluate handler of gretty-plugin, right after initialization of all tasks. This is the right place for altering gretty tasks.

Note that you don't need afterEvaluate handler for creating your own tasks, so the following would work just fine:

gretty {
}

import org.akhikhl.gretty.JettyStartTask

task('MyJettyRun', JettyStartTask) {
  interactive = true
  port = 7070
}

[bgaborg]

In my project, I've used
buildscript dependency: classpath 'org.akhikhl.gretty:gretty-plugin:+'

apply from: 'https://raw.githubusercontent.com/akhikhl/gretty/master/pluginScripts/gretty9-0.0.19.plugin'
// global settings
gretty {
    port = 8080
    scanInterval = 1
    scanDir 'src/main/webapp'
    onScanFilesChanged { fileList -> println "Files were changed: $fileList" }
    fastReload = true
    consoleLogEnabled = true
    fileLogEnabled = true
    logFileName = project.name
    logDir = "${System.getProperty('user.home')}/logs"
}

After this recent change, the initial build fails with this:

FAILURE: Build failed with an exception.
* Where:
Script 'https://raw.github.com/akhikhl/gretty/master/pluginScripts/gretty9.plugin'
* What went wrong:
A problem occurred evaluating script.
> org.akhikhl.gretty9.GrettyPlugin

After changing to

apply from: 'https://raw.githubusercontent.com/akhikhl/gretty/master/pluginScripts/gretty9-0.0.19.plugin'

the build script the with jettyRun fails with this:

Exception in thread "Thread-14" groovy.lang.MissingPropertyException: No such property: absolutePath for class: java.lang.String

Full stacktrace and log at:
http://pastebin.com/kuspgtNm

Please help :)

[bgaborg]

The error:
Exception in thread "Thread-9" groovy.lang.MissingPropertyException: No such property: absolutePath for class: java.lang.String
is thrown even with the simplest settings.

[akhikhl]

First problem (gretty9.plugin)

yes, it was an error in class file naming in gretty9.plugin. Now fixed, so it should work right away, without version upgrade. Attention: although github shows new formatted verson of file, when it still returns old raw version of file. I don't know the reason for this problem, may only guess that github aggressively caches files (or maybe it's their bug?).
Edit: now raw version is also up-to-date, so you can use gretty9.plugin right away.

[akhikhl]

Second problem (logback condig absolutePath)

It's a bug in Gretty. It appears only if "logback.xml" or "logback.groovy" file is found in folders projectDir, webAppDir/WEB-INF or in output (like buildDir/classes/main, buildDir/resources/main).
As soon as you remove (or rename) the file, the problem disappears. I know, this is bad workaround, but you can solve it that way for now.
I'll try to fix it ASAP and publish fixed version.

[akhikhl]

Please, don't hesitate opening new issues 😉