> For my curiosity, reason for -1 on the werkz additions (not
> that I was
> thinking about it, but....)
Its (unfortunately) very much tied into the way the plugin manager works and
vice-versa. And it'll disappear (or be much thinner) in maven2 anyway, as
none of the plugin handling is tied to Jelly any more.
>
> > There may be a problem here anyway because of the
> classloaders - so if
> they
> > are split, I'm not sure if you can use different versions across
> projects.
> Across one project or many? I was simply hoping we could
> split maven tags
> out, so that if a new tag is introduced in 1.1 and I'm on
> 1.0, assuming
> the tag change doesn't use 1.1 features, I can simply upgrade the jar.
I'm not exactly sure what'll happen - but I have a feeling forehead will
keep using the one in MAVEN_HOME/lib regardless. I may be wrong. I'm going
off the bad problems that come around when you use a different version of
jelly to that in MAVEN_HOME/lib.
> > I'm ok with this happening if that is considered and proven to work
> > ok,
> and
> > also as long as the implications for beanshell or whatever tag
> > libraries
> or
> > equivalent are also considered so code duplication is a
> minimum going
> > forward into supporting multiple scripting languages in maven2.
>
> BeanShell support in Jelly is busted from memory, so I'm not
> sure what the
> above means. Since the jelly tags are in a separate set of
> jars, I can't
> see any issues arising from classloader support that way, and
> the plan
> would be to have maven-tags in ${maven.home}/lib.
>
> I wouldn't know anything about Maven2.
Have a read about the stuff on the wiki (has been around for ages, but has
been updated more recently). Plugins will be able to be written in Java,
beanshell, Jelly and more.
Jelly tags shouldn't do any work - they should just wrap functionality (eg,
the reactor shouldn't be implemented in a jelly tag), so that other
implementations can do the same thing too. Most of the maven: ones already
farm off the work to MavenUtils or similar.
But then it gets weird - maven-tags depends on maven.jar (which is fine,
because maven.jar doesn't depend on the tags), but if your project is
importing maven-tags it might actually be using a newer version of maven
anyway via a dependency on maven.jar.
Something worth thinking about.
- Brett
