[ x ] disable this feature by default, put instructions on how to enable it into component-not-found related exception messages [ ] leave it enabled by default
i like the idea of a debug deployment mode. if we get into profiles, i'd prefer it be kept in code and not introduce any kind of data store (particularly XML) for this. each deployment mode could just be a subclass of an AbstractDeployment base class which basically takes a Settings object and configures it. then picking your deployment would just be a matter of giving the deployment class you want to start with (the current string based configure method would be deprecated but select the right deployment class for compatibility). Eelco Hillenius wrote: > > [ x ] disable this feature by default, put instructions on how to enable > it > into component-not-found related exception messages > [ ] leave it enabled by default > > I've argued before that if it were up to me, deployment would be our > default. Lost that argument and that is fine, but I feel that debug > options such as there can give people the wrong ideas. > > One thing we might consider is to add a third deployment mode - > something like DEBUG - which would include this setting and e.g. the > outputMarkupClass setting[1] (which is a very useful tool that is > turned off by default). And/ or we could consider to have plugable > profiles rather than the two hard-coded ones. > > Eelco > > [1] > http://chillenious.wordpress.com/2007/06/20/locate-where-that-wicket-markup-comes-from/ > > -- View this message in context: http://www.nabble.com/-VOTE--disable-line-precise-error-reporting-by-default-tf4037146.html#a11475042 Sent from the Wicket - Dev mailing list archive at Nabble.com.
