That makes sense. I'll just write my own then. Thanks, Dan.
On 11 November 2010 18:54, Mauro Talevi <[email protected]> wrote: > The story names are typically derived from package names, > com.example.SomeName, hence the trimming after the last period. > > > On 11/11/2010 18:45, Dan Godfrey wrote: > > I'm trying to get it to match the specification document I have. I > understand about capitalising after _, but why trim off before the last > period? > > I'll probably just write my own StoryNameResolver then. > > On 11 November 2010 18:41, Mauro Talevi <[email protected]>wrote: > >> Yes that is intentional. It assumes names use underscores to separate >> words. >> >> Can you not use underscores, i.e 1_1_2_some_requirement.story? >> >> On 11/11/2010 18:13, Dan Godfrey wrote: >> > Hi, >> > >> > I'm using full stops/periods in my story names, such as "1.1.2 some >> > requirement name.story". However, in the list of stories in Story >> > Reports page, it's cutting everything up to the last period off >> > (exclusing .story part). So, my list is showing "2 some requirement >> name". >> > >> > This is happening in UnderscoredToCapitalized, which is trimming >> > everything before the first period. Is this intentional or should I >> > raise a defect? >> > As from what I can tell the value passed into StoryNameResolver will >> > always be the filename without .story on the end. >> > >> > Thanks, >> > Dan. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > >
