Created a jira issue including a patch that only takes files directly
under flow/ into account.
http://issues.apache.org/jira/browse/COCOON-1933
Alex
Alexander Klimetschek schrieb:
I just run into a problem with the automatic loading of all files inside
flow/: if there is a subversion
I now implemented this convention stuff - all files located in the
flow directory relative to the current sitemap are added to the flow
interpreter - regardless of the file name suffix and the used
interpreter (javascript, javaflow etc). The directory is of course optional.
By this we show a best
On 29.09.2006 09:19, Carsten Ziegeler wrote:
Now what about the other directories we currently have:
config/spring, config/xconf and config/properties?
Should we leave them where they are or move them one directory up?
I'd prefer the flat variant, i.e. without config subdir.
Jörg
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Is anyone against make using flow a little bit easier in trunk?
I really hate to specify all my flow scripts in the sitemap - so what
about using some convention over configuration stuff and include by
default all *.js files which are located in
Carsten Ziegeler said the following on 29/9/06 09:19:
If noone objects I will add the stuff in the next days.
I like the feature but not the location as flowscripts are not configuration
files. What about ./flow only?
Ok, it seems that everyone here is in favour of using just flow
without an
hepabolu wrote:
How much extra effort would it take to allow overriding the location in
e.g. the sitemap? E.g. as an attribute in map:flow
map:flow location=my/own/path/to/flow/
That shouldn't be difficult - but then the question is if this is
overriding the
default location or an
Carsten Ziegeler wrote:
hepabolu wrote:
How much extra effort would it take to allow overriding the location in
e.g. the sitemap? E.g. as an attribute in map:flow
map:flow location=my/own/path/to/flow/
That shouldn't be difficult - but then the question is if this is
overriding the
default
Reinhard Poetz said the following on 29/9/06 11:14:
Carsten Ziegeler wrote:
hepabolu wrote:
How much extra effort would it take to allow overriding the location
in e.g. the sitemap? E.g. as an attribute in map:flow
map:flow location=my/own/path/to/flow/
That shouldn't be difficult - but
hepabolu wrote:
Agree, but since it's more part of the application like Bertrand pointed
out, I favor a way to override the default location. So:
- default = all *.js in ./flow
- some specification somewhere = all *.js in my/own/path/to/flow
- different locations = use map:flow/ (which is
Is anyone against make using flow a little bit easier in trunk?
I really hate to specify all my flow scripts in the sitemap - so what
about using some convention over configuration stuff and include by
default all *.js files which are located in the config/flow
directory (relative to the current
Carsten Ziegeler wrote:
Is anyone against make using flow a little bit easier in trunk?
I really hate to specify all my flow scripts in the sitemap - so what
about using some convention over configuration stuff and include by
default all *.js files which are located in the config/flow
directory
On 9/28/06, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Is anyone against make using flow a little bit easier in trunk?
I really hate to specify all my flow scripts in the sitemap - so what
about using some convention over configuration stuff and include by
default all *.js files which are located
Carsten Ziegeler wrote:
Is anyone against make using flow a little bit easier in trunk?
I really hate to specify all my flow scripts in the sitemap - so what
about using some convention over configuration stuff and include by
default all *.js files which are located in the config/flow
directory
13 matches
Mail list logo
