faresd / appengine-maven-plugin

Automatically exported from code.google.com/p/appengine-maven-plugin
Apache License 2.0
0 stars 0 forks source link

Enhancement: specify generated_dir on devserver startup #24

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
We should be able to specify optional --generated_dir devserver command line 
argument when starting devserver.

One should be able to set this variable outsite maven target directory, so that 
data can retain during multiple maven clean runs.

Attached patch implements this enhancement (you probably want to set it to 
${user.home}/.appengine/generated/${project.artifactId}).

Original issue reported on code.google.com by brane.gr...@outfit7.com on 23 Apr 2013 at 10:13

Attachments:

GoogleCodeExporter commented 8 years ago
It would be better if it somehow tied into the plugin version (and thereby the 
sdk version) and didn't persist during upgrades, or if it provided 
functionality to clean the generated directory without the user manually having 
to delete things.  I would rather this be built in a much different way so it's 
easier for less experienced users of the plugin to take advantage of it.  Let 
me know your thoughts.

Thanks,
Matt

Original comment by matts...@google.com on 23 Apr 2013 at 10:22

GoogleCodeExporter commented 8 years ago
Maybe we could introduce some kind of magic placeholder to generatedDir 
property, something like %{version}, which would be rewritten in runtime with 
plugin version, so that you could specify generatedDir in pom.xml like this:

${user.home}/.appengine/generated/%{version}/${project.artifactId}

We could also add simple goal, appengine:generated_cleanup for example, to 
perform generated directory cleanup.

What do you think?

Original comment by brane.gr...@outfit7.com on 24 Apr 2013 at 9:06

GoogleCodeExporter commented 8 years ago
Is there currently any way to set generated_dir param via maven? 

Original comment by hus...@gmail.com on 12 Jun 2014 at 12:35