Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-09 Thread Sean Schofield
> But does MyFaces depend on Tomahawk components at compile time? This is > the circular link that has me concerned. No, that part is different. Its a one-way dependency. I guess there is nothing that Maven2 can do for you then. > Don Sean ---

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-09 Thread Don Brown
Sean Schofield wrote: Agreed. I handled this in scripting by adding an element to each dependency declaration marking it as optional or not. I used this new element to create the release notes (combined with changes.xml) as well as create website docs. Perhaps we could do something similar i

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-09 Thread Sean Schofield
> Agreed. I handled this in scripting by adding an element to each dependency > declaration marking it as optional or not. > I used this new element to create the release notes (combined with > changes.xml) as well as create website docs. > Perhaps we could do something similar in Maven 2. Ma

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Antonio Petrelli
Greg Reddin ha scritto: But I'm not sure if Tiles-Struts Action integration will happen in the Tiles Subproject or as a sub-subproject of Action :-) Maybe in a sub-subproject of Tiles :-P - To unsubscribe, e-mail: [EMAIL PROT

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Greg Reddin
On Apr 6, 2006, at 2:52 PM, Don Brown wrote: With the new restructuring, we have three official Struts subprojects - Action, Shale, and Tiles. Currently, Tiles depends on Action 1, and through Action 1's EL artifact, Action 1 depends on Tiles. I propose we remove this circular dependenc

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Don Brown
Craig McClanahan wrote: It's ok to keep it the way you propose, I guess ... but hard versus soft runtime dependencies is worth some thought across all of the artifacts, as we are reorganizing things. Agreed. I handled this in scripting by adding an element to each dependency declaration markin

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Craig McClanahan
On 4/6/06, Don Brown <[EMAIL PROTECTED]> wrote: > > Craig McClanahan wrote: > > On 4/6/06, Don Brown <[EMAIL PROTECTED]> wrote: > >> With the new restructuring, we have three official Struts subprojects - > >> Action, Shale, and Tiles. Currently, Tiles > >> depends on Action 1, and through Action

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Don Brown
Craig McClanahan wrote: On 4/6/06, Don Brown <[EMAIL PROTECTED]> wrote: With the new restructuring, we have three official Struts subprojects - Action, Shale, and Tiles. Currently, Tiles depends on Action 1, and through Action 1's EL artifact, Action 1 depends on Tiles. I propose we remove thi

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Craig McClanahan
On 4/6/06, Don Brown <[EMAIL PROTECTED]> wrote: > > With the new restructuring, we have three official Struts subprojects - > Action, Shale, and Tiles. Currently, Tiles > depends on Action 1, and through Action 1's EL artifact, Action 1 depends > on Tiles. > > I propose we remove this circular dep

Re: [Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread James Mitchell
Definitely +1 -- James Mitchell On Apr 6, 2006, at 3:52 PM, Don Brown wrote: With the new restructuring, we have three official Struts subprojects - Action, Shale, and Tiles. Currently, Tiles depends on Action 1, and through Action 1's EL artifact, Action 1 depends on Tiles. I propo

[Proposal] Remove Tiles dependency in Action 1

2006-04-06 Thread Don Brown
With the new restructuring, we have three official Struts subprojects - Action, Shale, and Tiles. Currently, Tiles depends on Action 1, and through Action 1's EL artifact, Action 1 depends on Tiles. I propose we remove this circular dependency and move the Tiles-dependent EL tags into Tiles its