Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conditioanlly create and explode war #15

Closed
kdabir opened this issue Jul 29, 2014 · 1 comment
Closed

conditioanlly create and explode war #15

kdabir opened this issue Jul 29, 2014 · 1 comment
Labels

Comments

@kdabir
Copy link
Owner

kdabir commented Jul 29, 2014

Currently every invocation of glide creates and exploded war in the same app dir. This is redundant. This is required only when dependencies have changed of the outputApp does not exists.

We can conditionally skip the execution of tasks.

war {
    setOnlyIf {
    }
}
@kdabir kdabir added the plugin label Apr 8, 2016
@kdabir
Copy link
Owner Author

kdabir commented Aug 5, 2016

If nothing is changed in source code, up-to-date check saves the hassle. We can verify by checking for UP-TO-DATE.

....
:war UP-TO-DATE
:appengineExplodeApp UP-TO-DATE
...

However this may change when the glide's sync and appengineRun reuse the same directory as the content of directory might have been changed after the war was exploded. Which is fair.

Currently, if warDir config is set on appengine this can be skipped. we need some other tasks to assemble war contents in warDir.

Closing for now. If that turns out to be big deal, can reopen.

@kdabir kdabir closed this as completed Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant