Jörn Nettingsmeier wrote:
Michael Wechner wrote:
Jörn Nettingsmeier wrote:
hi *!
i have a custom module that contains a usecase-edit.xconf patchfile.
the module is located in a local modules path that has been
specified with ./configure.sh.
when i make changes to my module, i re-deploy it by killing lenya,
doing a ./build.sh --noconfig and restarting lenya. all changes are
there, except for the patchfile (i checked WEB-INF/cocoon.xconf,
it's still the old version).
what can i do (short of deleting the build tree) do get my
patchfiles re-applied?
Did you link the module directly (e.g. src/modules/my-module) or just
the parent path (e.g. src/modules).
The first doesn't work properly yet and still seems to have a bug.
hmm, not sure if i understand you...
i have given the config script "...:/build/localmodules" in addition
to the
you mean
modules.root.dirs=src/modules:src/pubs/default/modules:/build/localmodules
?
maybe this has also a bug (whereas it shouldn't)
default settings, and my module is /build/localmodules/person.
but
modules.root.dirs=src/modules:src/pubs/default/modules:/build/localmodules/person
does definitely have bugs :-( whereas I recently fixed one, but it will
only help you if you add a module.xml as description to you module
anyway, the workaround i'm using atm is to delete
WEB-INF/cocoon.xconf, which forces all patchfiles to be re-applied.
that works for me.
maybe you want to file a bug within bugzilla
Michi
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
