castleproject / nvelocity Goto Github PK

The on_success script is used to publish the NuGet package to nuget.org, we only need it to run on Windows, it also fails on Linux anyway:

...
Running "on_success" scripts
if ($env:APPVEYOR_REPO_TAG -eq "true") {
  nuget push ".\build\NVelocity.${env:APPVEYOR_BUILD_VERSION}.nupkg" -ApiKey $env:NUGET_API_KEY -Source https://api.nuget.org/v3/index.json
}
File does not exist (.\build\NVelocity.1.2.0.nupkg).
Command exited with code 1
Build failed

This is the first issue in this new repository to kick start NVelocity development again, it stems from castleproject-deprecated/MonoRail#27. I've imported the source code (minus the cruft).

First things first, let's get a .NET Framework build going again with the new .NET tooling, the project files in the repository are for Visual Studio 2010.

/cc @phillip-haydon

According to http://velocity.apache.org/engine/devel/user-guide.html#if-elseif-else

When you wish to include text immediately following a #else directive you will need to use curly brackets immediately surrounding the directive to differentiate it from the following text. (Any directive can be delimited by curly brackets, although this is most useful for #else).

But it doesn't work.

var context = new VelocityContext();
var engine = new VelocityEngine();
var sw = new StringWriter();
var template = "#if(1 == 1)it's true!#{else}it's not!#end";
engine.Init();
engine.Evaluate(context, sw, "", template);
var expected = "it's true!";
Assert.AreEqual(expected, sw.ToString()); // <-- fails, actual (wrong) result is "it's true!#{else}it's not!"

Initial release of rebooted NVelocity. The primary driving force of this release is to bring support for .NET Standard 2.0 for people who still use NVelocity, and those who wish to use it in new projects.

@castleproject/committers your input?

NuGet outputs the following warning during packaging. We should change to specify the license.

WARNING: <licenseUrl> element will be deprecated,please consider switching to specifying the license in the package. Learn more: https://aka.ms/deprecateLicenseUrl.

While here it would be good to reinstate the Castle logo on the package, I know the icon can now be embedded into the package which is definitely much better than pointing to the web site.

Can I submit a PR to get this working the same way Windsor does in terms of builds?

how can i write the Unparsed Content like in java #[[]]#

So far I can find no way of getting Nvelocity to support the text variants of the logical operators. Here are some examples from velocity:

version 1.1.1

Current situation:

• This repository's README.me says:

  More information about NVelocity can be found at http://www.castleproject.org/

• On the website, NVelocity is not (yet?) listed as an active project. Knowing that NVelocity used to be part of MonoRail, that's where I'm taking a look next, only to find that the MonoRail V2 documentation is back on GitHub!

• And there it is that we finally find the documentation on NVelocity, however it is written in the context of MonoRail, which probably no longer matches the current situation / use case?

Suggestions:

• Add a docs directory to this repository, which is where the documentation will live for the time being.

• Use https://github.com/castleproject-deprecated/MonoRail/blob/master/MR2/docs/nvelocity.md as a template for some new documentation.

• Update the repository's main README.md to link to docs/README.md instead of the website.

• Update the website: Add NVelocity as an active project (castleproject/castleproject.org#4 is a first small step in that direction, but by itself not sufficient) on the website and have its documentation link point to docs/README.md here.