Be the first to post a text review of forcevelocity. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• forcevelocity Beta 26082008 file released: forcevelocity-beta-28082008-src.zip

  26/8/2008 - Beta release - IMPORTANT: To support 'request' scope Velocity tools the Velocity context is now scoped around each template execution - If you utlised the fact that all templates ran in the same scope to load macros you will need to use the 'templateLibraries' attribute to ensure you macros remain visible - Furthermore if you setup data (not recommended anyway) in your macro template using #set this needs to be wrapped in a macro and called from the templates - Completion of <include> and <exclude> Ant tasks elements, also see new <templateset> feature bellow - Added 'toolsConfiguration' attribute to point to a Velocity Tools XML configuration file (optional) - This allows custom Java classes to be written and utilised in the templates to reduce complexity - See http://velocity.apache.org/tools/devel/config.html - Also see SObjectHelperTool JavaDoc as an example Velocity Tool that uses the existing $SObject context variable - Added 'propertiesFile' attribute to point to a Velocity properties file (optional) - See http://velocity.apache.org/engine/devel/developer-guide.html#velocity_configuration_keys_and_values - Added 'templateLibraries' allows for Velicmacros to be defined in a single place and availble to all templates - See http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocimacros - Added <property> inner element - e.g. <property name="runtime.log" value="mylog.log"/> see above link under 'propertiesFile' - Added <data> inner element to inject external data into the template context - e.g. <data key="version" value="1.0"/> - See http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/config/Data.html - This element can occur as an immediate child of the Ant task itself or as a child of the <include> element in this case the data values will only be applied to templates executing against the SObject/s matched by the include - Added <templateset> inner element - This allows for templates to be logically grouped together. Groups can then be referenced via the new 'templates' attribute on the <include> element. Thus only those templates in the group will be run for SObject's matching the include. - Added new tool ApexParserTool to allow Apex source files to be used as context in the templates (this can be useful to implement sudo class inheritance, via proxy methods) - New Apex Source Object Model (ASOM) and Parser (com.plingtools.apex.code) (this uses JavaCC and current slightly modified Java 1.5 grammer to parse Apex Source code) - Note the parser only parses comments, class, field and method declartions presently, though the ASOM will emit method bodies

  posted 499 days ago

• forcevelocity Beta 26082008 file released: forcevelocity-beta-28082008-license.txt

  26/8/2008 - Beta release - IMPORTANT: To support 'request' scope Velocity tools the Velocity context is now scoped around each template execution - If you utlised the fact that all templates ran in the same scope to load macros you will need to use the 'templateLibraries' attribute to ensure you macros remain visible - Furthermore if you setup data (not recommended anyway) in your macro template using #set this needs to be wrapped in a macro and called from the templates - Completion of <include> and <exclude> Ant tasks elements, also see new <templateset> feature bellow - Added 'toolsConfiguration' attribute to point to a Velocity Tools XML configuration file (optional) - This allows custom Java classes to be written and utilised in the templates to reduce complexity - See http://velocity.apache.org/tools/devel/config.html - Also see SObjectHelperTool JavaDoc as an example Velocity Tool that uses the existing $SObject context variable - Added 'propertiesFile' attribute to point to a Velocity properties file (optional) - See http://velocity.apache.org/engine/devel/developer-guide.html#velocity_configuration_keys_and_values - Added 'templateLibraries' allows for Velicmacros to be defined in a single place and availble to all templates - See http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocimacros - Added <property> inner element - e.g. <property name="runtime.log" value="mylog.log"/> see above link under 'propertiesFile' - Added <data> inner element to inject external data into the template context - e.g. <data key="version" value="1.0"/> - See http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/config/Data.html - This element can occur as an immediate child of the Ant task itself or as a child of the <include> element in this case the data values will only be applied to templates executing against the SObject/s matched by the include - Added <templateset> inner element - This allows for templates to be logically grouped together. Groups can then be referenced via the new 'templates' attribute on the <include> element. Thus only those templates in the group will be run for SObject's matching the include. - Added new tool ApexParserTool to allow Apex source files to be used as context in the templates (this can be useful to implement sudo class inheritance, via proxy methods) - New Apex Source Object Model (ASOM) and Parser (com.plingtools.apex.code) (this uses JavaCC and current slightly modified Java 1.5 grammer to parse Apex Source code) - Note the parser only parses comments, class, field and method declartions presently, though the ASOM will emit method bodies

  posted 499 days ago

• forcevelocity Beta 26082008 file released: forcevelocity-beta-26082008.zip

  26/8/2008 - Beta release - IMPORTANT: To support 'request' scope Velocity tools the Velocity context is now scoped around each template execution - If you utlised the fact that all templates ran in the same scope to load macros you will need to use the 'templateLibraries' attribute to ensure you macros remain visible - Furthermore if you setup data (not recommended anyway) in your macro template using #set this needs to be wrapped in a macro and called from the templates - Completion of <include> and <exclude> Ant tasks elements, also see new <templateset> feature bellow - Added 'toolsConfiguration' attribute to point to a Velocity Tools XML configuration file (optional) - This allows custom Java classes to be written and utilised in the templates to reduce complexity - See http://velocity.apache.org/tools/devel/config.html - Also see SObjectHelperTool JavaDoc as an example Velocity Tool that uses the existing $SObject context variable - Added 'propertiesFile' attribute to point to a Velocity properties file (optional) - See http://velocity.apache.org/engine/devel/developer-guide.html#velocity_configuration_keys_and_values - Added 'templateLibraries' allows for Velicmacros to be defined in a single place and availble to all templates - See http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocimacros - Added <property> inner element - e.g. <property name="runtime.log" value="mylog.log"/> see above link under 'propertiesFile' - Added <data> inner element to inject external data into the template context - e.g. <data key="version" value="1.0"/> - See http://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/config/Data.html - This element can occur as an immediate child of the Ant task itself or as a child of the <include> element in this case the data values will only be applied to templates executing against the SObject/s matched by the include - Added <templateset> inner element - This allows for templates to be logically grouped together. Groups can then be referenced via the new 'templates' attribute on the <include> element. Thus only those templates in the group will be run for SObject's matching the include. - Added new tool ApexParserTool to allow Apex source files to be used as context in the templates (this can be useful to implement sudo class inheritance, via proxy methods) - New Apex Source Object Model (ASOM) and Parser (com.plingtools.apex.code) (this uses JavaCC and current slightly modified Java 1.5 grammer to parse Apex Source code) - Note the parser only parses comments, class, field and method declartions presently, though the ASOM will emit method bodies

  posted 499 days ago

• File released: /forcevelocity/Beta 26082008/forcevelocity-beta-28082008-src.zip

  posted 500 days ago

• File released: /forcevelocity/Beta 26082008/forcevelocity-beta-28082008-license.txt

  posted 500 days ago

• File released: /forcevelocity/Beta 26082008/forcevelocity-beta-26082008.zip

  posted 500 days ago

• forcevelocity Alpha 28052008 file released: forcevelocity-alpha-28052008-license.txt

  28/5/2008 - Third alpha release - Bug fix for 'serverURL' attribute on Ant task, default is https://www.salesforce.com/services/Soap/u/12.0 specify full alternate SOAP end point, as per those seen in Force.com IDE

  posted 589 days ago

• forcevelocity Alpha 28052008 file released: forcevelocity-alpha-28052008-src.zip

  28/5/2008 - Third alpha release - Bug fix for 'serverURL' attribute on Ant task, default is https://www.salesforce.com/services/Soap/u/12.0 specify full alternate SOAP end point, as per those seen in Force.com IDE

  posted 589 days ago

• forcevelocity Alpha 28052008 file released: forcevelocity-alpha-28052008.zip

  28/5/2008 - Third alpha release - Bug fix for 'serverURL' attribute on Ant task, default is https://www.salesforce.com/services/Soap/u/12.0 specify full alternate SOAP end point, as per those seen in Force.com IDE

  posted 589 days ago

• File released: /forcevelocity/Alpha 28052008/forcevelocity-alpha-28052008.zip

  posted 589 days ago