Liferay: Avoiding Re-creating / Redeploying CSS Files

if you are familiar with Liferay, you will understand that when you make its-bit change in the css file, you must rebuild the theme and reinstall it.

Regarding the redistribution, I made a symbolic link (I think I'm on Windows: to inquisitively create a symbolic link on Vista, we are only talking about the release of mklink / d dir1 dir2).

But what about rebuilding things with maven? I would rather skip this step. Basically, what he does is combine and pack all the CSS into one all_packed.css file. Is there some kind of configuration variable to tell liferay to just include the raw files and skip the redistribution of alltogether?

thanks

+4
source share
4 answers

Guys, I found a solution myself.

You should have a file named portal -ext.properties in

$ TOMCAT_DIR / WebApps / ROOT / WEB-INFO / classes

Or, more specifically, for my setup win C: \ Liferay \ WebApps \ ROOT \ WEB-INF \ classes

The file will store the value

theme.css.fast.load = false

This will not allow liferay to look for all_packed.css, and therefore you can change your material without recovery and CTRL-R to refresh the page and see the changes.

+4
source

Just for completeness, since this question is somewhat old, and the problem has already been solved: there is much more along these lines, for example. javascript, layouts, etc. that can be used without a cache. This is described in the Liferay Wiki (as a developer mode) or in the Development Guide available from the documentation site (although it does not currently exist for the latest version - if it is not there yet when you read it, look for it (PDF) in older versions.

It is advisable to use these settings only in development, and not in production, since all css and javascript in as many files as possible lead to a huge result.

+3
source

To enable all of these settings, simply add the following line to the portal-ext.properties file:

include-and-override = portal-developer.properties

this will include all the settings defined by the developer, and when you want to remove them, you can just comment on this line.

+3
source

you can edit css files of your theme from Webapps {your theme} \ css

And can see the changes directly.

You can edit almost all files that do not require compilation. .jsp files but not .java files

0
source

All Articles