[richfaces-issues] [JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
Michal Petrov (JIRA)
jira-events at lists.jboss.org
Thu Sep 26 11:07:03 EDT 2013
[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807645#comment-12807645 ]
Michal Petrov commented on RF-13225:
------------------------------------
The image mapping would need to be renamed. {{org.richfaces.images.ui}}?
As far as the CSS is concerned, debugging shows the resource path is obtained from [DynamicResourceWrapper|https://github.com/richfaces/richfaces/blob/master/framework/src/main/resource-optimizer/org/richfaces/resource/optimizer/resource/handler/impl/DynamicResourceWrapper.java#L93], which will always return a path beginning with {{%skin%}} needed for the mapping files. I'm assuming those files are then supposed to be scanned and the path resolved from them (via a different handler) but that doesn't seem to be happening.
> RF5 build fails to render optimized resources
> ---------------------------------------------
>
> Key: RF-13225
> URL: https://issues.jboss.org/browse/RF-13225
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
>
> The improvements for 4.5.x along with resource handling improvements introduced several issues:
> * framework/pom.xml resource optimization
> {code}
> <execution>
> <id>static-resources</id>
> <phase>process-classes</phase>
> <goals>
> <goal>java</goal>
> </goals>
> <configuration>
> <arguments>
> <argument>--classpathDir</argument>
> <argument>${project.build.outputDirectory}</argument>
> <argument>--output</argument>
> <argument>${optimized.resources.directory}/Static/</argument>
> <argument>--prefix</argument>
> <argument>${optimized.resources.prefix}/Static/</argument>
> <argument>--mapping</argument
> <argument>${optimized.resources.mapping}/Static.properties</argument>
> <argument>--skins</argument>
> <argument>${optimized.resources.skins}</argument>
> <argument>--excludeFile</argument>
> <argument>^javax.faces</argument>
> <argument>excludeFile</argument>
> <argument>^org.richfaces.ui.images.*</argument>
> {code}
> {panel}
> the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail
> {panel}
> * CSS rendering from *.ecss
> {code}
> #{richSkin.imageUrl('inputBackgroundImage.png')}
> {code}
> {panel}
> the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{../org.richfaces.ui.images/gradientA.png}} (current)
> {panel}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list