Ok,
here's what I've tried:
= NOMACRO: I create a file properties.vm, right next to my index.adoc.vm
and inside it I put
#set($a = "Petar")
$a
then inside my index.adoc.vm I put
#parse("properties.vm")
[ERROR] Max recursion depth reached (10) File stack: >
C:\wo
Am 2016-04-20 um 08:35 schrieb Petar Tahchiev:
Hi Michael,
I had a chat with Herve last night, and he mentioned this is actually not
possible. If one wants to use velocity macros one must put it in the site
(if you put them in your theme it will not work). Which is a shame, as I
have a project w
Hi Michael,
I had a chat with Herve last night, and he mentioned this is actually not
possible. If one wants to use velocity macros one must put it in the site
(if you put them in your theme it will not work). Which is a shame, as I
have a project with 50 submodules and each module requires #myMac
Am 2016-04-19 um 20:26 schrieb Petar Tahchiev:
Hello,
I'm asking this question here, as I don't really see the answer in the
documentation or anywhere else on the internet. If you have a website
document: src/site/asciidoc/index.adoc.vm and you use a velocity macro in
it:
# myMacro()
I know d
On Tue, 19 Apr 2016 21:40:04 +0200, Karl Heinz Marbaise
wrote:
Hi Robert,
On 4/19/16 9:27 PM, Robert Scholte wrote:
Hi,
Not sure if this is the right moment,
why not? 3.0.0 is a good moment or may be exactly the right time for
such change
> but I'd like to make finalName
reado
On Tue, Apr 19, 2016 at 9:27 PM, Robert Scholte
wrote:
> Hi,
>
> Not sure if this is the right moment, but I'd like to make finalName
> readonly for all packaging plugins.
> The reason: for some new features I probably need to know the name of the
> generated (main) artifact, preferably without h
Hi Robert,
On 4/19/16 9:27 PM, Robert Scholte wrote:
Hi,
Not sure if this is the right moment,
why not? 3.0.0 is a good moment or may be exactly the right time for
such change
> but I'd like to make finalName
readonly for all packaging plugins.
Ok...have created an appropriate issu
Hi,
Not sure if this is the right moment, but I'd like to make finalName
readonly for all packaging plugins.
The reason: for some new features I probably need to know the name of the
generated (main) artifact, preferably without having to analyze plugin
configuration. Instead, users should
Hi Karl,
Great. I saw you've fixed MJAR-209, thanks!
Before rolling a new release, do you think we could get some tests for
MJAR-199 as well? I just looked briefly, but I'm concerned how this will
work with the instructions on [1]. Would it still be type 'test-jar' but
with a classifier as well?
Based on the things which are missing i CANCEL the VOTE...
On 4/17/16 12:49 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 16 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12334171
There are still a couple of issues left in JIRA:
https://issues.apach
Hi Anders,
On 4/18/16 10:31 AM, Anders Hammar wrote:
I'm -1 as I think we should handle MJAR-209 [1] in v3.0.0. Sorry for not
pushing that earlier, but I didn't know a release was imminent.
I think it has become time cause last release is a long time ago...
04. March 2015 ...
but you are rig
Hello,
I'm asking this question here, as I don't really see the answer in the
documentation or anywhere else on the internet. If you have a website
document: src/site/asciidoc/index.adoc.vm and you use a velocity macro in
it:
# myMacro()
I know doxia will process the velocity and it works fine,
12 matches
Mail list logo
