On 9/13/06, Ted Husted <[EMAIL PROTECTED]> wrote:
For 2.0.0, I think we should just go with the latter. It's only an example application, after all. Not that I'm volunteering, but would having a set of Maven archetypes for the different porlet containers make sense?
I think one archetype, which has profiles to include the files for the portlet container of choice, would work. We would probably need to move the portlet config files either into the core or more likely, a separate struts2-portlet jar (plugin? extension?) so we can copy them around at build time for both this example app, and when building from the archetype. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
