#1226: Suport for multiple public directory
-------------------------------+--------------------------------------------
Reporter: mug...@… | Owner: impl
Type: enhancement | Status: closed
Priority: normal | Milestone: 1.0.3
Component: build | Version: 1.0.2
Severity: normal | Resolution: wontfix
Keywords: | Has_patch: 0
-------------------------------+--------------------------------------------
Changes (by felix):
* status: new => closed
* resolution: => wontfix
Comment:
a) I haven't checked but public-create should overwrite the files in the
public directory, so there's no need for a public-update. If it doesn't,
roll your own
b) The agavi build system creates a standard project layout, we can not
and will not cater for all possible demands. Some prefer all dispatcher
files for multiple contexts and virtual hosts in one directory, others
prefer multiple directories as you do. We're not going to promote or
enforce one of two equally good solutions.
Currently the build system relies on the pub directory to find the
project. While this may be changed in future releases, it's not easily
configurable atm. You can, however pass it on the commandline via
-Dproject.directory.pub=foo. You can also pass the directory to copy from
via -Dproject.directory.dev.pub=bar.
You can also add a create-public-mobile task to your project's build.xml
and if you wish to create a task that calls all of the environment-
creation tasks.
You can have a look at http://blog.agavi.org/post/155525959/extending-the-
build-system-integrating-jsllint for an example of how to extend the build
script and at http://blog.agavi.org/post/155569516/using-your-own-build-
templates-from-second-zero for how to use your custom build.xml template
for all future projects.
--
Ticket URL: <http://trac.agavi.org/ticket/1226#comment:3>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
