cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: svn commit: r109328 - in cocoon/branches/BRANCH_2_1_X: . src/blocks/template src/blocks/template/conf src/blocks/template/java src/blocks/template/java/org src/blocks/template/java/org/apache src/blocks/template/java/org/apache/cocoon src/blocks/template/java/org/apache/cocoon/el src/blocks/template/java/org/apache/cocoon/el/jexl src/blocks/template/java/org/apache/cocoon/el/util src/blocks/template/java/org/apache/cocoon/template src/blocks/template/java/org/apache/cocoon/template/generation src/blocks/template/java/org/apache/cocoon/template/script src/blocks/template/java/org/apache/cocoon/template/tag src/blocks/template/java/org/apache/cocoon/template/tag/samples src/blocks/template/java/org/apache/cocoon/util src/blocks/template/samples src/blocks/template/test src/blocks/template/test/org src/blocks/template/test/org/apache src/blocks/template/test/org/apache/cocoon src/blocks/template/test/org/apache/cocoon/el src/blocks/template/test/org/apache/cocoon/el/je! xl src/blocks/template/test/org/apache/cocoon/el/util src/blocks/template/test/org/apache/cocoon/template src/blocks/template/test/org/apache/cocoon/template/generation src/blocks/template/test/org/apache/cocoon/template/script src/blocks/template/test/org/apache/cocoon/util
Date Wed, 01 Dec 2004 14:50:09 GMT
Leszek Gawron wrote:

> Upayavira wrote:
>
>> Daniel Fagerstrom wrote:
>>
>>> Leszek Gawron wrote:
>>>
>>>> Daniel Fagerstrom wrote:
>>>
>>>
>>>
>>>
>>> <snip/>
>>>
>>>>> Thanks for commiting the template stuff !
>>>>>
>>>>> But do you really think that it is worth the effort to keep 2.1.x 
>>>>> syncronized with trunk wrt template at this early stage of 
>>>>> development? I'd prefer to sync it when we are a little bit more 
>>>>> shure about what interfaces we should have and so on.
>>>>
>>>>
>>>>
>>>>
>>>> Fine by me. Still we can sync once a few revisions.
>>>
>>>
>>>
>>>
>>> We can do that, but then we have to change the code so that it is 
>>> Java 1.3 compatible (or just turn of compilation of the block in 
>>> 2.1.x by default). The code contains some java.nio stuff which IIRC 
>>> not is contained in 1.3.
>>
>>
>>
>> Really, this should be developed in trunk, and then back-ported when 
>> it reaches a level of stability (unless we get 2.2 out quick enough 
>> :-) )
>>
>> Trunk is where new stuff goes, IMO.
>
> I see, sorry for the mess. 

No probs. That's what the rest of us are here for!

> Should I disable the block build by default ?

Erm. In trunk, I would leave it enabled. After all, it is just another 
unstable block.

Regards, Upayavira


Mime
View raw message