[jbosstools-issues] [JBoss JIRA] (JBIDE-812) Adding JSF suport: multiple wb-resources

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen resolved JBIDE-812.
---------------------------------------

    Resolution: Out of Date


Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).

If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.

Thank you!


                
> Adding JSF suport: multiple wb-resources
> ----------------------------------------
>
>                 Key: JBIDE-812
>                 URL: https://issues.jboss.org/browse/JBIDE-812
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsf
>    Affects Versions: 2.0.0.Beta3
>            Reporter: Petr Lindovsky
>            Assignee: Viacheslav Kabanovich
>             Fix For: LATER
>
>         Attachments: screenshot.jpg, toy_firstjsf.zip, toy_firstjsf_redhat.zip
>
>
> We have a Web project whose directory structure is enforced by our internal build system. To make it work with Europa, the .settings\org.jboss.tools.jst.web.xml  file has two wb-resource elements. My problem is that when adding RedHat JSF support to this project using the wizard, the resulting project seems to ignore the second wb-resource directory.
> To reproduce this, I created a helloworld-style project based on http://www.horstmann.com/corejsf/ (see attachment). With Europa, this works OK, that is, the project is correctly exported with Export... > WAR file and correctly run with Run As > Run on Server. But I'm not sure how to make this work with RedHat JSF support, that is how to tell it that ui/resources is a second WebContent directory.

--
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