cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <coc...@leverageweb.com>
Subject Re: Running the latest CVS snapshot - should it be this hard?
Date Sat, 16 Aug 2003 22:29:21 GMT
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
> 
> 
> 
> 
> 



Mime
View raw message