cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Gallardo <agalla...@agssa.net>
Subject Re: Releasing 2.1.8
Date Fri, 14 Oct 2005 03:44:21 GMT
Leszek Gawron wrote:

> Upayavira wrote:
>
>> Leszek Gawron wrote:
>>
>>> Leszek Gawron wrote:
>>>
>>>> Jorg Heymans wrote:
>>>>
>>>>> Leszek Gawron wrote:
>>>>>
>>>>>> want it - got it.
>>>>>> check the trunk - if it's ok - I'll port it back to 2.1.
>>>>>>
>>>>>
>>>>>
>>>>> I don't have time to check myself, but are these new properties
>>>>> respected by the eclipse-customized-project target ?
>>>>
>>>>
>>>>
>>>>
>>>> They should but ... to tell you the truth I do not know. I will 
>>>> check that.
>>>>
>>>> Slightly OT: why don't we make eclipse-customized-project a default 
>>>> target for eclipse IDE? Since eclipse-customized-project was 
>>>> introduced this is the only one I use.
>>>
>>>
>>>
>>> I will remove the standard eclipse-project (It also seems outdated 
>>> comparing to eclipse-customized-project). eclipse-customized-project 
>>> has all the functionality of the former one so this should be no 
>>> problem for anyone.
>>
>>
>>
>> But what happens now if someone runs the old eclipse-project? Does it 
>> output an error saying to use eclipse-customized-project and what has 
>> changed? Or does it just say "no such target"?
>
>
>   <!-- for those who like long names.. -->
>   <target name="eclipse-customized-project" depends="eclipse-project"/>

Sorry for the long name. I was unable to find quickly a better name. ;-)

Seriously, since the long name for customized eclipse build seems to be 
used only by you and me, then I think we can also deprecate it now and 
remove it in 2.2.

WDYT?

Best Regards,

Antonio Gallardo


Mime
View raw message