Would it make sense to rename the current struts/tiles directory struts/struts-tiles and it would eventually serve as the glue between struts/core and struts/tiles? For the time being it would have a copy of tiles but eventually struts would use the stand-alone tiles jar.
The struts-tiles bridge code could also move back into core since supporting tiles could be considered a core feature of struts at this point, the same way supporting validator is core. > -----Original Message----- > From: David Geary [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 26, 2005 4:59 PM > To: Struts Developers List > Subject: [Tiles] Subproject Questions > > Ted Husted has convinced me that Tiles should, afterall, be a Struts > subproject. But I have a couple of questions. First, should I put > this in a directory called struts/tiles? There's already a Struts top- > level directory named tiles, so reusing that name might cause > confusion. Should I name it tiles-standalone, or something like that? > > Second, I'm not sure about packages. Right now, I've got > org.apache.tiles instead of the original org.apache.struts.tiles, but > of course, that will break existing code. OTOH, if I switch back to > the original package names, then we run the risk of clashing with the > Struts packages. > > Thoughts? > > > david > > --------------------------------------------------------------------- > 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]
