Maven themes workaround for 6.1.1 and 6.1.20

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Completed
• Fix Version/s: 6.1CE2EE2
• Component/s: Core Infrastructure
• Labels: None
• Git Pull Request: https://github.com/sez11a/liferay-docs/pull/481

Minchau Dang describes the issue with the current 6.1 releases (i.e., until SP1 is released) ...

Right now, the generate:archetype for themes is incorrect.

After investigating, the reason is that the stuff that's in
src/main/webapps doesn't get copied over until the 'package' phase, while the build-css goal is run in the generate-sources phase. This means that everything in .sass-cache is correct EXCEPT for any customizations, making it largely useless for creating themes.

One workaround is to explicitly copy the files in src/main/webapps in any phase before 'package' and delay the build-css until a phase afterwards. One strategy I tested was to copy the files in the 'generate-sources' phase and to run build-css in the 'prepare-sources' phase.

http://www.liferay.com/community/forums/-/message_boards/message/23709304

The issue and fix commit (at least for 6.1.x) are here:
https://issues.liferay.com/browse/MAVEN-48
https://github.com/liferay/liferay-maven-support/commit/5c79c66b9234d3eedb8b1daeae4920b9401e2127

We need to describe what people using the current release archetypes should do to pick up this fix. Perhaps it is just modifying their existing POMs.

Developer references: Minchau and Mika, and ticket https://issues.liferay.com/browse/MAVEN-48