ha!
why is everybody so pro deployment mode as default?
When i was busy doing the changes in that area (adding the system property
and so on)
i asked and wanted to have deployment as default but back then i was
vetoed..
another thing. We need to check in jar files!! Please remember the osgi
folks!!!
But what sebastiaan in another thread proposed seems to work, i will
implement that the coming days
johan
On 11/27/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 11/27/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> On 11/27/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > We could add to the quickstart project's pom a filter that alters
the
> > > mode from development to deployment when a war is built.
> > But why not make deployment the default. Really, that makes so much
> > more sense to me.
>
> Because then you have to restart everytime you have altered a HTML,
> css, js, or properties file.
No, because when you're developing, you turn on the development
version, e.g. by providing a system arg when starting up or putting in
that web-xml parameter.
> Another thing is that you loose any
> debugging tools you have installed.
They should be used for development only. If you want to run your site
in development mode, that's fine, but let's just not make it a
default.
> Deployment is only needed when you
> package into a war. The quickstart is mainly used for development, and
> therefore it is very reasonable to make the default development, until
> you package your application.
The quickstart thing: that's fine, I don't care what you do with that.
I'm talking about the fact that Wicket itself by default runs in
development mode, which is just a bad idea (like I've argued before).
> Making this seamless in the building procedure is something that we
> can do, but hampering development just because of plain stupidity is
> not something I would like to enforce. If you enforce deployment as a
> default people will go around it, ask questions on the list and look
> at other frameworks because we don't have an easy development mode.
Well, now people have problems when they actually deploy! I rather
have them look a bit harder when they develop.
> So the proposal is: set development mode in the web.xml for
> quickstart. If *no* mode is set, then the default will be deployment.
Yes. If nothing is set explicitly, Wicket defaults to deployment mode.
And I don't care about what is done with the quickstart project. That
is probably used for just some testing and learning, so defaulting to
development sounds fine to me.
Eelco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
