]
Lukáš Fryč resolved RF-11501.
-----------------------------
Resolution: Done
maven-resources-plugin generates xyz/js files instead of xyz.js
---------------------------------------------------------------
Key: RF-11501
URL:
https://issues.jboss.org/browse/RF-11501
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: base functionality
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0-SNAPSHOT r.
Metamer 4.1.0-SNAPSHOT r.22779
Mojarra 2.1.3-SNAPSHOT
JBoss Web 7.0.1.Final
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Chrome 14.0.835.202 @ Linux i686
Reporter: Pavol Pitonak
Assignee: Lukáš Fryč
Fix For: 4.1.0.CR1
# deploy Metamer and open
http://localhost:8080/metamer/faces/components/richTabPanel/simple.xhtml
# the following appears in server log:
{code}
13:40:36,879 WARNING [javax.enterprise.resource.webcontainer.jsf.context]
(http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file jquery/js. To
resolve this, add a mime-type mapping to the applications web.xml.
13:40:36,880 WARNING [javax.enterprise.resource.webcontainer.jsf.context]
(http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file richfaces/js. To
resolve this, add a mime-type mapping to the applications web.xml.
13:40:36,880 WARNING [javax.enterprise.resource.webcontainer.jsf.context]
(http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file richfaces-queue/js.
To resolve this, add a mime-type mapping to the applications web.xml.
13:40:36,881 WARNING [javax.enterprise.resource.webcontainer.jsf.context]
(http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file
richfaces-base-component/js. To resolve this, add a mime-type mapping to the applications
web.xml.
13:40:36,881 WARNING [javax.enterprise.resource.webcontainer.jsf.context]
(http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file richfaces-event/js.
To resolve this, add a mime-type mapping to the applications web.xml.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: