Magnolia

Integrated in magnolia_main-trunk #259
/ MAGNOLIA-2245 : removed DeploymentUtilsPage - moved i18n reload tool to DevelopmentUtilsPage
(+ slight improvement of the devutilspages)

What about for those that still use jsp? How are the changes going to be redeployed now?

Vasko - I don't mind readding this at all, if you briefly explain your working scenario. Are you copying a new jar to your running system ?

Standard maven webapp development. I have my modules in source. I have the magnolia-empty-webapp in source as well. Add the module in the pom of the webapp. Build the module, build the webapp . Run the webapp. I f iI make any changes in the module (jsp) I must click redeploy in order for the changes to be visible (the new jars to be extracted). And, yes, for "live" sites, I copy the newjars into the lib folder, of the webapp. Is there another way, that I am not aware of?

You didn't say if you copied your new jar when the webapp was running.
However, I highly suspect that the reason you need this button is because module files are (by default) only extracted 1) when updating to a new version of this module 2) when they haven't been modified on the filesystem.

I might re-add it on the dev-tools page, with a dropdown to select your module, then; however, you might want to check the module/update mechanism out.

Moved it to the dev-tools page, would be great if you could have a shot at it

Integrated in magnolia_main-trunk #269

• re-added files extraction, to DevelopmentUtilsPage, with a module selection box
• added IDs to form elements

Just to answer the question above..

No.. the webapp was not running when I was adding the jars.... and 1) No I was not using a new version of the module (which would bu default cause a bootstrap of the files, right?) and 2) No, they have been modified in the jar, but the webapp by default works with the previous state of the files in the file system, until a newer version of the file is supplied (like via redeployment or adding a new version). This probably confirms your suspectoins..

I will try your new deployment page, and provide feedback tommorow... and looking forward to try the new modules as well..

And, if you could provide more info on the module/update mechanizam

Regards,
Vasko

It is a general need to extract the jsps on any restart. While developing I normally use an ant builder in eclipse to copy the templates to the webapp. See :MAGNOLIA-1200.

I have written for one project a module version handler which extract the files on every startup if the version is a snapshot. I should probably checkin this version handler.

An other option could be to extract the jsps, when ever magnolia.develop property is set to true (for instance by using a startup task).

Opinions are welcome.

Yes, I like the idea of automatically extract the jsps. However, I tried it and it does not extract all of the files (hmm..?). I know that the files are supposed to be in mgnl-files, and xmls in mgnl-bootrap (and so on), but am I required to have some kind of predefined structure beyond those folders (ex: in docroot are only css, js and imgs folders allowed?). I tried the new "extractor" of files, but it didnt help either. So what I have now is the following situation, some of the modules have all of their files extracted, some (one) has none, and one module have some of the files extracted, and some not.. very, very, very weird...

We'll hopefully review this completely for 4.0