You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Joerg Heinicke <jo...@gmx.de> on 2003/08/16 21:06:07 UTC
Re: Running the latest CVS snapshot - should it be this hard?
This poor guy has edited the complete cocoon.xconf by hand, what is not
that easy as you can imagine. Should we make the "webapp" target the
default one in 2.0 too or speaks anything against it?
Joerg
John Williams wrote:
> Yes, I tested it and "build webapp" does exactly what I wanted and I see now
> in http://cocoon.apache.org/2.0/installing/ that the following is written:
>
> "The target you WILL MOST USE IS PROBABLY THE WEBAPP TARGET which builds a
> Cocoon web application. For more information see below." (my uppercase)
>
> I wonder if more attention should not be drawn to the fact the "build all"
> ONLY builds cocoon.jar - I know the intall page says so but intuitively (and
> a C make background) all sounds like the big one.
>
> John
>
> Joerg Heinicke wrote:
>
>>Sorry, but if you use "build webapp", these things are donw for you by
>>the build system.
>>
>>
>>>In order to test a recent fix I downloaded a CVS snapshot .
>>>My expectation was that once I had done a "build all" and copied all the
>>>necessary jars into WEB-INF I could use the configuration in
>>>cocoon-2.0/src/webapp in the snapshot's tar.gz file and be on my way.
>>>
>>>Not so! I had to make the modifications detailed below to the
>
> cocoon.xconf
Re: Running the latest CVS snapshot - should it be this hard?
Posted by Vadim Gritsenko <va...@verizon.net>.
Geoff Howard wrote:
> Joerg Heinicke wrote:
>
>> This poor guy has edited the complete cocoon.xconf by hand, what is
>> not that easy as you can imagine. Should we make the "webapp" target
>> the default one in 2.0 too or speaks anything against it?
>
>
> I'd be +1. It's the 99% most used, it should be the default.
+1.
I'd also remove "webapp-local", rename "webapp" to "war", and
"prepare-war" to "webapp". :)
Vadim
> At the very least "all" should run _all_ targets, not just compile
> (or whatever it was doing).
>
> Geoff
Re: Running the latest CVS snapshot - should it be this hard?
Posted by Geoff Howard <co...@leverageweb.com>.
Joerg Heinicke wrote:
> This poor guy has edited the complete cocoon.xconf by hand, what is not
> that easy as you can imagine. Should we make the "webapp" target the
> default one in 2.0 too or speaks anything against it?
I'd be +1. It's the 99% most used, it should be the default. At the
very least "all" should run _all_ targets, not just compile (or whatever
it was doing).
Geoff
>
>> Yes, I tested it and "build webapp" does exactly what I wanted and I
>> see now
>> in http://cocoon.apache.org/2.0/installing/ that the following is
>> written:
>>
>> "The target you WILL MOST USE IS PROBABLY THE WEBAPP TARGET which
>> builds a
>> Cocoon web application. For more information see below." (my uppercase)
>>
>> I wonder if more attention should not be drawn to the fact the "build
>> all"
>> ONLY builds cocoon.jar - I know the intall page says so but
>> intuitively (and
>> a C make background) all sounds like the big one.
>>
>> John
>>
>> Joerg Heinicke wrote:
>>
>>> Sorry, but if you use "build webapp", these things are donw for you by
>>> the build system.
>>>
>>>
>>>> In order to test a recent fix I downloaded a CVS snapshot .
>>>> My expectation was that once I had done a "build all" and copied all
>>>> the
>>>> necessary jars into WEB-INF I could use the configuration in
>>>> cocoon-2.0/src/webapp in the snapshot's tar.gz file and be on my way.
>>>>
>>>> Not so! I had to make the modifications detailed below to the
>>
>>
>> cocoon.xconf
>
>
>
>
>
Re: Running the latest CVS snapshot - should it be this hard?
Posted by Geoff Howard <co...@leverageweb.com>.
Joerg Heinicke wrote:
> This poor guy has edited the complete cocoon.xconf by hand, what is not
> that easy as you can imagine. Should we make the "webapp" target the
> default one in 2.0 too or speaks anything against it?
I'd be +1. It's the 99% most used, it should be the default. At the
very least "all" should run _all_ targets, not just compile (or whatever
it was doing).
Geoff
>
>> Yes, I tested it and "build webapp" does exactly what I wanted and I
>> see now
>> in http://cocoon.apache.org/2.0/installing/ that the following is
>> written:
>>
>> "The target you WILL MOST USE IS PROBABLY THE WEBAPP TARGET which
>> builds a
>> Cocoon web application. For more information see below." (my uppercase)
>>
>> I wonder if more attention should not be drawn to the fact the "build
>> all"
>> ONLY builds cocoon.jar - I know the intall page says so but
>> intuitively (and
>> a C make background) all sounds like the big one.
>>
>> John
>>
>> Joerg Heinicke wrote:
>>
>>> Sorry, but if you use "build webapp", these things are donw for you by
>>> the build system.
>>>
>>>
>>>> In order to test a recent fix I downloaded a CVS snapshot .
>>>> My expectation was that once I had done a "build all" and copied all
>>>> the
>>>> necessary jars into WEB-INF I could use the configuration in
>>>> cocoon-2.0/src/webapp in the snapshot's tar.gz file and be on my way.
>>>>
>>>> Not so! I had to make the modifications detailed below to the
>>
>>
>> cocoon.xconf
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org