[MetaCRS] Directory structure for CSV Test data files

[Norm Olsen]

Don't we already have a directory "testsuite" at the root.  I don't imagine folks reading the file directly from the web.  Obtaining the test file would be part of their download procedure and they put it where they need it.

You don't get to a "trunk" folder until you've selected a library.  The purpose of this file is to be completely independent of the specific library in use, is it not???

Norm

-----Original Message-----
From: metacrs-bounces at lists.osgeo.org [mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Frank Warmerdam
Sent: Sunday, November 15, 2009 10:05 PM
To: Martin Desruisseaux
Cc: metacrs at lists.osgeo.org
Subject: Re: [MetaCRS] Directory structure for CSV Test data files

Martin Desruisseaux wrote:
> Just a precision for those who may not be familiar with Maven. Setting 
> up the directory structure as a Maven project means that we would have:
> 
>   trunk/pom.xml
>   trunk/src/main/resources/whateverTestDataFile.csv
> 
> We can alternatively rename "src/main/resources/" to something shorter 
> (but non-maven standard) if people wish.

Martin,

While this seems rather arcane as a directory structure, I'm ok with
if it if it helps substantially in Java/Maven deployment.

For my purposes, in GDAL, I expect to manually import new versions of the
file periodically rather than have it picked up entirely automatically.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
MetaCRS mailing list
MetaCRS at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/metacrs