I don't think there is; let me look. Could not find anything; the module does
not have a spot for Jira issues yet (as it has not been formally introduced).
I expect we should use gt-data
(https://jira.codehaus.org/browse/GEOT/component/12110) and treat these issues
as problems with ContentDataStore.
--
Jody Garnett
On Tuesday, 10 May 2011 at 4:40 PM, lee-verizon wrote:
> Always including a jira number in commit comment is something we've done
> for years at my company. We have jira and svn connected together
> somehow (with fisheye?) so there's no need to put the revision info in
> the jira. Anyway, Jody: is there an open jira for the csv work I'm doing?
>
> Lee
>
> On 5/9/2011 11:30 PM, Jody Garnett wrote:
> > > Please also include any Jira issue id in your commit log, and note the
> > > svn revision and branch in your Jira issue. Jody, you got me doing this,
> > > and it is a great practice. Is it in the developer guide?
> > Ben I recommend we get a glass of wine; and make a patch for the
> > developers guide it needs some love.
> > (and perhaps you need the glass of wine?)
> >
> > Jody
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
