Hi Karl-Heinz,
the current situation is that if you haven't defined plugin versions, the
version as defined in Maven will be used. So if I use a different version
of Maven, other versions of the plugins might kick in with a different
result.
By moving it to the "packaging" plugin, at least
Hi Robert,
On 4/20/16 9:48 AM, Robert Scholte wrote:
https://issues.apache.org/jira/browse/MJAR-183 should also be good to do
now.
that is: *copy* the lifecycle from core to the plugin.
IIRC it was Igor who told me this was safe to do, Maven has a clear
strategy how to resolve lifecycle handlers
Hi Michael,
I have a custom theme, but what you have written doesn't work. It gives me:
[ERROR] ResourceManager : unable to find resource
'C:\test\src\site\asciidoc/macro.vm' in any resource loader.
Anyways, I think it's a nice feature, but I'll just leave it like this.
Thanks for the reply
20
If your parse.vm lives next to your template.vm, call #parse('parse.vm') and
your macro should be available to the rest. Though, I have not tried that.
You will probably have to create a custom skin. You should really create
complete sample project.
Michael
> Gesendet: Mittwoch, 20. April 2016 um
Indeed,
with MSITE 3.5.1 I can add my macro in a .vm file next to my documentation,
but since i have 50 modules in my project and they are require this macro
it kind of makes it unusable. I was hoping to have it declared in my theme
just once, and then reference it from every module.
2016-04-20 1
> Here's the test repo:
>
> https://github.com/ptahchiev/maven-velocity-macro
Cloned and tested. Upgrade to MSITE 3.5.1 and your pain will go away.
#parse/#include
has been resolved with DOXIASITETOOLS 1.7.1/MSITE 3.5.1.
Michael
> 2016-04-20 8:57 GMT+02:00 Petar Tahchiev :
>
> > Ok,
> >
> > h
+1
v3.0.0 is an excellent opportunity to do this I think!
/Anders
On Wed, Apr 20, 2016 at 9:48 AM, Robert Scholte
wrote:
> https://issues.apache.org/jira/browse/MJAR-183 should also be good to do
> now.
> that is: *copy* the lifecycle from core to the plugin.
> IIRC it was Igor who told me thi
https://issues.apache.org/jira/browse/MJAR-183 should also be good to do
now.
that is: *copy* the lifecycle from core to the plugin.
IIRC it was Igor who told me this was safe to do, Maven has a clear
strategy how to resolve lifecycle handlers, having definitions in both
Maven and the plugin
Here's the test repo:
https://github.com/ptahchiev/maven-velocity-macro
2016-04-20 8:57 GMT+02:00 Petar Tahchiev :
> 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
>
>
