Carsten Ziegeler wrote:
Reinhard Poetz wrote:
How can we help our upcoming 2.2 users? IMO there are two approaches
which should be followed in parallel:
1) make the usage of Maven 2 as simple as possible
- the tutorials take this into account
- we provide different archetypes
2) offer an alternative to Maven 2
Option one is clear and is nearly finsihed. My question is regarding
to option 2: What do you expect, when you download Cocoon 2.2 in order
to get your new Cocoon 2.2 project started?
Keep in mind that Cocoon 2.2 is split into a core and several blocks
(template, forms, etc.). All of them are separate release artifacts
and in contrast to Cocoon 2.1 they can and will be shipped as binaries
again. (Note that I'm not talking about samples, that's something
different.)
Just some unstructured thoughts:
What about creating a zip containing the result of the cocoon archetype
run? People could use this as a starting point for own projects without
maven.
I guess that you mean the result in ./target/webapp which is created by "mvn
install", don't you?
Adding blocks should then just be adding the jar which is
available for download.
yep
The final step would be a document how to build your own block without
maven, perhaps someone could come up with an ant script doing this stuff.
good idea, shouldn't be that difficult.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
