svn commit: r1860994 - /velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml

[cb...@apache.org]

Author: cbrisson
Date: Mon Jun 10 23:32:57 2019
New Revision: 1860994

URL: http://svn.apache.org/viewvc?rev=1860994&view=rev
Log:
[engine][VELOCITY-917] Fix pom comment

Modified:
    velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml

Modified: velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml
URL: http://svn.apache.org/viewvc/velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml?rev=1860994&r1=1860993&r2=1860994&view=diff
==============================================================================
--- velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml (original)
+++ velocity/engine/branches/parser_experiments/velocity-engine-core/pom.xml Mon Jun 10 23:32:57 2019
@@ -31,16 +31,8 @@
     <name>Apache Velocity - Engine</name>
 
     <properties>
-        <!-- You can modify those properties to build a custom parser.
-             The parser.name property will be used to generate the class:
-               org.apache.velocity.runtime.parser.${parser.name}Parser
-             which you must specify at runtime using the parser.class Velocity property.
-             You'll have to skip the tests which for now don't work for custom parsers:
-               mvn -DskipTests package
-             and extract the parser class from the jar if you wish this custom parser to
-             cohexist with the standard one.
-             You're strongly advised to change the groupId and/or artifactId if you plan
-             to use the generated jar directly.
+        <!-- You should not directly modify those properties which define the behavior of the parser.
+             Instead, you should customize the velocity-custom-parser-example module to fit your own needs.
         -->
         <parser.debug>false</parser.debug>
         <parser.name>Standard</parser.name>