Joerg Heinicke wrote:
...
Ralph made a proposal [1] where exactly one block (= directory) per
block (= block in the narrower sense) exists, but with many modules
(in the maven sense) in them:
/src
/blocks
/cforms
/api
pom.xml
/impl
pom.xml
/samples
pom.xml
/test
pom.xml
This holds together all parts of one block, but provides still the
possibility to separate them.
Hope this makes it more clear,
Jörg
[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113004733610151&w=4
Although I agree with that 120 blocks in one directory is easy to get
lost in and that we have to do something about that, I see some problems
with the above proposal.
It is a good idea to separate in api and implementation, but a good api
might have several impementations. For the flow api we have flowscripts,
Java flow and Apples, IIUC. The expression api that we discussed
recently have a JXPath, Jexl and Rhino implementation.
For tests Jorg have already said that Maven's test support assumes that
the tests are integrated in the module. For OSGi it will also be easier
to handle unit tests if they are part of the bundle, otherwise all
packages that we want to unit test (i.e. all implementaion packages),
need to be exported which we don't want.
For functional tests it might however make sense to write an external
test block.
/Daniel
