Re: Re: Naming scheme

OK.

what about this change in version.properties?

tl.usertasks.spec=1.25.${tl.api.impl}${tl.core.impl}${tl.usertasks.impl}
to
tl.usertasks.spec=1.25.2

Do we use it only because AU will not use a new nbm if it hasn't a new 
spec version?
If so, isn't it a bug in AU?

--Tim

Petr Kuzel wrote:

>Tim wrote:
>
>  
>
>>Hi specificallyylyI am not pleased with the current naming scheme of the
>>    
>>
>tasklist module.
>  
>
>>There are 2 things I don't like:
>>- Version numbers like 1.25.51136 look very strange and do not express
>>the real progress of a module
>>- Module's version may change although the module itself did not (if the
>>core changes)
>>
>>Why not use something like this (">" is important here):
>>
>>OpenIDE-Module-Specification-Version: @tl.usertasks.spec@
>>OpenIDE-Module-Implementation-Version: @DATE@
>>OpenIDE-Module-Module-Dependencies: org.netbeans.modules.tasklist.core/2
>> > @tl.core.spec@
>>
>>Wouldn't this be enough to satisfy all our needs?
>>    
>>
>
>There are restrictions on specification version (">")
>dependencies usage in NetBeans modules. Well, problem
>is not bound to NB modules specifically but to backward
>comparability. With specification version deps. one cannot
>make any backward incompatible changes. And backward
>compatability is a strict requirement for NB modules.
>
>  Cc.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>
>  
>