[
https://issues.apache.org/jira/browse/VELOCITY-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-963.
---
Assignee: Claude Brisson
Resolution: Won't Fix
> Incompatible API changes in 2.x
>
[
https://issues.apache.org/jira/browse/VELOCITY-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705088#comment-17705088
]
Claude Brisson commented on VELOCITY-963:
-
Point #3 is already documented, as stated by the
[
https://issues.apache.org/jira/browse/VELOCITY-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-964:
Affects Version/s: 2.3
> Allow formal notation for block macros
>
[
https://issues.apache.org/jira/browse/VELOCITY-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-964:
Component/s: Engine
> Allow formal notation for block macros
>
[
https://issues.apache.org/jira/browse/VELOCITY-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson reassigned VELOCITY-964:
---
Assignee: Claude Brisson
> Allow formal notation for block macros
>
[
https://issues.apache.org/jira/browse/VELOCITY-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-964:
Description:
The syntax #@\{test} is not functional.
> Allow formal notation for
[
https://issues.apache.org/jira/browse/VELOCITY-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-964:
Priority: Minor (was: Major)
> Allow formal notation for block macros
>
Claude Brisson created VELOCITY-964:
---
Summary: Allow formal notation for block macros
Key: VELOCITY-964
URL: https://issues.apache.org/jira/browse/VELOCITY-964
Project: Velocity
Issue
[
https://issues.apache.org/jira/browse/VELOCITY-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705081#comment-17705081
]
Claude Brisson commented on VELOCITY-940:
-
PS: I open another issue for #@\{test} and #\{@test}
[
https://issues.apache.org/jira/browse/VELOCITY-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-940.
-
Fix Version/s: 2.4
Assignee: Claude Brisson
Resolution: Fixed
>
[
https://issues.apache.org/jira/browse/VELOCITY-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705080#comment-17705080
]
Claude Brisson commented on VELOCITY-940:
-
Velocimacros do support recursion. But there was a
[
https://issues.apache.org/jira/browse/VELOCITY-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705046#comment-17705046
]
Michael Osipov commented on VELOCITY-963:
-
Unless there is a bug or documentation deficit, this
[
https://issues.apache.org/jira/browse/VELOCITY-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705042#comment-17705042
]
Claude Brisson commented on VELOCITY-963:
-
IMO those are only points to document in the
[
https://issues.apache.org/jira/browse/VELOCITY-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-963:
Component/s: Documentation
(was: Engine)
> Incompatible API changes
arkanovicz closed pull request #17: Provide a flag to ignore exception when
template generator encounters…
URL: https://github.com/apache/velocity-engine/pull/17
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
arkanovicz closed pull request #3: Added the S3Resource Loader to pull velocity
templates from Amazon S3…
URL: https://github.com/apache/velocity-engine/pull/3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
arkanovicz commented on PR #3:
URL: https://github.com/apache/velocity-engine/pull/3#issuecomment-1484027944
Ok, let's close it right away, then.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
arkanovicz commented on PR #17:
URL: https://github.com/apache/velocity-engine/pull/17#issuecomment-1484026250
>> InvalidReferenceHandler
> That would mean a broader check including invalid method names etc,
And? I maintain that it's a typical use case for the
arkanovicz commented on PR #26:
URL: https://github.com/apache/velocity-engine/pull/26#issuecomment-1484022777
The PR has been merged to the 1.7.x branch. But I don't have neither the
time or the envy to release a 1.7.x version, so you'll have to use the SNAPSHOT
or join the Apache
arkanovicz merged PR #26:
URL: https://github.com/apache/velocity-engine/pull/26
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
arkanovicz closed pull request #21: [Backport] Velocity 931 update secure
classlist
URL: https://github.com/apache/velocity-engine/pull/21
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
arkanovicz commented on PR #21:
URL: https://github.com/apache/velocity-engine/pull/21#issuecomment-1484022148
Closing this PR, as it has been updated elsewhere.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
arkanovicz commented on PR #3:
URL: https://github.com/apache/velocity-engine/pull/3#issuecomment-1484021923
The `isSourceModified()` always returns false. So even as a contribution, it
looks rather incomplete. Let's leave it here for now...
--
This is an automated message from the
23 matches
Mail list logo
