Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Claude Brisson
On 26/01/2017 19:45, Michael Osipov wrote: Am 2017-01-26 um 18:37 schrieb Claude Brisson: Now my question is: do you or someone else think that the OSGi missing meta-informations are a show stopper for the 2.0? Otherwise, my plan is to open JIRA issues for all those remarks, try to release

Velocity 2 press release announcement

2017-01-26 Thread Mike Kienenberger
It might be worthwhile to send a message to press@ to start the process of creating a velocity 2 press release. MyFaces Tobago is working through that process now, and while I am not directly involved, it appears that Sally will prepare a draft press release for you and someone from velocity

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Michael Osipov
Am 2017-01-26 um 17:54 schrieb Claude Brisson: On 26/01/2017 14:11, Michael Osipov wrote: [...] * StringUtils#normalizePath() can likely be replaced with Common IO's FilenameUtils#normalize() If we take this route, then we'll shade the commons-io class. Absolutely, they might be other spots

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Michael Osipov
Am 2017-01-26 um 18:37 schrieb Claude Brisson: Now my question is: do you or someone else think that the OSGi missing meta-informations are a show stopper for the 2.0? Otherwise, my plan is to open JIRA issues for all those remarks, try to release the RC6, and handle the issues in 2.0.1 or

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Claude Brisson
Now my question is: do you or someone else think that the OSGi missing meta-informations are a show stopper for the 2.0? Otherwise, my plan is to open JIRA issues for all those remarks, try to release the RC6, and handle the issues in 2.0.1 or 2.1. The OSGi thing is the only one I'm not

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Claude Brisson
On 26/01/2017 14:11, Michael Osipov wrote: [...] * StringUtils#normalizePath() can likely be replaced with Common IO's FilenameUtils#normalize() If we take this route, then we'll shade the commons-io class. * StringUtils#nullTrim() can be replaced with Commons Lang's StringUtils#trim() *

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Greg Huber
Ahh java, now seems so many different ways of doing the same thing Just importing a file, I also have standard utils. The path is the tricky one now, without testing it. value = FileUtils.readFileToString(new File( getProject().resolveFile(value)

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Greg Huber
Hello, I use the taxen task, and now have a local copy as its no longer supported. What would be an equivalent to .fileContentsToString(..) as its now missing? org.apache.velocity.util.StringUtils value = StringUtils.fileContentsToString(

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

2017-01-26 Thread Michael Osipov
Am 2017-01-26 um 04:39 schrieb Claude Brisson: A new test build of Velocity Engine 2.0 is available (RC6). No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.0 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and