It's nice to know I'm not the only person seeing this. I'd ignore the
warnings, but the build terminates when it sees more complex JSTL than
simply a bean substitution.
I guess I'll look into Velocity. I'm aware of it, but have never
investigated.
Thanks!
-K
On 3/14/06 8:23 AM, "Wendy Smoak" <
On 3/14/06, Kathryn Huxtable <[EMAIL PROTECTED]> wrote:
> I should actually have asked where the lexical analysis is happening? I'm
> interested in where the file's text is broken up into tokens, as that's
> where escaping usually happens.
I believe this is done with Velocity: http://jakarta.apac
I should actually have asked where the lexical analysis is happening? I'm
interested in where the file's text is broken up into tokens, as that's
where escaping usually happens.
-K
On 3/14/06 8:06 AM, "Kathryn Huxtable" <[EMAIL PROTECTED]> wrote:
> Yes, I tried that. I also tried doubling the d
Yes, I tried that. I also tried doubling the dollar sign. Neither worked.
If the syntax looked like \${bean.property} I got a warning about an unknown
variable "bean.property" and I got \${bean.property} in my output. Likewise
with the doubled dollar sign.
I could live with the warning, but it di
Have you tried '\'? I don't know if it's work but it is usually the
convention in the Java world.
On 3/13/06, Kathryn Huxtable <[EMAIL PROTECTED]> wrote:
> I posted this last week and never got a response.
>
> I'm creating an archetype for my team to use in creating new projects. I
> want to inclu
I posted this last week and never got a response.
I'm creating an archetype for my team to use in creating new projects. I
want to include a sample jsp file with jstl tags. The archetype creates just
fine, but when I do a "mvn archetype:create" command it blows up on the
${empty bean.property
