-
Notifications
You must be signed in to change notification settings - Fork 30
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
application.properties
should be optional
#20
Comments
The fact that application crashes, means this file is used. I really don't get your point, why it doesn't makes sense? This file specifies which Grain version should be used to generate static website. Do you want to specify Grain version in build.gradle, instead? Is this your point? |
I looked through the code. It only checks if then file exist and then does nothing. It makes sense if one uses Grain as a static generator with pre-built theme. Since the number of such themes is very low, in my opinion the greatest advantage of Grain is its flexibility and ability to embed. In this case it makes much more sense to define grain version in gradle build or in |
@altavir |
does grainw work faster than gradle daemon? If not, it is possible that you should drop it. I don't use it so Idon't know. |
I need to take a look at latest Gradle versions, that come with Gradle daemon, if they work reasonably fast, then grainw can be dropped. |
@altavir Alexander, don't you want to fix this issue yourself and submit Pull Request? I think Gradle with daemon will be almost as fast as |
I am definitely interested because I think that Grain is a very promising way to handle static site generation in a very flexible way (flexibility is a key word). I am currently maintaining two sites made with Grain. |
Currently, application crashes if this file does not exist, but it is not really used. This file does not make sense for embedded site.
The text was updated successfully, but these errors were encountered: