2008/8/26 Olivier Lamy <[EMAIL PROTECTED]>: > +1 (in the future could you provide a link to the jira issues ?)
I would have liked to although the shared components all share the single MSHARED JIRA project, and thus the issues have no version fields set. I could send a link for the remaining issues but not for the issues fixed. This leads to the question I've been meaning to ask about how best to organise JIRA for the shared components. Should we: 1) Split up MSHARED into separate JIRA projects for each component 2) Use the notion of component-specific versions, e.g. version 'maven-dependency-tree-1.2' 3) Create the union of all shared component's versions and search by component+version 4) Leave out version information altogether as we currently do Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
