Reinhard Poetz pisze:
Andrew Savory wrote:
Hi,
Following up on the thread about archetypes etc, I'd love to hear from
others on how they are approaching application building with 2.2 and
what they see as 'best practise' - primarily because I'm concerned
that the route the current setup sends people down might explicitly
*not* be good:
On 19 Apr 2007, at 00:57, Andrew Savory wrote:
- Looking at the way this works, myBlock is installed into $M2_REPO
as part of the build. But myBlock seems like the logical place to put
my XML content (in resource/internal/ as per the Block conventions
thread). I really don't want multiple copies being put into $M2_REPO,
and then installed into myCocoonWebapp/target/work/blocks/myBlock1
too. I know disk space is cheap, but ... !
I want my app just working. Even though I know how Maven manages files of my
projects, I usually don't care. Space is *very* cheap.
How are others doing this?
- I start a new cocoon-22 project using the block archetype
- I activate the cocoon-rcl plugin in pom.xml
- then I enter "mvn eclipse:eclipse cocoon-rcl:webapp jetty:run"
- I import the project in Eclipse
- finally it's time to start working
When the need arises, I create more blocks (e.g. skinning, CMS access,
etc.).
When I need a deployment unit, I use the webapp archetype and add my
block as dependency.
Same here. I think this can be considered as standard practise.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
