> <project>
>
> <extend>template:jelly-tag-library</extend>
>
Oooh....very cool. I can't comment on the technical viability of the
patches or what not, but as a user, this would be awesome. Especially
cool would be if I'm using say both maven and Turbine on the same
project, something like multiple inheritance:
<project>
<extend>template:maven</extend>
<extend>template:turbine</extend>
</project>
The major, though somewhat trivial, I suppose, thing this would save is
keeping track of all the various dependencies. So, really, perhaps what
I'm thinking of is more:
<project>
<extend>template:company-project</extend>
<import-depedencies
project="template:maven"
mask="export"/>
<import-depedencies
project="template:turbine"
mask="export"/>
The mask thing then being something like the war.bundle.jar property
that would have to be true for the dependencies which are required run
the imported project, leaving out the compile/test dependencies.
This type of thing could very well be done a better way, I'm just
thinking that this type of functionality would be cool.
Perhaps something like:
<dependency>
<id>turbine</id>
<version>2.1</version>
<properties>
<import-dependences>template:turbine</import-dependencies>
</properties>
</dependency>
Dunno. Just some suggestions.
Thanks,
Stephen
--
To unsubscribe, e-mail: <mailto:turbine-maven-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-maven-dev-help@;jakarta.apache.org>
