Followup: use the #evaluate Velocity macro in the skin Velocity emplate
Hi all guys, I invested some time on trying the upgrade and I miserably failed :( The fact is that I didn't get explicit warnings/errors, the macro was simply ignored and rendered as #evaluate String, with arguments. Can someone please, with more doxia background, help me on give a try? Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Aug 29, 2012 at 8:15 AM, Lukas Theussl ltheu...@apache.org wrote: FYI: I've had troubles trying to upgrade velocity beyond version 1.5: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 IIRC, the main problem was backward compatibility. It should be ok with current skin versions but that's not tested. HTH, -Lukas Hervé BOUTEMY wrote: Hi Simone, Velocity is a direct dependency of doxia-site-renderer [2] and maven- reporting-exec [3] and ultimately of maven-site-plugin. I had a look at m-site-p trunk sources and actual Velocity version is 1.5. For immediate tests, you can try to override Velocity dependency in your pom's m-site-p plugin configuration. And later, add a Jira issue and change dependency in m-site-p trunk if you know Velocity well and are sure this won't break actual user sites (using Velocity 1.5 implicitely). I added explicit Velocity version in r1378417. Regards, Hervé [2] http://maven.apache.org/doxia/doxia-sitetools/index.html [3] http://maven.apache.org/shared/maven-reporting-exec/ Le mardi 28 aoűt 2012 14:02:12 Simone Tripodi a écrit : Hi all guys, as per subject, before cutting the current fluido RC, Robert and I gave some tries to evaluate strings inside the skin template using the #evaluate Velocity macro[1] but with no success... I guess mainly because the used velocity engine is a previous version which doesn't support that yet, but my question is if someone can point me to the direction on how I can provide my help on performing that upgrade. TIA, all the best! -Simo [1] http://velocity.apache.org/engine/devel/vtl-reference-guide.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Followup: use the #evaluate Velocity macro in the skin Velocity emplate
Hi Simone, I will try to have a look if you create a JIRA with a test project that I can play with. No promises though, my velocity skills are quite rusty by now... -Lukas Simone Tripodi wrote: Hi all guys, I invested some time on trying the upgrade and I miserably failed :( The fact is that I didn't get explicit warnings/errors, the macro was simply ignored and rendered as #evaluate String, with arguments. Can someone please, with more doxia background, help me on give a try? Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Aug 29, 2012 at 8:15 AM, Lukas Theussl ltheu...@apache.org wrote: FYI: I've had troubles trying to upgrade velocity beyond version 1.5: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 IIRC, the main problem was backward compatibility. It should be ok with current skin versions but that's not tested. HTH, -Lukas Hervé BOUTEMY wrote: Hi Simone, Velocity is a direct dependency of doxia-site-renderer [2] and maven- reporting-exec [3] and ultimately of maven-site-plugin. I had a look at m-site-p trunk sources and actual Velocity version is 1.5. For immediate tests, you can try to override Velocity dependency in your pom's m-site-p plugin configuration. And later, add a Jira issue and change dependency in m-site-p trunk if you know Velocity well and are sure this won't break actual user sites (using Velocity 1.5 implicitely). I added explicit Velocity version in r1378417. Regards, Hervé [2] http://maven.apache.org/doxia/doxia-sitetools/index.html [3] http://maven.apache.org/shared/maven-reporting-exec/ Le mardi 28 aoűt 2012 14:02:12 Simone Tripodi a écrit : Hi all guys, as per subject, before cutting the current fluido RC, Robert and I gave some tries to evaluate strings inside the skin template using the #evaluate Velocity macro[1] but with no success... I guess mainly because the used velocity engine is a previous version which doesn't support that yet, but my question is if someone can point me to the direction on how I can provide my help on performing that upgrade. TIA, all the best! -Simo [1] http://velocity.apache.org/engine/devel/vtl-reference-guide.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: use the #evaluate Velocity macro in the skin Velocity emplate
FYI: I've had troubles trying to upgrade velocity beyond version 1.5: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 IIRC, the main problem was backward compatibility. It should be ok with current skin versions but that's not tested. HTH, -Lukas Hervé BOUTEMY wrote: Hi Simone, Velocity is a direct dependency of doxia-site-renderer [2] and maven- reporting-exec [3] and ultimately of maven-site-plugin. I had a look at m-site-p trunk sources and actual Velocity version is 1.5. For immediate tests, you can try to override Velocity dependency in your pom's m-site-p plugin configuration. And later, add a Jira issue and change dependency in m-site-p trunk if you know Velocity well and are sure this won't break actual user sites (using Velocity 1.5 implicitely). I added explicit Velocity version in r1378417. Regards, Hervé [2] http://maven.apache.org/doxia/doxia-sitetools/index.html [3] http://maven.apache.org/shared/maven-reporting-exec/ Le mardi 28 août 2012 14:02:12 Simone Tripodi a écrit : Hi all guys, as per subject, before cutting the current fluido RC, Robert and I gave some tries to evaluate strings inside the skin template using the #evaluate Velocity macro[1] but with no success... I guess mainly because the used velocity engine is a previous version which doesn't support that yet, but my question is if someone can point me to the direction on how I can provide my help on performing that upgrade. TIA, all the best! -Simo [1] http://velocity.apache.org/engine/devel/vtl-reference-guide.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: use the #evaluate Velocity macro in the skin Velocity emplate
Hi Simone, Velocity is a direct dependency of doxia-site-renderer [2] and maven- reporting-exec [3] and ultimately of maven-site-plugin. I had a look at m-site-p trunk sources and actual Velocity version is 1.5. For immediate tests, you can try to override Velocity dependency in your pom's m-site-p plugin configuration. And later, add a Jira issue and change dependency in m-site-p trunk if you know Velocity well and are sure this won't break actual user sites (using Velocity 1.5 implicitely). I added explicit Velocity version in r1378417. Regards, Hervé [2] http://maven.apache.org/doxia/doxia-sitetools/index.html [3] http://maven.apache.org/shared/maven-reporting-exec/ Le mardi 28 août 2012 14:02:12 Simone Tripodi a écrit : Hi all guys, as per subject, before cutting the current fluido RC, Robert and I gave some tries to evaluate strings inside the skin template using the #evaluate Velocity macro[1] but with no success... I guess mainly because the used velocity engine is a previous version which doesn't support that yet, but my question is if someone can point me to the direction on how I can provide my help on performing that upgrade. TIA, all the best! -Simo [1] http://velocity.apache.org/engine/devel/vtl-reference-guide.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: use the #evaluate Velocity macro in the skin Velocity emplate
Please also include: velocity.properties specifically we'll need all macro library specifications e.g. velocimacro.library = VM_global_library.vm any .vm macros and more specifically the macro libraries VM_global_library.vm Merci, Martin __ Note de déni et de confidentialité Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: herve.bout...@free.fr To: dev@maven.apache.org Subject: Re: use the #evaluate Velocity macro in the skin Velocity emplate Date: Wed, 29 Aug 2012 03:45:43 +0200 Hi Simone, Velocity is a direct dependency of doxia-site-renderer [2] and maven- reporting-exec [3] and ultimately of maven-site-plugin. I had a look at m-site-p trunk sources and actual Velocity version is 1.5. For immediate tests, you can try to override Velocity dependency in your pom's m-site-p plugin configuration. And later, add a Jira issue and change dependency in m-site-p trunk if you know Velocity well and are sure this won't break actual user sites (using Velocity 1.5 implicitely). I added explicit Velocity version in r1378417. Regards, Hervé [2] http://maven.apache.org/doxia/doxia-sitetools/index.html [3] http://maven.apache.org/shared/maven-reporting-exec/ Le mardi 28 août 2012 14:02:12 Simone Tripodi a écrit : Hi all guys, as per subject, before cutting the current fluido RC, Robert and I gave some tries to evaluate strings inside the skin template using the #evaluate Velocity macro[1] but with no success... I guess mainly because the used velocity engine is a previous version which doesn't support that yet, but my question is if someone can point me to the direction on how I can provide my help on performing that upgrade. TIA, all the best! -Simo [1] http://velocity.apache.org/engine/devel/vtl-reference-guide.html http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org