Reinhard Poetz wrote:
Jean-Baptiste Quenot wrote:
* Reinhard Poetz:
<snip/>
Do you mean deploying Cocoon built with Maven without the real
blocks?
No
If this is the case, how to test it, is there an « mvn
something » in some directory?
Or are you talking about cocoon-deployer-webapp-sample? This one
seems to be dealing with real blocks.
Thanks in advance for your answer,
The idea is that at packaging time, a M2 plugin scans an artifact (jar)
whether it is a Cocoon blocks if it is, some files (xconf, xlog, etc.)
are extracted into the right directory. e.g. all .xconf files go to
WEB-INF/xconf.
The unit-tests are already working but I need some more time to provide
a sample based on cocoon-webapp. This will make it hopefully clearer.
I added the cocoon deployer plugin to the cocoon-webapp module. Instead of "mvn
package" you have to call "mvn cocoon:deploy". The plugin scans all modules by
scanning for patterns in document paths (see
http://svn.apache.org/repos/asf/cocoon/trunk/cocoon-block-deployer/cocoon-deployer-core/src/main/java/org/apache/cocoon/deployer/MonolithicCocoonDeployer.java).
I also added a simple example by adding a dependency on
'cocoon-deployer-plugin-demo'.
What do you have to do to run trunk?
------------------------------------
0. checkout complete trunk and
$ mvn clean install -Dmaven.test.skip=true
Call this as long as you get "BUILD SUCCESSFUL".
1. go to cocoon-webapp
$ mvn cocoo:deploy
$ mvn jetty6:run
2. point your browser to http://localhost:8888/ or
http://localhost:8888/apps/cocoon-deployer-plugin-demo/test
Please report back if it works for you too.
- o -
What needs to be done to get a release of trunk out of the door?
----------------------------------------------------------------
a) we have to change the directory structure of all blocks as shown in
'cocoon-deployer-plugin-demo'. I will do it together with Andreas on Thursday
for the blocks in "cocoon/blocks". For the blocks that are already Maven modules
there is some work left.
b) clean up the directory structure of trunk (will do it next week on Thursday
too)
c) check every block if it works.
d) sync trunk with branch completly
e) go through all tests and either make them run or delete them
f) make the samples browsable again (without URL guessing)
I will do b) and partly a) on Thursday - I hope that others jump in for the
remaining tasks.
- o -
I hope that the possibility of running trunk again resolves all uncertainty
whether trunk is usefull or alive in a positive way. If there are problems with
the deployment I will gladly help, otherwise I will concentrate on cleaning up
trunk, the documentation (--> M2 plugin for Daisy) and OSGi deployment over the
next weeks.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
