[etlas] Support WAR file generation

[rahulmutt]

1. The special resources directory should be recognised by etlas and it should package them up into a JAR for static resources WEB-INF, META-INF, *.html, *.css files.
2. When building a project, all the dependency jars should be copied into the lib/ folder of the WAR file.

etlas configure --generate-war

[jneira]

Good one! it will do web app devlopment with eta more agile and comfortable.
To have a reference, other build tools in jvm ecosystem usually do:

• put the compiled code and other resources that have to be in the classpath (config files f.e.) in WEB-INF\classes without packaging it
  • maybe etlas could handle it as a dependency
• by default they copy the app dependencies int WEB-INF\lib
  • although you usually can avoid it with a option: --no-jars or alike
  • it's common in some envs to handle dependencies (part of all of them) outside the app, at server level
• copy the content of resources (maybe configurable in cabal file) in the root of the war package
  • i suppose web.xml would be in that dir
• they can create the flat war structure in dist to let the user config the server to use that location directly to serve the app, instead of have to make the war in each compile step

[Jyothsnasrinivas]

This can be easily done with the Gradle plugin. @jneira Do you still think it's a good idea to keep it inside of etlas?

[jneira]

@Jyothsnasrinivas yeah, gradle seems to be the correct tool for this

[Jyothsnasrinivas]

@jneira In that case I'm closing this issue.