Add a 'development mode' behavior to jsp tag

[davideanderson]

Be able to have the jsp tag act differently in a development environment rather than a production environment. Uploading all the assets to s3 makes sense for production, but if I am in the middle of development, and am making a lot of css and js changes, I don't want to have to upload the files for every change.

This can be handled within the jsp tag. Rather than always translating the original file to an uploaded url, if in development mode, local urls should used for the resources.

[aro1976]

There are at least 2 options already available to achieve what you're looking for:
a) run your application using jetty:run or tomcat:run, this way the plugin does not upload to S3 bucket neither creates the manifest file, when this file doesn't exist at runtime the path is not translated.
b) create maven profiles for development and production and setup the plugin only inside production profile this way you could package the web application and deliver to any application server.

Em 25/03/2013, às 11:16, David Anderson notifications@github.com escreveu:

Be able to have the jsp tag act differently in a development environment rather than a production environment. Uploading all the assets to s3 makes sense for production, but if I am in the middle of development, and am making a lot of css and js changes, I don't want to have to upload the files for every change.

This can be handled within the jsp tag. Rather than always translating the original file to an uploaded url, if in development mode, local urls should used for the resources.

—
Reply to this email directly or view it on GitHub.