We might get around this by enabling wild-carded configPaths. Then
scan for struts-plugin-*.xml in addition to what we already do.
What do you think?
--
James Mitchell
678.910.8017
On Dec 7, 2006, at 11:23 PM, Don Brown wrote:
The only way we could do it is if we had a custom maven 2 plugin
that combined all the xml, and even then, we'd have to build in
conflict resolution capability. No, I think we should get rid of
struts-all.
Don
Wendy Smoak wrote:
On 11/28/06, Ted Husted <[EMAIL PROTECTED]> wrote:
So, should we even have a struts-all JAR then?
I haven't worked much with plugins, but I don't see how an -all jar
can work given that each plugin has a struts-plugin.xml file in the
root of the jar.
Don?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
