Reinhard Poetz wrote:
> I think the general problem is that you need to have downloaded the
> artifacts once as Maven have to put them into the local artifacts
> repository. Indeed, this can take very long if Maven is used for the
> first them. But then, it should work fine in the future as furth
CTED]>
>>> Reply-To: dev@cocoon.apache.org
>>> To: dev@cocoon.apache.org
>>> Subject: Re: Deployment into a monolithic Cocoon web app
>>>
>>> Le 25 mars 06 à 15:37, Reinhard Poetz a écrit :
>>>
>>>> ...What do you have to do to run trunk
into a monolithic Cocoon web app
Le 25 mars 06 à 15:37, Reinhard Poetz a écrit :
...What do you have to do to run trunk?...
Your instructions worked for me as well, but it took *ages*.
IIUC it's because Maven was trying to download stuff, getting
timeouts, retrying etc, lines like
[INF
Upayavira wrote:
Reinhard Poetz wrote:
Upayavira wrote:
[INFO] The plugin 'org.apache.maven.plugins:maven-cocoo-plugin' does not
exist or no valid version could be found
What's up?
You have to run it from "cocoon/trunk/cocoon-webapp".
Ah, yes. That did it.
Now, being stupid, are we su
Reinhard Poetz wrote:
> Upayavira wrote:
>
>> [INFO] The plugin 'org.apache.maven.plugins:maven-cocoo-plugin' does not
>> exist or no valid version could be found
>>
>> What's up?
>
> You have to run it from "cocoon/trunk/cocoon-webapp".
Ah, yes. That did it.
Now, being stupid, are we supposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 25 Mar 2006, Bertrand Delacretaz wrote:
Date: Sat, 25 Mar 2006 21:32:13 +0100
From: Bertrand Delacretaz <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Deployment into a monolithic Cocoon w
Upayavira wrote:
[INFO] The plugin 'org.apache.maven.plugins:maven-cocoo-plugin' does not
exist or no valid version could be found
What's up?
You have to run it from "cocoon/trunk/cocoon-webapp".
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering
Antonio Gallardo wrote:
> Upayavira escribió:
>> Tried both. No luck with either.
>>
> Are you using maven 2.0.2?
$ mvn -version
Maven version: 2.0.2
Upayavira
Upayavira escribió:
Tried both. No luck with either.
Are you using maven 2.0.2?
Best Regards,
Antonio Gallardo.
Bertrand Delacretaz wrote:
> Le 27 mars 06 à 20:44, Upayavira a écrit :
>
>> ...Then ran mvn cocoo:deploy and mvn cocoon:deploy..
>
> AFAIK It's
> cocoon:deploy, not
> cocoo:deploy
Tried both. No luck with either.
Upayavira
Le 27 mars 06 à 20:44, Upayavira a écrit :
...Then ran mvn cocoo:deploy and mvn cocoon:deploy..
AFAIK It's
cocoon:deploy, not
cocoo:deploy
-Bertrand
smime.p7s
Description: S/MIME cryptographic signature
Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>> Reinhard Poetz wrote:
>>
>>> 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
>
Carsten Ziegeler wrote:
> Reinhard Poetz wrote:
>
>> Two more things:
>>
>> - Carsten, I tried to deploy the session-fw but didn't succeeded because
>> the xconf files aren't correct. Could you have a look at it?
>> (the dependency on session-fw-samples is commented in the pom.xml ATM)
>
Reinhard Poetz schrieb:
>
> Two more things:
>
> - Carsten, I tried to deploy the session-fw but didn't succeeded because
> the xconf files aren't correct. Could you have a look at it?
> (the dependency on session-fw-samples is commented in the pom.xml ATM)
>
Yepp, will look at it ton
Thanks Reinhard! It simply works again. :-)
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
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:/ or
http
Reinhard Poetz wrote:
> 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:/ or
> http:/
Le 25 mars 06 à 15:37, Reinhard Poetz a écrit :
...What do you have to do to run trunk?...
Your instructions worked for me as well, but it took *ages*.
IIUC it's because Maven was trying to download stuff, getting
timeouts, retrying etc, lines like
[INFO] artifact org.apache.maven.plugi
* Reinhard Poetz:
> 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
Reinhard Poetz wrote:
> 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
cocoon:deploy
> $ mvn jetty6:run
>
> 2. point your browse
Reinhard Poetz wrote:
Jean-Baptiste Quenot wrote:
* Reinhard Poetz:
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
* Reinhard Poetz:
> Reinhard Poetz wrote:
>
> > Reinhard Poetz wrote:
> >
> > > I want to add some thoughts to Daniel's idea of writing some
> > > Ant script for the build: trunk has been mavenized and split
> > > up into many modules. The missing thing is some tool that
> > > will create a web
Jean-Baptiste Quenot wrote:
* Reinhard Poetz:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I want to add some thoughts to Daniel's idea of writing some
Ant script for the build: trunk has been mavenized and split
up into many modules. The missing thing is some tool that
will create a w
Carsten Ziegeler wrote:
Reinhard Poetz schrieb:
At least a description which files from META-INF/legacy/** are expected
under WEB-INF would be very helpful.
Carsten, does cocoon-webapp/src/main/webapp already show the correct structure?
Don't know :) The current core expects cocoon.xconf i
Reinhard Poetz schrieb:
>> At least a description which files from META-INF/legacy/** are expected
>> under WEB-INF would be very helpful.
>
> Carsten, does cocoon-webapp/src/main/webapp already show the correct
> structure?
>
Don't know :) The current core expects cocoon.xconf in WEB-INF as we
At least a description which files from META-INF/legacy/** are expected
under WEB-INF would be very helpful.
Carsten, does cocoon-webapp/src/main/webapp already show the correct structure?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open S
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I want to add some thoughts to Daniel's idea of writing some Ant
script for the build: trunk has been mavenized and split up into many
modules. The missing thing is some tool that will create a web
application out of a number of blocks. In a "world
27 matches
Mail list logo
