Leszek Gawron wrote:
Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
snip/
It's a pity we cannot move .xconf files into jars.
Why can't we?
AFAIR due to the fact that resource:/ protocol is not as functional as
file:/ (no directiories?)
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
AFAIR due to the fact that resource:/ protocol is not as functional
as file:/ (no directiories?) and it would be quite intensive
operation to find .xconf files.
Carsten made the resource: protocol traversable a couple of months ago.
Nope,
Reinhard Poetz wrote:
Should we move the stylesheets
I would help a lot to be able to deploy cocoon with no additional files
at all. What do you say if we moved cocoon logo and default stylesheets
(the ones styling error pages etc.) to some jar (either existing or a
new one)?
This way we
Leszek Gawron wrote:
Reinhard Poetz wrote:
Should we move the stylesheets
I would help a lot to be able to deploy cocoon with no additional
files at all. What do you say if we moved cocoon logo and default
stylesheets (the ones styling error pages etc.) to some jar (either
existing or a
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
Should we move the stylesheets
I would help a lot to be able to deploy cocoon with no additional
files at all. What do you say if we moved cocoon logo and default
stylesheets (the ones styling error pages etc.) to some
Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
Should we move the stylesheets
I would help a lot to be able to deploy cocoon with no additional
files at all. What do you say if we moved cocoon logo and default
stylesheets (the ones styling
