[jsr-314-open] [jsf2next] PROJECT_STAGE system property configuration
Andy Schwartz
andy.schwartz at oracle.com
Thu Jan 14 15:15:22 EST 2010
Cay Horstmann wrote:
> It is certainly reasonable to expect dev tools to set the project
> stage to development. I'll ping the NetBeans folks and Ludo who does
> the Eclipse plugin.
>
Great, thanks Cay. Please pass along any thoughts that they have on the
topic. We still may need some spec changes/additions to make this
possible/easy.
> Still, it's interesting that your colleague thinks that deployers
> can't be trusted set the project stage. With GlassFish, for example, a
> deployer has to do a whole bunch of other stuff, such as set the
> server password to something other than the default :-)
Hah, fun stuff. Yeah, clearly there is a certain amount of tweaking
that must be done at deployment time, though having JSF add to this
burden by requiring additional deployment-time configuration is
unappealing to me. I would prefer to avoid adding this as a new
requirement on JSF users/deployers.
While I would prefer not to change the project stage default, I am
totally behind doing whatever we can to ensure a reasonable out of the
box experience. Development tools can certainly help here, but we
should all be vigilant about reporting/discussing/addressing cases where
we fall short of this goal.
Andy
More information about the jsr-314-open-mirror
mailing list