[JBoss JIRA] (RF-13258) Build RichWidgets dist with maven
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13258?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13258:
-------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
> Build RichWidgets dist with maven
> ---------------------------------
>
> Key: RF-13258
> URL: https://issues.jboss.org/browse/RF-13258
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Currently RichWidgets keeps it's dist folder in version control to allow RichFaces to consume the compiled widgets. It would be better if the RichFaces build built the widgets itself, and we could remove the dist folder from RichWidgets version control.
--
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
12 years, 5 months
[JBoss JIRA] (RF-13258) Build RichWidgets dist with maven
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13258?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13258:
-------------------------------
Sprint: (was: 5.0.0.Alpha2 - Sprint 3)
> Build RichWidgets dist with maven
> ---------------------------------
>
> Key: RF-13258
> URL: https://issues.jboss.org/browse/RF-13258
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Currently RichWidgets keeps it's dist folder in version control to allow RichFaces to consume the compiled widgets. It would be better if the RichFaces build built the widgets itself, and we could remove the dist folder from RichWidgets version control.
--
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
12 years, 5 months
[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13225:
-------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
> 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
> Assignee: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> 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
> {{%skin%/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
12 years, 5 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12802:
-------------------------------
Sprint: (was: 5.0.0.Alpha2 - Sprint 3)
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
12 years, 5 months