Artifact just defines taglibs and that works from war I believe? I think all 3
use cases are covered (call a jelly tag, attain a goal, manipulate a property).
Cheers,
Brett
Quoting Felipe Leme <[EMAIL PROTECTED]>:
> Hi Carlos,
>
> On Wed, 1 Sep 2004 20:25:18 +0200, "Carlos Sanchez"
> <[EMAIL PR
Hi Carlos,
On Wed, 1 Sep 2004 20:25:18 +0200, "Carlos Sanchez" <[EMAIL PROTECTED]> wrote:
> Not sure but I think that you have to load the plugin before you can use the
> taglib, as it happens with the plugin properties.
Yes, I think so.
> You can use attainGoal, maven:get,...
It worked when
; From: Felipe Leme [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 01, 2004 5:13 PM
> To: Maven Developers List
> Subject: RE: Reusing a Jelly taglibs
>
> Vincent,
>
> I was already using a namespace, but looks like maven was not
> loading the plugin that defined the
Vincent,
I was already using a namespace, but looks like maven was not loading the plugin that
defined the taglib. If I called a goal from that plugin (using ) before
using the tag, it worked though. That might be some issue in my code though, as maven
executes all plugin.jellys and plugin.prop
septembre 2004 16:27
> To: [EMAIL PROTECTED]
> Subject: Reusing a Jelly taglibs
>
> Hi all,
>
> Is it possible to use (inside a plugin or in maven.xml) a Jelly taglib
> defined somewhere else?
>
> For instance, let's say a have a plugin A below:
>
>
Hi all,
Is it possible to use (inside a plugin or in maven.xml) a Jelly taglib defined
somewhere else?
For instance, let's say a have a plugin A below:
If I try to access taglibA from a plugin B, it doesn't work:
My undest
