Another feature request for Carsten. We have already discussed this once:
While testing a development block the properties from
/src/main/resources/META-INF/properties/* are not copied to webapp
directory. In order to load them properly we need include-properties/
also in cocoon.xconf
Leszek Gawron wrote:
Another feature request for Carsten. We have already discussed this once:
While testing a development block the properties from
/src/main/resources/META-INF/properties/* are not copied to webapp
directory. In order to load them properly we need include-properties/
Carsten Ziegeler wrote:
Leszek Gawron wrote:
Another feature request for Carsten. We have already discussed this once:
While testing a development block the properties from
/src/main/resources/META-INF/properties/* are not copied to webapp
directory. In order to load them properly we need
Leszek Gawron wrote
As long as it is configured automatically so the only thing that user
does is:
mvn clean compile cocoon:deploy jetty:run
I'm not that familiar with all aspects of the cocoon:deploy plugin, but
I thought that this one is deploying all files into the necessary locations?
Carsten Ziegeler wrote:
Leszek Gawron wrote
As long as it is configured automatically so the only thing that user
does is:
mvn clean compile cocoon:deploy jetty:run
I'm not that familiar with all aspects of the cocoon:deploy plugin, but
I thought that this one is deploying all files into
Leszek Gawron wrote:
SNIP
The blocks consists of:
- COB-INF resources (covered with mount in sitemap)
- java classes (loaded on sitemap level with reloading classloader, now
gets me thinking it will break if block supplies some core spring beans)
- avalon contexts (covered by include in
Carsten Ziegeler wrote:
Leszek Gawron wrote:
SNIP
The blocks consists of:
- COB-INF resources (covered with mount in sitemap)
- java classes (loaded on sitemap level with reloading classloader, now
gets me thinking it will break if block supplies some core spring beans)
- avalon contexts
Carsten Ziegeler wrote:
Leszek Gawron wrote:
SNIP
The blocks consists of:
- COB-INF resources (covered with mount in sitemap)
- java classes (loaded on sitemap level with reloading classloader, now
gets me thinking it will break if block supplies some core spring beans)
- avalon contexts
Carsten Ziegeler wrote:
Carsten Ziegeler wrote:
Leszek Gawron wrote:
SNIP
The blocks consists of:
- COB-INF resources (covered with mount in sitemap)
- java classes (loaded on sitemap level with reloading classloader, now
gets me thinking it will break if block supplies some core spring
Leszek Gawron wrote:
Hmmm ... not really. And the system property solution would not also
work. Everything because you may mount more that one development block
directly from source:
plugin
groupIdorg.apache.cocoon/groupId
artifactIdcocoon-deployer-plugin/artifactId
10 matches
Mail list logo