For some time velocity engine 2.0 is out but the velocity tools is not upgraded yet.
As I understand it, velocity tools 3.0 will work with velocity engine 2.0.
The latstest in maven repo is velocitytools 2.0 but this one depends on velocity 1.6
Latest news is that you can just download velocity tools 3.0 SNAPSHOT
Note for Velocity Tools users: Velocity Tools 3.0 shall soon be released. Meanwhile, you are encouraged to use the Velocity Tools 3.x last snapshot (see Velocity Tools 3.x Upgrading notes).
And yes, velocity engine 2.0 is one of its dependencies:
velocity 2.0+ Required for core infrastructure, ClassTool, LinkTool, LoopTool, RenderTool and XmlTool
EDIT
The test build of Velocity Tools 3.0 is available:
No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Tools 3.0 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build.
Release notes:
https://dist.apache.org/repos/dist/dev/velocity/velocity-tools/3.0/release-notes.html
Distribution:
https://dist.apache.org/repos/dist/dev/velocity/velocity-tools/3.0/
Related
I see there are list active version of karate available.
Our team develop tool for reporting (reportportal.io) and our users are asking for support of various versions.
As far as i see, there is no back compatibility between 0.9.2 - 0.9.3 - 0.9.4 - 0.9.5RC5
support and track integrations for each of minor versions is overhead.
Could you please updated on any roadmap, ETA and strategy for version compatibility, so we can focus on 1 certain version.
thank you in advance.
Use 0.9.5.RC5 and the develop branch in GitHub. The plan is to release 0.9.5 final within a month.
After upgrading from Azure SDK 1.7 => 1.8, we're noticing that there are two classes of essentially the same thing:
Microsoft.WindowsAzure.Storage.CloudStorageAccount (v1.7)
Microsoft.WindowsAzure.CloudStorageAccount (v1.8)
Before we migrate over to 1.8 in code (we can still reference Azure SDK 1.7 and compile), does anyone know what the newer benefits are and if there is some sample code to use it? This is from the perspective of Azure Diagnostics, so start and stop On-Demand transfers.
Microsoft.WindowsAzure.Storage namespace is introduced with Storage Client Library 2.0, which comes with Azure SDK 1.8. But the Storage Client Library 1.7 also exists in SDK 1.8 for backward compatibility reasons. For more information on Storage Client Library 2.0, please refer to this blog post.
doesn't play framework 2.0.4 support some consoles?
when i was using 1.x, i could use the console "play eclipsify"
and "play dependencies" to fbconnect and fbgraph modules
but from when i chaged the version, it's not working.
then how can i connect those modules? i've no idea to do that
i think the new version doesn't support those consoles for modules
is it correct?
is the way totally different? if then please let me know.
also juz awhile ago i checked the 1.2.5 version
and there is no dependencies.yml and module folder
would you let me know what changed and how can i apply and adjust?
Thank you for your time
https://github.com/playframework/Play20/wiki/Play-2.0-for-Play-1.x-developers
check this out
and i wanna tell you some people who evaluate my question
what if there is no begginer who really want to learn and ask, how developing survives?
i hate reputations!
Yes, it's TOTALY different, although some ideas are the same, Play 2.x is quite new product (as stated in many topics and questions since many months), there's (fortunately) no backward compatibility between Play 1.x and 2.x!
When you'll visit Play 1.x (only) modules page the first thing you'll see will be that disclaimer:
These modules are for the Play 1.x series only. Play 2.0 modules can be hosted anywhere on any Ivy, Maven or Git repository. We will add a directory for them here shortly.
Thanx to Pere Villega you can also search for Play 2.0 for Java or Scala modules on PlayModules.net site, however you need carefully choose between Play 1.x and Play 2.x series.
For working with eclipse, check the Play's 2.0 IDE documentation.
I'm working on a cross-platform solution currently. The solution uses XmlMtomReader and XmlMtomWriter from .NET framework 3.0.
Now i need to know if these two classes (and all the nessasary infrastructure around them) are fully supported in Mono project from the porting-it-to-linux point of view. :)
You can check it on the mono status:
http://go-mono.com/status/
You can also check your code using the mono migration analyser
http://www.mono-project.com/MoMA
I checked they are currently not implemented
The APIs are available on the current Mono 2.6 preview, but they are not available on the 2.4 release (the current official release).
I would like to integrate Castle Windsor into a WCF project and have read that you can hook it up using the WcfIntegration facility but I am unable to find where to download the dll.
Can anyone help?
WCF Facility did not have an official release yet, as there are still few rough edges and issues we want to address before making the release. Your best option now is to either get the source using link provided in the other answer, or to get it from Horn website. The latter option is compiled against trunk version of other projects, so if you want to use released version of Windsor (2.1.1) you have to compile it yourself.
It's in NuGet now with all of the other 3.0 beta stuff.
Install-Package Castle.WcfIntegrationFacility
http://nuget.org/List/Packages/Castle.WcfIntegrationFacility
Update
Just to follow up, The one in nuget is targeted for Windsor 3.0 beta 1. I found out the hard way that some of the other facilities do not yet support 3.0 beta 1. Specifically, if you're using the NHibernate or AutoTx facilities, you need to stick with a WCF factility compiled for Windsor 2. The latest one seems to be the Jul 29 2011 commit from the git repository, available here.
This will have to suffice until the 3.0 versions of the other facilities are updated. It's already being discussed on the castle users group list.
https://svn.castleproject.org/svn/castle/Facilities/Wcf/trunk from http://www.castleproject.org/subversion.html you have to download the source and build it yourself apperently.