Just a thought, David, but is the opposite possibly true? That is, could you create a situation where the identity of names rather than a problem would be a solution and would create a situation where people would not have their code broken because the names were the same?
On 5/26/05, David Geary <[EMAIL PROTECTED]> wrote: > 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] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
