On 3/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> We need to decide on a Maven groupId for Struts Action. Currently,
> we're using 'struts' but we've been asked to conform to the Maven 2
> repository structure and place our artifacts under org/apache/struts.
>
> My plan is to use org.apache.str
On 3/17/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> Any thoughts on grouping the Action 1 related modules together in some way?
Hmmm, that's going to depend on what you mean by Action 1 related
modules. Would Scripting and Flow fall into that category, or just
Action, Apps, EL, Extras, and Taglib
We need to decide on a Maven groupId for Struts Action. Currently,
we're using 'struts' but we've been asked to conform to the Maven 2
repository structure and place our artifacts under org/apache/struts.
My plan is to use org.apache.struts.action as the groupId.
As you can see with Shale, that