Re: using maven archetypes

Am 04.07.2013 08:16, schrieb Francesco Chicchiriccò:
> On 03/07/2013 20:40, Piratenvisier wrote:
>> Where do I find your workaround instructions ?
>
> At [1], in the "Maven 2 archetypes" section (you might need to clear 
> your browser's cache):
>
> Some issues were identified in the 3.0.0-alpha-3 artifacts that 
> prevent the generated projects to work properly; as a temporary 
> workaround, you will need to apply the following changes to the 
> generated pom.xml files:
>
> 1. replace any 3.0.0-alpha-3-SNAPSHOT occurrency with 3.0.0-alpha-3
>
> 2. add <version>1.0.0</version> right below 
> <artifactId>cocoon-maven-plugin</artifactId>
>
> Regards.
Thank you I got it.
I was an adherent of cocoon from the beginning.
But with the upcoming AJAX I felt that for dynamic web it was not the 
rightt solution.
So I stopped to use it.I started my project again because thanks to 
cocoon's hompage I
noticed the upcoming wicket.
Wicket brought a new dynamic in my project there were only two use-cases 
for which I preferred cocoon.
For PDF generation and email-transport. I used flow :cocoon-protocol fop-ng
But this services could not be upgraded from cocoon 2.2.0 to 3.
Meanwhile I use hibernate and spring 3.1 and I would prefer to use the 
hibernate ojb-part with annotations in cocoon.
but in cocoon 3 first flow and cocoon-protokol is missing and I can not 
use spring 3.1
So the situation becomes worse and worse for me. So I am looking how to 
escape from cocoon
with flyingsaucer and an own email adaption maybe as soap-application.
Best regards
Heiner

>
>> Am 03.07.2013 10:12, schrieb Francesco Chicchiriccò:
>>> On 03/07/2013 08:37, Piratenvisier wrote:
>>>> When i create the mysample block with the atchetype as described on 
>>>> the cocoon 3.0
>>>> homepage maven first complains that there is no cocoon-optional 
>>>> 3.0.0-alpha-3-SNAPSHOT dependency.
>>>> when I ask for cocoon-optional 3.0.0-alpha-3 I get the error when I 
>>>> start jetty
>>>> java.lang.NoClassDefFoundError: 
>>>> org/springframework/core/env/Environment
>>>> what is the problem
>>>> when I want to use the cocoon pipeline in my wicket application
>>>> I have a dependency problem between flyingsaucer and
>>>> org.apache.xmlgraphics fop 1.0
>>>> or org.apache.cocoon cocoon-fop-ng-impl 1.0.0-SNAPSHOT
>>>
>>> Hi,
>>> it seems there are some issues with 3.0.0-alpha-3 maven archetypes: 
>>> I have updated [1] with some workaround instructions that should fix 
>>> your issues.
>>>
>>> Regards.
>>>
>>> [1] http://cocoon.apache.org/3.0/download.html
>