svn commit: r933800 - in /websites/staging/sis/trunk/content: ./ contributor.html
Author: buildbot Date: Tue Dec 23 17:58:14 2014 New Revision: 933800 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/contributor.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 17:58:14 2014 @@ -1 +1 @@ -1647625 +1647629 Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 17:58:14 2014 @@ -169,7 +169,7 @@ by Apache SIS. the functionality available in the base module, and the functioning of the modules of interest. Fetching and editing source code Different SIS branches are available depending on the target platforms. -Unless working on a SIS port (e.g. to the Android platform), contributors are encouraged +Unless working on a SIS port (e.g. the Android platform), contributors are encouraged to work on the SIS branch targeting the most recent JDK platform (currently JDK8): svn checkout https://svn.apache.org/repos/asf/sis/branches/JDK8 sis cd sis @@ -183,7 +183,7 @@ and guidelines about the way SIS source Copies or displacements of files shall be done with the svn copy or svn move command, respectively. Be aware that not all IDE or graphical tools perform this action appropriately. Always verify on the command-line, at least the first times that a new tools is used, by executing svn status. -Files that have been moved or copied shall have a A+ symbol in the left margin, like below: +Files that have been moved or copied shall have a + symbol in the left margin, like below: D my-directory/the-old-filename A +my-directory/the-new-filename
svn commit: r933801 - in /websites/staging/sis/trunk/content: ./ contributor.html
Author: buildbot Date: Tue Dec 23 18:02:28 2014 New Revision: 933801 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/contributor.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 18:02:28 2014 @@ -1 +1 @@ -1647629 +1647631 Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 18:02:28 2014 @@ -131,7 +131,7 @@ Contributors to SIS should have at least identical versions of standards which have evolved from the collaboration. The OGC specifications are available for the http://www.opengeospatial.org/standards";>OGC standards and specification page. As time progresses, we hope to develop documentation material to introduce the ISO 19000 specification series. -Most of this documentation can be found in the Apache SIS developer guide. +Most of the documentation provided by SIS can be found in the developer guide. Object-Oriented Programming in Java SIS is a library designed to be used by other programmers. To play this role effectively, SIS must consider the various ways that users can reuse Java code: not only through object
svn commit: r1647631 - /sis/site/trunk/content/contributor.mdtext
Author: desruisseaux Date: Tue Dec 23 18:02:24 2014 New Revision: 1647631 URL: http://svn.apache.org/r1647631 Log: Reword a confusing sentence (the old wording gave the impression that SIS was documenting most of ISO specifications, which is very far from the reality). Modified: sis/site/trunk/content/contributor.mdtext Modified: sis/site/trunk/content/contributor.mdtext URL: http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647631&r1=1647630&r2=1647631&view=diff == --- sis/site/trunk/content/contributor.mdtext [UTF-8] (original) +++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 18:02:24 2014 @@ -68,7 +68,7 @@ identical versions of standards which ha are available for the [OGC standards and specification][standards] page. As time progresses, we hope to develop documentation material to introduce the ISO 19000 specification series. -Most of this documentation can be found in the [Apache SIS developer guide](book/en/developer-guide.html). +Most of the documentation provided by SIS can be found in the [developer guide](book/en/developer-guide.html).
svn commit: r1647629 - /sis/site/trunk/content/contributor.mdtext
Author: desruisseaux
Date: Tue Dec 23 17:58:10 2014
New Revision: 1647629
URL: http://svn.apache.org/r1647629
Log:
Minor edition.
Modified:
sis/site/trunk/content/contributor.mdtext
Modified: sis/site/trunk/content/contributor.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647629&r1=1647628&r2=1647629&view=diff
==
--- sis/site/trunk/content/contributor.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 17:58:10 2014
@@ -136,7 +136,7 @@ Fetching and editing source code{#so
=
Different SIS [branches](branches.html) are available depending on the target
platforms.
-Unless working on a SIS port (e.g. to the Android platform), contributors are
encouraged
+Unless working on a SIS port (e.g. the Android platform), contributors are
encouraged
to work on the SIS branch targeting the most recent JDK platform (currently
JDK8):
:::bash
@@ -156,7 +156,7 @@ Committing changes{#commit}
Copies or displacements of files shall be done with the `svn copy` or `svn
move` command, respectively.
Be aware that not all IDE or graphical tools perform this action appropriately.
**Always verify on the command-line**, at least the first times that a new
tools is used, by executing `svn status`.
-Files that have been moved or copied shall have a `A+` symbol in the left
margin, like below:
+Files that have been moved or copied shall have a `+` symbol in the left
margin, like below:
:::text
D my-directory/the-old-filename
svn commit: r1647625 - in /sis/site/trunk/content: code-patterns.mdtext contributor.mdtext
Author: desruisseaux
Date: Tue Dec 23 17:47:53 2014
New Revision: 1647625
URL: http://svn.apache.org/r1647625
Log:
Minor adjustement to the formatting and wordings.
Modified:
sis/site/trunk/content/code-patterns.mdtext
sis/site/trunk/content/contributor.mdtext
Modified: sis/site/trunk/content/code-patterns.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/code-patterns.mdtext?rev=1647625&r1=1647624&r2=1647625&view=diff
==
--- sis/site/trunk/content/code-patterns.mdtext (original)
+++ sis/site/trunk/content/code-patterns.mdtext Tue Dec 23 17:47:53 2014
@@ -121,9 +121,9 @@ Apache SIS uses the `java.util.logging`
instead of invoking the `getLogger(String)` method provided by the
`java.util.logging.Logger` class,
we rather invoke the method provided by the `apache.sis.util.logging.Logging`
class.
The result is identical by default,
-but the SIS method gives us a chance to redirect the logging to an other
framework like Log4J if desired.
-The difference between the SIS approach and other facades like
`common-logging` is that
-SIS uses the standard Java API (except for the above-cited `getLogger` method)
instead than defining new API.
+but the SIS method gives a chance to redirect the logging to an other
framework like Log4J if desired.
+The difference between the SIS approach and other facades like
`common-logging` is that SIS uses the
+standard Java API (except for the above-cited `getLogger` method) instead than
defining a new API.
@@ -133,7 +133,7 @@ Logger name{#logger-name}
The name given in argument to the `getLogger(String)` method is usually the
package name of the class
emitting the log messages, but not necessarily. In particular, we do not
follow this convention if the class
is located in an internal package (`org.apache.sis.internal.*`) since those
packages are considered privates.
-In such case, the logger name should be the package name of the public class
that use the internal class.
+In such cases, the logger name should be the package name of the public class
that use the internal class.
The reason for the above rule is that logger names are considered part of the
public API,
since developers use them for configuring their logging (verbosity,
destination, etc.).
Modified: sis/site/trunk/content/contributor.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647625&r1=1647624&r2=1647625&view=diff
==
--- sis/site/trunk/content/contributor.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 17:47:53 2014
@@ -155,7 +155,7 @@ Committing changes{#commit}
Copies or displacements of files shall be done with the `svn copy` or `svn
move` command, respectively.
Be aware that not all IDE or graphical tools perform this action appropriately.
-*Always verify on the command-line*, at least the first times that a new tools
is used, by executing `svn status`.
+**Always verify on the command-line**, at least the first times that a new
tools is used, by executing `svn status`.
Files that have been moved or copied shall have a `A+` symbol in the left
margin, like below:
:::text
svn commit: r933797 - in /websites/staging/sis/trunk/content: ./ code-patterns.html contributor.html
Author: buildbot Date: Tue Dec 23 17:47:57 2014 New Revision: 933797 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/code-patterns.html websites/staging/sis/trunk/content/contributor.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 17:47:57 2014 @@ -1 +1 @@ -1647622 +1647625 Modified: websites/staging/sis/trunk/content/code-patterns.html == --- websites/staging/sis/trunk/content/code-patterns.html (original) +++ websites/staging/sis/trunk/content/code-patterns.html Tue Dec 23 17:47:57 2014 @@ -162,14 +162,14 @@ Consequently, when iterating over charac instead of invoking the getLogger(String) method provided by the java.util.logging.Logger class, we rather invoke the method provided by the apache.sis.util.logging.Logging class. The result is identical by default, -but the SIS method gives us a chance to redirect the logging to an other framework like Log4J if desired. -The difference between the SIS approach and other facades like common-logging is that -SIS uses the standard Java API (except for the above-cited getLogger method) instead than defining new API. +but the SIS method gives a chance to redirect the logging to an other framework like Log4J if desired. +The difference between the SIS approach and other facades like common-logging is that SIS uses the +standard Java API (except for the above-cited getLogger method) instead than defining a new API. Logger name The name given in argument to the getLogger(String) method is usually the package name of the class emitting the log messages, but not necessarily. In particular, we do not follow this convention if the class is located in an internal package (org.apache.sis.internal.*) since those packages are considered privates. -In such case, the logger name should be the package name of the public class that use the internal class. +In such cases, the logger name should be the package name of the public class that use the internal class. The reason for the above rule is that logger names are considered part of the public API, since developers use them for configuring their logging (verbosity, destination, etc.). Note that the "real" package name of the emitter is available by LogRecord.getSourceClassName(). Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 17:47:57 2014 @@ -182,7 +182,7 @@ and guidelines about the way SIS source Committing changes Copies or displacements of files shall be done with the svn copy or svn move command, respectively. Be aware that not all IDE or graphical tools perform this action appropriately. -Always verify on the command-line, at least the first times that a new tools is used, by executing svn status. +Always verify on the command-line, at least the first times that a new tools is used, by executing svn status. Files that have been moved or copied shall have a A+ symbol in the left margin, like below: D my-directory/the-old-filename A +my-directory/the-new-filename
svn commit: r1647622 - in /sis/site/trunk/content: build.mdtext code-patterns.mdtext contributor.mdtext source.mdtext
Author: desruisseaux
Date: Tue Dec 23 17:39:11 2014
New Revision: 1647622
URL: http://svn.apache.org/r1647622
Log:
Added more developer guidance.
Modified:
sis/site/trunk/content/build.mdtext
sis/site/trunk/content/code-patterns.mdtext
sis/site/trunk/content/contributor.mdtext
sis/site/trunk/content/source.mdtext
Modified: sis/site/trunk/content/build.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/build.mdtext?rev=1647622&r1=1647621&r2=1647622&view=diff
==
--- sis/site/trunk/content/build.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/build.mdtext [UTF-8] Tue Dec 23 17:39:11 2014
@@ -38,7 +38,7 @@ The Pack200 bundle is a file with the `.
Pack200 files are uncompressed by the `unpack200` command provided in JDK/JRE
installation.
However for users convenience, we provide a shell script for uncompressing and
launching the SIS
command line tool in a single step. That shell script, together with the
Pack200 file and other
-files (`README`, `LICENSE`, ) are bundled in a ZIP file created as below:
+files (`README`, `LICENSE`, etc.) are bundled in a ZIP file created as
below:
:::bash
mvn org.apache.sis.core:sis-build-helper:dist --non-recursive
Modified: sis/site/trunk/content/code-patterns.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/code-patterns.mdtext?rev=1647622&r1=1647621&r2=1647622&view=diff
==
--- sis/site/trunk/content/code-patterns.mdtext (original)
+++ sis/site/trunk/content/code-patterns.mdtext Tue Dec 23 17:39:11 2014
@@ -113,6 +113,44 @@ Consequently, when iterating over charac
+
+Logging{#logging}
+=
+
+Apache SIS uses the `java.util.logging` framework with one minor difference:
+instead of invoking the `getLogger(String)` method provided by the
`java.util.logging.Logger` class,
+we rather invoke the method provided by the `apache.sis.util.logging.Logging`
class.
+The result is identical by default,
+but the SIS method gives us a chance to redirect the logging to an other
framework like Log4J if desired.
+The difference between the SIS approach and other facades like
`common-logging` is that
+SIS uses the standard Java API (except for the above-cited `getLogger` method)
instead than defining new API.
+
+
+
+Logger name{#logger-name}
+-
+
+The name given in argument to the `getLogger(String)` method is usually the
package name of the class
+emitting the log messages, but not necessarily. In particular, we do not
follow this convention if the class
+is located in an internal package (`org.apache.sis.internal.*`) since those
packages are considered privates.
+In such case, the logger name should be the package name of the public class
that use the internal class.
+
+The reason for the above rule is that logger names are considered part of the
public API,
+since developers use them for configuring their logging (verbosity,
destination, etc.).
+Note that the "real" package name of the emitter is available by
`LogRecord.getSourceClassName()`.
+
+
+
+Logging level{#logging-level}
+-
+
+All logging at `Level.INFO` or above shall be targeted to users or
administrators, not to developers.
+In particular `Level.SEVERE` shall be reserved for critical errors that
compromise the application stability â
+it shall not be used for exceptions thrown while parsing user data (file or
database).
+
+
+
+
*[CRS]: Coordinate Reference System
*[JDBC]: Java DataBase Connectivity
*[OGC]: Open Geospatial Consortium
Modified: sis/site/trunk/content/contributor.mdtext
URL:
http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647622&r1=1647621&r2=1647622&view=diff
==
--- sis/site/trunk/content/contributor.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 17:39:11 2014
@@ -144,6 +144,28 @@ to work on the SIS branch targeting the
cd sis
mvn install
+The [source code](source.html) page provides tips for opening the files in an
IDE,
+and guidelines about the way SIS source code is organized.
+
+
+
+
+Committing changes{#commit}
+===
+
+Copies or displacements of files shall be done with the `svn copy` or `svn
move` command, respectively.
+Be aware that not all IDE or graphical tools perform this action appropriately.
+*Always verify on the command-line*, at least the first times that a new tools
is used, by executing `svn status`.
+Files that have been moved or copied shall have a `A+` symbol in the left
margin, like below:
+
+:::text
+D my-directory/the-old-filename
+A +my-directory/the-new-filename
+
+Using the proper SVN command is necessary for preserving the history,
pre
svn commit: r933796 - in /websites/staging/sis/trunk/content: ./ build.html code-patterns.html contributor.html source.html
Author: buildbot Date: Tue Dec 23 17:39:17 2014 New Revision: 933796 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/build.html websites/staging/sis/trunk/content/code-patterns.html websites/staging/sis/trunk/content/contributor.html websites/staging/sis/trunk/content/source.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 17:39:17 2014 @@ -1 +1 @@ -1647565 +1647622 Modified: websites/staging/sis/trunk/content/build.html == --- websites/staging/sis/trunk/content/build.html (original) +++ websites/staging/sis/trunk/content/build.html Tue Dec 23 17:39:17 2014 @@ -110,7 +110,7 @@ from the SIS project root: Pack200 files are uncompressed by the unpack200 command provided in JDK/JRE installation. However for users convenience, we provide a shell script for uncompressing and launching the SIS command line tool in a single step. That shell script, together with the Pack200 file and other -files (README, LICENSE, ) are bundled in a ZIP file created as below: +files (README, LICENSE, etc.) are bundled in a ZIP file created as below: mvn org.apache.sis.core:sis-build-helper:dist --non-recursive Modified: websites/staging/sis/trunk/content/code-patterns.html == --- websites/staging/sis/trunk/content/code-patterns.html (original) +++ websites/staging/sis/trunk/content/code-patterns.html Tue Dec 23 17:39:17 2014 @@ -99,6 +99,11 @@ Loop over character sequences using code points +Logging +Logger name +Logging level + + Referencing @@ -150,6 +155,28 @@ Consequently, when iterating over charac i += Character.charCount(c); } + + +Logging +Apache SIS uses the java.util.logging framework with one minor difference: +instead of invoking the getLogger(String) method provided by the java.util.logging.Logger class, +we rather invoke the method provided by the apache.sis.util.logging.Logging class. +The result is identical by default, +but the SIS method gives us a chance to redirect the logging to an other framework like Log4J if desired. +The difference between the SIS approach and other facades like common-logging is that +SIS uses the standard Java API (except for the above-cited getLogger method) instead than defining new API. +Logger name +The name given in argument to the getLogger(String) method is usually the package name of the class +emitting the log messages, but not necessarily. In particular, we do not follow this convention if the class +is located in an internal package (org.apache.sis.internal.*) since those packages are considered privates. +In such case, the logger name should be the package name of the public class that use the internal class. +The reason for the above rule is that logger names are considered part of the public API, +since developers use them for configuring their logging (verbosity, destination, etc.). +Note that the "real" package name of the emitter is available by LogRecord.getSourceClassName(). +Logging level +All logging at Level.INFO or above shall be targeted to users or administrators, not to developers. +In particular Level.SEVERE shall be reserved for critical errors that compromise the application stability â +it shall not be used for exceptions thrown while parsing user data (file or database). Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 17:39:17 2014 @@ -100,7 +100,8 @@ effective computer programming. The SIS library modules -Fetching and editing source code +Fetching and editing source code +Committing changes Configuring Subversion properties @@ -176,10 +177,24 @@ mvn install +The source code page provides tips for opening the files in an IDE, +and guidelines about the way SIS source code is organized. +Committing changes +Copies or displacements of files shall be done with the svn copy or svn move command, respectively. +Be aware that not all IDE or graphical tools perform this action appropriately. +Always verify on the command-line, at least the first times that a new tools is used, by executing svn status. +Files that have been moved or copied shall have a A+ symbol in the left margin, like below: +D my-directory/the-old-filename +A +my-directory/the-new-filename + + + +Using the proper SVN command is necessary for preserving the history, preserving the SVN properties, +and consuming less space on the Apache server h
svn commit: r933764 - in /websites/staging/sis/trunk/content: ./ code-patterns.html contributor.html
Author: buildbot Date: Tue Dec 23 12:36:07 2014 New Revision: 933764 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/code-patterns.html websites/staging/sis/trunk/content/contributor.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 12:36:07 2014 @@ -1 +1 @@ -1647504 +1647565 Modified: websites/staging/sis/trunk/content/code-patterns.html == --- websites/staging/sis/trunk/content/code-patterns.html (original) +++ websites/staging/sis/trunk/content/code-patterns.html Tue Dec 23 12:36:07 2014 @@ -106,12 +106,11 @@ Never explicitely swap ordinates for axis order The axis order issue causes lot of confusion, and developers are sometime tempted to swap their ordinate values in order to comply with some expected axis ordering. -It should never be necessary, since the Apache SIS referencing engine manages axis order transparently - provided that +It should never be necessary, since the Apache SIS referencing engine manages axis order transparently â provided that the Coordinate Reference System (CRS) definition is accurate. If a code needs to swap ordinates, this is probably an indication that the CRS has not been properly defined. Instead than patching the coordinate values, try to make sure that the Source CRS (associated to the original data) and the Target CRS (the coordinate space where to perform the -work) are properly defined, and let the referencing engine performs the conversion from the source to the target CRS. -For example when fetching the CRS, make sure that the proper boolean value is given to the CRS.forCode(â¦) method. +work) are properly defined, and let the referencing engine performs the conversion from the source to the target CRS. Coverages Recommended code pattern when using the sis-coverage module. Georeference images with affine transforms, not bounding boxes Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 12:36:07 2014 @@ -185,40 +185,45 @@ Developers can specify default propertie Open ~/.subversion/config in an editor, where ~ is the user home directory. Set the enable-auto-props value to yes. - -Scroll down to the [auto-props] section and add the following lines: -*.java = svn:mime-type=text/plain;svn:eol-style=native -*.sql= svn:mime-type=text/plain;svn:eol-style=native -*.txt= svn:mime-type=text/plain;svn:eol-style=native -*.properties = svn:mime-type=text/plain;svn:eol-style=native -*.xml= svn:mime-type=text/xml;svn:eol-style=native -*.xsd= svn:mime-type=text/xml;svn:eol-style=native -*.sld= svn:mime-type=text/xml;svn:eol-style=native -*.gml= svn:mime-type=text/xml;svn:eol-style=native -*.xsl= svn:mime-type=text/xsl;svn:eol-style=native -*.html = svn:mime-type=text/html;svn:eol-style=native -*.xhtml = svn:mime-type=text/html;svn:eol-style=native -*.css= svn:mime-type=text/css;svn:eol-style=native -*.bat= svn:eol-style=CRLF -*.sh = svn:eol-style=native;svn:executable -*.bmp= svn:mime-type=image/bmp -*.png= svn:mime-type=image/png -*.jpg= svn:mime-type=image/jpeg -*.jpeg = svn:mime-type=image/jpeg -*.gif= svn:mime-type=image/gif -*.tif= svn:mime-type=image/tiff -*.tiff = svn:mime-type=image/tiff -*.zip= svn:mime-type=application/zip -*.utf= svn:mime-type=application/octet-stream -*.shp= svn:mime-type=application/octet-stream -*.shx= svn:mime-type=application/octet-stream -*.dbf= svn:mime-type=application/octet-stream -README = svn:mime-type=text/plain;svn:eol-style=native - - - - +Scroll down to the [auto-props] section and make sure to assign the appropriate +(usually native) value to the End Of Line (EOL) style of the files to be edited. +Below is an example of a portion of Subversion configuration file: +[miscellany] +enable-auto-props = yes + +# Section for configuring automatic properties. +# The file-name-pattern can contain wildcards such as '*' and '?'. +# All entries which match will be applied to the file. +[auto-props] +*.java = svn:mime-type=text/plain;svn:eol-style=native +*.sql= svn:mime-type=text/plain;svn:eol-style=native +*.txt= svn:mime-type=text/plain;svn:eol-style=native +*.properties = svn:mime-type=text/plain;svn:eol-style=native +*.xml= svn:mime-type=text/xml;svn:eol-style=native +*.xsd= svn:mime-type=text/xml;svn:eol-style=native +*.sld
svn commit: r1647565 - in /sis/site/trunk/content: code-patterns.mdtext contributor.mdtext
Author: desruisseaux Date: Tue Dec 23 12:36:01 2014 New Revision: 1647565 URL: http://svn.apache.org/r1647565 Log: New formatting attempt. Modified: sis/site/trunk/content/code-patterns.mdtext sis/site/trunk/content/contributor.mdtext Modified: sis/site/trunk/content/code-patterns.mdtext URL: http://svn.apache.org/viewvc/sis/site/trunk/content/code-patterns.mdtext?rev=1647565&r1=1647564&r2=1647565&view=diff == --- sis/site/trunk/content/code-patterns.mdtext (original) +++ sis/site/trunk/content/code-patterns.mdtext Tue Dec 23 12:36:01 2014 @@ -35,12 +35,11 @@ Never explicitely swap ordinates for axi The [axis order issue](faq.html#axisOrder) causes lot of confusion, and developers are sometime tempted to swap their ordinate values in order to comply with some expected axis ordering. -It should never be necessary, since the Apache SIS referencing engine manages axis order transparently - provided that +It should never be necessary, since the Apache SIS referencing engine manages axis order transparently â provided that the Coordinate Reference System (CRS) definition is accurate. If a code needs to swap ordinates, this is probably an indication that the CRS has not been properly defined. Instead than patching the coordinate values, try to make sure that the _Source CRS_ (associated to the original data) and the _Target CRS_ (the coordinate space where to perform the work) are properly defined, and let the referencing engine performs the conversion from the source to the target CRS. -For example when fetching the CRS, make sure that the proper boolean value is given to the `CRS.forCode(â¦)` method. Modified: sis/site/trunk/content/contributor.mdtext URL: http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647565&r1=1647564&r2=1647565&view=diff == --- sis/site/trunk/content/contributor.mdtext [UTF-8] (original) +++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 12:36:01 2014 @@ -157,36 +157,46 @@ Developers can specify default propertie * Open `~/.subversion/config` in an editor, where `~` is the user home directory. * Set the `enable-auto-props` value to `yes`. - * Scroll down to the `[auto-props]` section and add the following lines: + * Scroll down to the `[auto-props]` section and make sure to assign the appropriate +(usually `native`) value to the End Of Line (EOL) style of the files to be edited. -:::text -*.java = svn:mime-type=text/plain;svn:eol-style=native -*.sql= svn:mime-type=text/plain;svn:eol-style=native -*.txt= svn:mime-type=text/plain;svn:eol-style=native -*.properties = svn:mime-type=text/plain;svn:eol-style=native -*.xml= svn:mime-type=text/xml;svn:eol-style=native -*.xsd= svn:mime-type=text/xml;svn:eol-style=native -*.sld= svn:mime-type=text/xml;svn:eol-style=native -*.gml= svn:mime-type=text/xml;svn:eol-style=native -*.xsl= svn:mime-type=text/xsl;svn:eol-style=native -*.html = svn:mime-type=text/html;svn:eol-style=native -*.xhtml = svn:mime-type=text/html;svn:eol-style=native -*.css= svn:mime-type=text/css;svn:eol-style=native -*.bat= svn:eol-style=CRLF -*.sh = svn:eol-style=native;svn:executable -*.bmp= svn:mime-type=image/bmp -*.png= svn:mime-type=image/png -*.jpg= svn:mime-type=image/jpeg -*.jpeg = svn:mime-type=image/jpeg -*.gif= svn:mime-type=image/gif -*.tif= svn:mime-type=image/tiff -*.tiff = svn:mime-type=image/tiff -*.zip= svn:mime-type=application/zip -*.utf= svn:mime-type=application/octet-stream -*.shp= svn:mime-type=application/octet-stream -*.shx= svn:mime-type=application/octet-stream -*.dbf= svn:mime-type=application/octet-stream -README = svn:mime-type=text/plain;svn:eol-style=native +Below is an example of a portion of Subversion configuration file: + +:::ini +[miscellany] +enable-auto-props = yes + +# Section for configuring automatic properties. +# The file-name-pattern can contain wildcards such as '*' and '?'. +# All entries which match will be applied to the file. +[auto-props] +*.java = svn:mime-type=text/plain;svn:eol-style=native +*.sql= svn:mime-type=text/plain;svn:eol-style=native +*.txt= svn:mime-type=text/plain;svn:eol-style=native +*.properties = svn:mime-type=text/plain;svn:eol-style=native +*.xml= svn:mime-type=text/xml;svn:eol-style=native +*.xsd= svn:mime-type=text/xml;svn:eol-style=native +*.sld= sv
svn commit: r1647504 - in /sis/site/trunk/content: contributor.mdtext index.mdtext source.mdtext
Author: desruisseaux Date: Tue Dec 23 08:25:49 2014 New Revision: 1647504 URL: http://svn.apache.org/r1647504 Log: Fix formatting issue in the new contributor page. Modified: sis/site/trunk/content/contributor.mdtext sis/site/trunk/content/index.mdtext sis/site/trunk/content/source.mdtext Modified: sis/site/trunk/content/contributor.mdtext URL: http://svn.apache.org/viewvc/sis/site/trunk/content/contributor.mdtext?rev=1647504&r1=1647503&r2=1647504&view=diff == --- sis/site/trunk/content/contributor.mdtext [UTF-8] (original) +++ sis/site/trunk/content/contributor.mdtext [UTF-8] Tue Dec 23 08:25:49 2014 @@ -159,34 +159,34 @@ Developers can specify default propertie * Set the `enable-auto-props` value to `yes`. * Scroll down to the `[auto-props]` section and add the following lines: -:::text -*.java = svn:mime-type=text/plain;svn:eol-style=native -*.sql= svn:mime-type=text/plain;svn:eol-style=native -*.txt= svn:mime-type=text/plain;svn:eol-style=native -*.properties = svn:mime-type=text/plain;svn:eol-style=native -*.xml= svn:mime-type=text/xml;svn:eol-style=native -*.xsd= svn:mime-type=text/xml;svn:eol-style=native -*.sld= svn:mime-type=text/xml;svn:eol-style=native -*.gml= svn:mime-type=text/xml;svn:eol-style=native -*.xsl= svn:mime-type=text/xsl;svn:eol-style=native -*.html = svn:mime-type=text/html;svn:eol-style=native -*.xhtml = svn:mime-type=text/html;svn:eol-style=native -*.css= svn:mime-type=text/css;svn:eol-style=native -*.bat= svn:eol-style=CRLF -*.sh = svn:eol-style=native;svn:executable -*.bmp= svn:mime-type=image/bmp -*.png= svn:mime-type=image/png -*.jpg= svn:mime-type=image/jpeg -*.jpeg = svn:mime-type=image/jpeg -*.gif= svn:mime-type=image/gif -*.tif= svn:mime-type=image/tiff -*.tiff = svn:mime-type=image/tiff -*.zip= svn:mime-type=application/zip -*.utf= svn:mime-type=application/octet-stream -*.shp= svn:mime-type=application/octet-stream -*.shx= svn:mime-type=application/octet-stream -*.dbf= svn:mime-type=application/octet-stream -README = svn:mime-type=text/plain;svn:eol-style=native +:::text +*.java = svn:mime-type=text/plain;svn:eol-style=native +*.sql= svn:mime-type=text/plain;svn:eol-style=native +*.txt= svn:mime-type=text/plain;svn:eol-style=native +*.properties = svn:mime-type=text/plain;svn:eol-style=native +*.xml= svn:mime-type=text/xml;svn:eol-style=native +*.xsd= svn:mime-type=text/xml;svn:eol-style=native +*.sld= svn:mime-type=text/xml;svn:eol-style=native +*.gml= svn:mime-type=text/xml;svn:eol-style=native +*.xsl= svn:mime-type=text/xsl;svn:eol-style=native +*.html = svn:mime-type=text/html;svn:eol-style=native +*.xhtml = svn:mime-type=text/html;svn:eol-style=native +*.css= svn:mime-type=text/css;svn:eol-style=native +*.bat= svn:eol-style=CRLF +*.sh = svn:eol-style=native;svn:executable +*.bmp= svn:mime-type=image/bmp +*.png= svn:mime-type=image/png +*.jpg= svn:mime-type=image/jpeg +*.jpeg = svn:mime-type=image/jpeg +*.gif= svn:mime-type=image/gif +*.tif= svn:mime-type=image/tiff +*.tiff = svn:mime-type=image/tiff +*.zip= svn:mime-type=application/zip +*.utf= svn:mime-type=application/octet-stream +*.shp= svn:mime-type=application/octet-stream +*.shx= svn:mime-type=application/octet-stream +*.dbf= svn:mime-type=application/octet-stream +README = svn:mime-type=text/plain;svn:eol-style=native Modified: sis/site/trunk/content/index.mdtext URL: http://svn.apache.org/viewvc/sis/site/trunk/content/index.mdtext?rev=1647504&r1=1647503&r2=1647504&view=diff == --- sis/site/trunk/content/index.mdtext [UTF-8] (original) +++ sis/site/trunk/content/index.mdtext [UTF-8] Tue Dec 23 08:25:49 2014 @@ -38,7 +38,7 @@ The latest release is 0.4, released Apri The version under development is 0.5-SNAPSHOT. * [Downloads](downloads.html) as a `zip` files, or as Maven dependencies. - * Developer guide ([English](book/en/developer-guide.html) | [French](book/fr/developer-guide.html)) - note that this is work in progress. + * Developer guide ([English](book/en/developer-guide.html) | [French](book/fr/developer-guide.html)) — note that this is work in progress. * [Command-line interface](command-line.ht
svn commit: r933736 - in /websites/staging/sis/trunk/content: ./ contributor.html index.html source.html
Author: buildbot Date: Tue Dec 23 08:25:53 2014 New Revision: 933736 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/contributor.html websites/staging/sis/trunk/content/index.html websites/staging/sis/trunk/content/source.html Propchange: websites/staging/sis/trunk/content/ -- --- cms:source-revision (original) +++ cms:source-revision Tue Dec 23 08:25:53 2014 @@ -1 +1 @@ -1647492 +1647504 Modified: websites/staging/sis/trunk/content/contributor.html == --- websites/staging/sis/trunk/content/contributor.html (original) +++ websites/staging/sis/trunk/content/contributor.html Tue Dec 23 08:25:53 2014 @@ -187,34 +187,36 @@ Developers can specify default propertie Set the enable-auto-props value to yes. Scroll down to the [auto-props] section and add the following lines: -:::text -.java = svn:mime-type=text/plain;svn:eol-style=native -.sql= svn:mime-type=text/plain;svn:eol-style=native -.txt= svn:mime-type=text/plain;svn:eol-style=native -.properties = svn:mime-type=text/plain;svn:eol-style=native -.xml= svn:mime-type=text/xml;svn:eol-style=native -.xsd= svn:mime-type=text/xml;svn:eol-style=native -.sld= svn:mime-type=text/xml;svn:eol-style=native -.gml= svn:mime-type=text/xml;svn:eol-style=native -.xsl= svn:mime-type=text/xsl;svn:eol-style=native -.html = svn:mime-type=text/html;svn:eol-style=native -.xhtml = svn:mime-type=text/html;svn:eol-style=native -.css= svn:mime-type=text/css;svn:eol-style=native -.bat= svn:eol-style=CRLF -.sh = svn:eol-style=native;svn:executable -.bmp= svn:mime-type=image/bmp -.png= svn:mime-type=image/png -.jpg= svn:mime-type=image/jpeg -.jpeg = svn:mime-type=image/jpeg -.gif= svn:mime-type=image/gif -.tif= svn:mime-type=image/tiff -.tiff = svn:mime-type=image/tiff -.zip= svn:mime-type=application/zip -.utf= svn:mime-type=application/octet-stream -.shp= svn:mime-type=application/octet-stream -.shx= svn:mime-type=application/octet-stream -.dbf= svn:mime-type=application/octet-stream -README = svn:mime-type=text/plain;svn:eol-style=native +*.java = svn:mime-type=text/plain;svn:eol-style=native +*.sql= svn:mime-type=text/plain;svn:eol-style=native +*.txt= svn:mime-type=text/plain;svn:eol-style=native +*.properties = svn:mime-type=text/plain;svn:eol-style=native +*.xml= svn:mime-type=text/xml;svn:eol-style=native +*.xsd= svn:mime-type=text/xml;svn:eol-style=native +*.sld= svn:mime-type=text/xml;svn:eol-style=native +*.gml= svn:mime-type=text/xml;svn:eol-style=native +*.xsl= svn:mime-type=text/xsl;svn:eol-style=native +*.html = svn:mime-type=text/html;svn:eol-style=native +*.xhtml = svn:mime-type=text/html;svn:eol-style=native +*.css= svn:mime-type=text/css;svn:eol-style=native +*.bat= svn:eol-style=CRLF +*.sh = svn:eol-style=native;svn:executable +*.bmp= svn:mime-type=image/bmp +*.png= svn:mime-type=image/png +*.jpg= svn:mime-type=image/jpeg +*.jpeg = svn:mime-type=image/jpeg +*.gif= svn:mime-type=image/gif +*.tif= svn:mime-type=image/tiff +*.tiff = svn:mime-type=image/tiff +*.zip= svn:mime-type=application/zip +*.utf= svn:mime-type=application/octet-stream +*.shp= svn:mime-type=application/octet-stream +*.shx= svn:mime-type=application/octet-stream +*.dbf= svn:mime-type=application/octet-stream +README = svn:mime-type=text/plain;svn:eol-style=native + + + Modified: websites/staging/sis/trunk/content/index.html == --- websites/staging/sis/trunk/content/index.html (original) +++ websites/staging/sis/trunk/content/index.html Tue Dec 23 08:25:53 2014 @@ -99,7 +99,7 @@ The latest release is 0.4, released Apri The version under development is 0.5-SNAPSHOT. Downloads as a zip files, or as Maven dependencies. -Developer guide (English | French) - note that this is work in progress. +Developer guide (English | French) â note that this is work in progress. Command-line interface for an overview of a command-line tool. http://cwiki.apache.org/confluence/display/SIS";>SIS Wiki for "drawing board" and roadmap. Recommended code patterns for writing more robust applications. Modified: websites/staging/sis/trunk/content/source.html == --- websites/staging/sis/trunk/content/source.html (original) +++ websites/staging/sis/trunk/content/source.html Tue Dec 23 08:25:53 2014 @@
