In general, I recommend a full build for anything but the most trivial
change. You wouldn't want to break the build with your first commit,
would you? But changing the pom details is pretty trivial, any only
risks corrupting the pom (which would break the build). This would be
caught by building cvs.
TL;DR: add your details to the csv pom, build the csv module ("mvn clean
install"), then commit
To make changes to other modules, submit a patch to codehaus Jira and
ensure it is assigned to the module maintainer. If approved, you can
then commit (after a full build).
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?
On 10/05/11 13:24, lee-verizon wrote:
> Done. And just to be sure I understand:
>
> - To commit to csv, I just do it. I don't need to run a full
> build-and-test for all the other projects. csv project should pass its tests
> (but it won't break the rest of the build if not). Correct?
>
> - If I want to make a change to some other (supported) module, such as
> data, how do I handle that?
>
> Thanks,
>
> Lee
>
> On 5/9/2011 9:09 PM, Jody Garnett wrote:
> Welcome formally to the project Lee. Your first "task" is to update the
> pom.xml file for the csv module to include your details :-)
>
> --
> Jody Garnett
>
>
> On Tuesday, 10 May 2011 at 2:01 PM, lee-verizon wrote:
>
> Jody invited me to be a committer for the (unsupported) CSV project. I
> have filled out the paperwork and will get it to a mailbox tomorrow. My
> osgeo account id is LeeBreisacher.
>
> Thanks,
>
> Lee
>
> ------------------------------------------------------------------------------
> 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<mailto:Geotools-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
> iv>
>
>
>
--
Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
------------------------------------------------------------------------------
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
