On 3/13/13, Jure Zitnik <[email protected]> wrote: > On 3/13/13 8:58 AM, Olemis Lang wrote: >> On 3/13/13, Jure Zitnik <[email protected]> wrote: >>> On 3/13/13 5:18 AM, Branko Čibej wrote: >>>> On 13.03.2013 05:08, Olemis Lang wrote: >>>>> On 3/12/13, [email protected] <[email protected]> wrote: >>>>>> Author: jure >>>>>> Date: Tue Mar 12 15:15:22 2013 >>>>>> New Revision: 1455576 >>>>>> >>>>>> URL: http://svn.apache.org/r1455576 >>>>>> Log: >>>>>> Renamed default product to '@', >>>>> @jure: why ? >>>> Because it's a token that is forbidden as a product tag and therefore >>>> cannot conflict with existing product names. >> I'll ask the negation of the negation . >> >> Why is it that we'll have to apply this change instead of sticking to >> '' as global prefix? > > Just to clarify things, we did not change '' as the global prefix. The > default product '@' is the product to which all the tickets w/o product > get migrated during upgrade process. >
Oh ! Now I see ... and how will that data be retrieved if we use a non-standard prefix ? PS: /me just wandering to be consistent with the new convention ;) >>> Brane, I double checked and currently there's no prefix checking on >>> product creation, though we should add one to prevent someone from >>> adding product with funky prefixes, including the reserved '@' ... I >>> think '^[a-zA-Z0-9_]+$' would suffice for now. >>> >> -0 ... I'd suggest (?:(?!\d)\w+) ... which is already available in >> multiproduct.util.IDENTIFIER after recent patches . > > Sure, we can go with that one too ... > things like Hønsdrükḱenshàpełlmünçen (i.e. unicode chars ;) will be supported , which is nice to have ; and will be matched by TracLinks expressions ;) -- Regards, Olemis.
