[JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13232?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13232:
------------------------------------
[~jhuska] your proposal sounds reasonable. Would you like to formulate this as a Pull Request?
> Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
> --------------------------------------------------------------------------------------------------
>
> Key: RF-13232
> URL: https://issues.jboss.org/browse/RF-13232
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian.
> It matters to the {{CoreDeployment}} and to the similar.
> Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
> Here comes the problem with multiple deployments, when each deployed archive has to have different name.
> Proposed solution:
> Add overloaded constructor method, which would take a name for the deployed archive.
--
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
11 years, 1 month
[JBoss JIRA] (RF-13231) RF 5, tree component missing resource
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13231?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13231 at 10/1/13 11:58 AM:
--------------------------------------------------------------
[~jhuska] your proposal sounds reasonable. Would you like to formulate this as a Pull Request? -- sorry, commented in the wrong issue
was (Author: bleathem):
[~jhuska] your proposal sounds reasonable. Would you like to formulate this as a Pull Request?
> RF 5, tree component missing resource
> -------------------------------------
>
> Key: RF-13231
> URL: https://issues.jboss.org/browse/RF-13231
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output, regression
> Affects Versions: 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
> Chrome 29.0.1547.76 @ Linux x86_64
> Reporter: Matej Novotny
> Priority: Blocker
>
> Using Metamer I accesed a tree component (see steps to reproduce) and it did not render properly, therefore the tree was not usable.
> The error message in web console was:
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 500 (Internal Server Error)
> This may be also connected to https://issues.jboss.org/browse/RF-13200
--
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
11 years, 1 month
[JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13232?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13232:
-------------------------------
Description:
This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian.
It matters to the {{CoreDeployment}} and to the similar.
Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
Here comes the problem with multiple deployments, when each deployed archive has to have different name.
Proposed solution:
Add overloaded constructor method, which would take a name for the deployed archive.
was:
This should be added to support *multiple deployments* feature of Arquillian.
It matters to the {{CoreDeployment}} and to the similar.
Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
Here comes the problem with multiple deployments, when each deployed archive has to have different name.
Proposed solution:
Add overloaded constructor method, which would take a name for the deployed archive.
> Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
> --------------------------------------------------------------------------------------------------
>
> Key: RF-13232
> URL: https://issues.jboss.org/browse/RF-13232
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian.
> It matters to the {{CoreDeployment}} and to the similar.
> Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
> Here comes the problem with multiple deployments, when each deployed archive has to have different name.
> Proposed solution:
> Add overloaded constructor method, which would take a name for the deployed archive.
--
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
11 years, 1 month
[JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
by Juraj Húska (JIRA)
Juraj Húska created RF-13232:
--------------------------------
Summary: Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
Key: RF-13232
URL: https://issues.jboss.org/browse/RF-13232
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: tests - functional
Affects Versions: 5.0.0.Alpha1
Reporter: Juraj Húska
Priority: Minor
This should be added to support multiple deployments feature of Arquillian.
It matters to the {{CoreDeployment}} and to the similar.
Currently {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
Here comes the problem with multiple deployments, when each deployed archive has to have different name.
Proposed solution:
Add overloaded constructor method, which would take a name for the deployed archive.
--
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
11 years, 1 month
[JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13232?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13232:
-----------------------------
Description:
This should be added to support *multiple deployments* feature of Arquillian.
It matters to the {{CoreDeployment}} and to the similar.
Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
Here comes the problem with multiple deployments, when each deployed archive has to have different name.
Proposed solution:
Add overloaded constructor method, which would take a name for the deployed archive.
was:
This should be added to support multiple deployments feature of Arquillian.
It matters to the {{CoreDeployment}} and to the similar.
Currently {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
Here comes the problem with multiple deployments, when each deployed archive has to have different name.
Proposed solution:
Add overloaded constructor method, which would take a name for the deployed archive.
> Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment
> --------------------------------------------------------------------------------------------------
>
> Key: RF-13232
> URL: https://issues.jboss.org/browse/RF-13232
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> This should be added to support *multiple deployments* feature of Arquillian.
> It matters to the {{CoreDeployment}} and to the similar.
> Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class.
> Here comes the problem with multiple deployments, when each deployed archive has to have different name.
> Proposed solution:
> Add overloaded constructor method, which would take a name for the deployed archive.
--
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
11 years, 1 month
[JBoss JIRA] (RF-13224) RF 4.5 build fails to render optimized resources
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13224?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13224:
------------------------------------
The version of the resource plugin was 5.0.0.Alpha1, using 5.0.0-SNAPSHOT will fix the build but the resources are still being pulled from RF 5 (and having the issues described in (RF-13225)). Is it because of the plugin version? (I.e. do we need resource plugin 4.5?)
> RF 4.5 build fails to render optimized resources
> ------------------------------------------------
>
> Key: RF-13224
> URL: https://issues.jboss.org/browse/RF-13224
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.5.0.Alpha1
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha1
>
>
> I believe it's caused by:
> https://github.com/richfaces/richfaces/commit/46b03d226ae420bcbc8abd7f79e...
> {code}
> [INFO] --- richfaces-resource-optimizer-maven-plugin:5.0.0.Alpha1:process (static-resources) @ richfaces-components-rich ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> [ERROR] Exception rendering resorce org.richfaces:iteration/dataGrid/datagrid.ecss using skin blueSky: Method not found: SkinImpl: {warningBackgroundColor=#FFE6E6, headerWeightFont=bold, tableBorderColor=#C0C0C0, controlTextColor=#000000, headerTextColor=#000000, generalTextColor=#000000, selectControlColor=#E79A00, headerGradientColor=#F2F7FF, tableSubfooterBackgroundColor=#f1f1f1, trimColor=#D6E6FB, shadowOpacity=1, tipBorderColor=#E5973E , calendarCurrentBackgroundColor=#FF7800, subBorderColor=#ffffff, editorBackgroundColor=#F1F1F1, generalLinkColor=#0078D0, gradientType=plain, tabSizeFont=11px, calendarHolidaysTextColor=#FF7800, buttonSizeFont=11px, headerBackgroundColor=#BED6F8, hoverLinkColor=#0090FF, tabFamilyFont=Arial, Verdana, sans-serif, calendarSpecBackgroundColor=#E4F5E2, calendarHolidaysBackgroundColor=#FFEBDA, editorMainTextColor=#0B356C, tabDisabledTextColor=#8DB7F3, tableBorderWidth=1px, buttonFamilyFont=Arial, Verdana, sans-serif, generalFamilyFont=Arial, Verdana, sans-serif , tableBackgroundColor=#FFFFFF, calendarWeekBackgroundColor=#F5F5F5, tipBackgroundColor=#FAE6B0 , editorMainBackgroundColor=#D6E6FB, tableSubHeaderBackgroundColor=#ECF4FE, tableHeaderTextColor=#0B356C, calendarCurrentTextColor=#FFEBDA, editBackgroundColor=#FEFFDA, shadowBackgroundColor=#000000, headerFamilyFont=Arial, Verdana, sans-serif, tableFooterBackgroundColor=#cccccc, additionalBackgroundColor=#ECF4FE, panelBorderColor=#BED6F8, visitedLinkColor=#0090FF, controlBackgroundColor=#ffffff, inputNumberSliderBarHandlerBackgroundColor=#0078D0, errorColor=#FF0000, calendarSpecTextColor=#000000, tabBackgroundColor=#C6DEFF, tableHeaderBackgroundColor=#D6E6FB, generalBackgroundColor=#FFFFFF, generalSizeFont=11px, warningColor=#FF4719, headerSizeFont=11px}.imageUrl(java.lang.String)
> javax.el.MethodNotFoundException: Method not found: SkinImpl: {warningBackgroundColor=#FFE6E6, headerWeightFont=bold, tableBorderColor=#C0C0C0, controlTextColor=#000000, headerTextColor=#000000, generalTextColor=#000000, selectControlColor=#E79A00, headerGradientColor=#F2F7FF, tableSubfooterBackgroundColor=#f1f1f1, trimColor=#D6E6FB, shadowOpacity=1, tipBorderColor=#E5973E , calendarCurrentBackgroundColor=#FF7800, subBorderColor=#ffffff, editorBackgroundColor=#F1F1F1, generalLinkColor=#0078D0, gradientType=plain, tabSizeFont=11px, calendarHolidaysTextColor=#FF7800, buttonSizeFont=11px, headerBackgroundColor=#BED6F8, hoverLinkColor=#0090FF, tabFamilyFont=Arial, Verdana, sans-serif, calendarSpecBackgroundColor=#E4F5E2, calendarHolidaysBackgroundColor=#FFEBDA, editorMainTextColor=#0B356C, tabDisabledTextColor=#8DB7F3, tableBorderWidth=1px, buttonFamilyFont=Arial, Verdana, sans-serif, generalFamilyFont=Arial, Verdana, sans-serif , tableBackgroundColor=#FFFFFF, calendarWeekBackgroundColor=#F5F5F5, tipBackgroundColor=#FAE6B0 , editorMainBackgroundColor=#D6E6FB, tableSubHeaderBackgroundColor=#ECF4FE, tableHeaderTextColor=#0B356C, calendarCurrentTextColor=#FFEBDA, editBackgroundColor=#FEFFDA, shadowBackgroundColor=#000000, headerFamilyFont=Arial, Verdana, sans-serif, tableFooterBackgroundColor=#cccccc, additionalBackgroundColor=#ECF4FE, panelBorderColor=#BED6F8, visitedLinkColor=#0090FF, controlBackgroundColor=#ffffff, inputNumberSliderBarHandlerBackgroundColor=#0078D0, errorColor=#FF0000, calendarSpecTextColor=#000000, tabBackgroundColor=#C6DEFF, tableHeaderBackgroundColor=#D6E6FB, generalBackgroundColor=#FFFFFF, generalSizeFont=11px, warningColor=#FF4719, headerSizeFont=11px}.imageUrl(java.lang.String)
> at org.jboss.el.util.ReflectionUtil.findMethod(ReflectionUtil.java:221)
> at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:279)
> at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.parser.AstDeferredExpression.getValue(AstDeferredExpression.java:26)
> at org.jboss.el.parser.AstCompositeExpression.getValue(AstCompositeExpression.java:31)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at org.richfaces.resource.optimizer.faces.ApplicationImpl.evaluateExpressionGet(ApplicationImpl.java:485)
> at org.richfaces.resource.CSSVisitorImpl.visitStyleDeclaration(CSSVisitorImpl.java:212)
> at org.richfaces.resource.AbstractCSSVisitor.visitStyleRule(AbstractCSSVisitor.java:98)
> at org.richfaces.resource.AbstractCSSVisitor.visitRule(AbstractCSSVisitor.java:61)
> at org.richfaces.resource.AbstractCSSVisitor.visitStyleSheet(AbstractCSSVisitor.java:48)
> at org.richfaces.resource.CompiledCSSResource.getInputStream(CompiledCSSResource.java:122)
> at org.richfaces.resource.optimizer.resource.handler.impl.DynamicResourceWrapper.getInputStream(DynamicResourceWrapper.java:56)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl$ResourceInputStreamSupplier.getInput(ResourceWriterImpl.java:70)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl$ResourceInputStreamSupplier.getInput(ResourceWriterImpl.java:60)
> at org.richfaces.resource.optimizer.resource.writer.impl.ThroughputResourceProcessor.process(ThroughputResourceProcessor.java:53)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl.writeResource(ResourceWriterImpl.java:127)
> at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.renderResource(ResourceTaskFactoryImpl.java:96)
> at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.call(ResourceTaskFactoryImpl.java:160)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> [ERROR] Exception rendering resorce org.richfaces:iteration/dataGrid/datagrid.ecss using skin classic: Method not found: SkinImpl: {warningBackgroundColor=#FFE6E6, headerWeightFont=bold, tableBorderColor=#C0C0C0, controlTextColor=#000000, headerTextColor=#FFFFFF, generalTextColor=#000000, selectControlColor=#E79A00, headerGradientColor=#93C4E5, tableSubfooterBackgroundColor=#f1f1f1, trimColor=#C6D6EA, shadowOpacity=1, tipBorderColor=#E5973E , calendarCurrentBackgroundColor=#FF7800, subBorderColor=#ffffff, editorBackgroundColor=#F1F1F1, generalLinkColor=#0078D0, gradientType=plain, tabSizeFont=11px, calendarHolidaysTextColor=#FF7800, buttonSizeFont=11px, headerBackgroundColor=#4A75B5, hoverLinkColor=#0090FF, tabFamilyFont=Arial, Verdana, sans-serif, calendarSpecBackgroundColor=#E4F5E2, calendarHolidaysBackgroundColor=#FFEBDA, editorMainTextColor=#FFFFFF, tabDisabledTextColor=#6A92CF, tableBorderWidth=1px, buttonFamilyFont=Arial, Verdana, sans-serif, generalFamilyFont=Arial, Verdana, sans-serif , tableBackgroundColor=#FFFFFF, calendarWeekBackgroundColor=#F5F5F5, tipBackgroundColor=#FAE6B0 , editorMainBackgroundColor=#7596C6, tableSubHeaderBackgroundColor=#93C4E5, tableHeaderTextColor=#FFFFFF, calendarCurrentTextColor=#FFEBDA, editBackgroundColor=#FEFFDA, shadowBackgroundColor=#000000, headerFamilyFont=Arial, Verdana, sans-serif, tableFooterBackgroundColor=#cccccc, additionalBackgroundColor=#EAF0F8, panelBorderColor=#C0C0C0, visitedLinkColor=#0090FF, controlBackgroundColor=#ffffff, inputNumberSliderBarHandlerBackgroundColor=#0078D0, errorColor=#FF0000, calendarSpecTextColor=#000000, tabBackgroundColor=#9FBDEB, tableHeaderBackgroundColor=#4A75B5, generalBackgroundColor=#F3F2F2, generalSizeFont=11px, warningColor=#FF4719, headerSizeFont=11px}.imageUrl(java.lang.String)
> javax.el.MethodNotFoundException: Method not found: SkinImpl: {warningBackgroundColor=#FFE6E6, headerWeightFont=bold, tableBorderColor=#C0C0C0, controlTextColor=#000000, headerTextColor=#FFFFFF, generalTextColor=#000000, selectControlColor=#E79A00, headerGradientColor=#93C4E5, tableSubfooterBackgroundColor=#f1f1f1, trimColor=#C6D6EA, shadowOpacity=1, tipBorderColor=#E5973E , calendarCurrentBackgroundColor=#FF7800, subBorderColor=#ffffff, editorBackgroundColor=#F1F1F1, generalLinkColor=#0078D0, gradientType=plain, tabSizeFont=11px, calendarHolidaysTextColor=#FF7800, buttonSizeFont=11px, headerBackgroundColor=#4A75B5, hoverLinkColor=#0090FF, tabFamilyFont=Arial, Verdana, sans-serif, calendarSpecBackgroundColor=#E4F5E2, calendarHolidaysBackgroundColor=#FFEBDA, editorMainTextColor=#FFFFFF, tabDisabledTextColor=#6A92CF, tableBorderWidth=1px, buttonFamilyFont=Arial, Verdana, sans-serif, generalFamilyFont=Arial, Verdana, sans-serif , tableBackgroundColor=#FFFFFF, calendarWeekBackgroundColor=#F5F5F5, tipBackgroundColor=#FAE6B0 , editorMainBackgroundColor=#7596C6, tableSubHeaderBackgroundColor=#93C4E5, tableHeaderTextColor=#FFFFFF, calendarCurrentTextColor=#FFEBDA, editBackgroundColor=#FEFFDA, shadowBackgroundColor=#000000, headerFamilyFont=Arial, Verdana, sans-serif, tableFooterBackgroundColor=#cccccc, additionalBackgroundColor=#EAF0F8, panelBorderColor=#C0C0C0, visitedLinkColor=#0090FF, controlBackgroundColor=#ffffff, inputNumberSliderBarHandlerBackgroundColor=#0078D0, errorColor=#FF0000, calendarSpecTextColor=#000000, tabBackgroundColor=#9FBDEB, tableHeaderBackgroundColor=#4A75B5, generalBackgroundColor=#F3F2F2, generalSizeFont=11px, warningColor=#FF4719, headerSizeFont=11px}.imageUrl(java.lang.String)
> at org.jboss.el.util.ReflectionUtil.findMethod(ReflectionUtil.java:221)
> at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:279)
> at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59)
> at org.jboss.el.parser.AstValue.getValue(AstValue.java:67)
> at org.jboss.el.parser.AstDeferredExpression.getValue(AstDeferredExpression.java:26)
> at org.jboss.el.parser.AstCompositeExpression.getValue(AstCompositeExpression.java:31)
> at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
> at org.richfaces.resource.optimizer.faces.ApplicationImpl.evaluateExpressionGet(ApplicationImpl.java:485)
> at org.richfaces.resource.CSSVisitorImpl.visitStyleDeclaration(CSSVisitorImpl.java:212)
> at org.richfaces.resource.AbstractCSSVisitor.visitStyleRule(AbstractCSSVisitor.java:98)
> at org.richfaces.resource.AbstractCSSVisitor.visitRule(AbstractCSSVisitor.java:61)
> at org.richfaces.resource.AbstractCSSVisitor.visitStyleSheet(AbstractCSSVisitor.java:48)
> at org.richfaces.resource.CompiledCSSResource.getInputStream(CompiledCSSResource.java:122)
> at org.richfaces.resource.optimizer.resource.handler.impl.DynamicResourceWrapper.getInputStream(DynamicResourceWrapper.java:56)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl$ResourceInputStreamSupplier.getInput(ResourceWriterImpl.java:70)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl$ResourceInputStreamSupplier.getInput(ResourceWriterImpl.java:60)
> at org.richfaces.resource.optimizer.resource.writer.impl.ThroughputResourceProcessor.process(ThroughputResourceProcessor.java:53)
> at org.richfaces.resource.optimizer.resource.writer.impl.ResourceWriterImpl.writeResource(ResourceWriterImpl.java:127)
> at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.renderResource(ResourceTaskFactoryImpl.java:96)
> at org.richfaces.resource.optimizer.task.ResourceTaskFactoryImpl$ResourcesRendererCallable.call(ResourceTaskFactoryImpl.java:160)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
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
11 years, 1 month