filed a jira issue at https://issues.apache.org/jira/browse/WICKET-715
On 7/3/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
then just see if we do it for the next version. On 7/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Changing the case of Java files tends to cause pain on Windows systems, > > because they're case-insensitive. We're almost guaranteed to have people > > with strange ClassNotFoundExceptions if we go and do this. > > > > It's yet another API change just before we release 1.3.0. > > > > If we fix the class names, we should also fix the method names. There's > > a lot of inconsistency at the moment, and this would cause an awful lot > > of API breakage. > > > > It would make sense to use "Javascript" everywhere, as "JavaScript" is > > one word, so when you CamelCase it, it should all go lower. > > > > Otherwise, if you have a "JavaScriptHandler", is it a ScriptHandler for > > Java, or a Handler for JavaScript? > > > > Anyway, there's a bunch of stuff we'd need to fix, including > > HeaderContributor.forJavaScript(), etc. etc. > > > > I don't think we want to do that this close to a 1.3 release. I imagine > > it'd be a faff for the upcoming Wicket book, too. > > I agree. The book isn't much of a problem in this case, but I know > from some previous renames (around 1.1 if I recall correctly) that it > can be a pain especially for Windows users. Annoying as these little > naming inconsistencies can be, I'm not sure if it's is worth the pain. > > Eelco >
