Shash) Chatterjee a écrit :
Putting src/* under conf/ doesn't feel quite intuitive to me.
In fact in my proposition, overwrite directory would not stay under conf but move directly under project root directory
I think the current structure works. We should experiment with removing the "overwrite=false" attributes in that part of the plugin, and see if we can remove it.
OK. ATM I am testing with the current plugin.jelly 1.3 and I get overwriting to work. But I'm unable to state clear rules on howto. I play with dependency order and jar date. The main problem is: unjar command keeps the date of the files but copy command gives the current date to all the copied files. So you can't guess from the original file (in jar) dates what will happen.
If stuff is put in src/webapp, then I do think it should overwrite the files from the JARs. If the user does not want it there, then the files can be moved. The JARs are built ahead of time, so user has no control of where it creates files. Putting files in src/webapp, the user has some measure of control on how the webapp and config is assembled. I think leaving the "overwrite=false" out makes sense..
I think that if we can keep original dates of files when there are copied it may be possible to state simple rules.
Pierre http://keelframework.org/documentation.shtml Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
