[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-9310) JBoss tools does not take AS 6's jsf.deployer into account

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-9310.
--------------------------------

        Labels: debugging new_and_noteworthy source  (was: debugging source)
    Resolution: Done


Marking this as resolved =] 

> JBoss tools does not take AS 6's jsf.deployer into account
> ----------------------------------------------------------
>
>                 Key: JBIDE-9310
>                 URL: https://issues.jboss.org/browse/JBIDE-9310
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: arjan tijms
>            Assignee: Rob Stryker
>              Labels: debugging, source, new_and_noteworthy
>             Fix For: 3.3.0.M3
>
>         Attachments: JBIDE-9310.png
>
>
> In JBoss AS 6, one can change which JSF implementation JBoss AS uses by editing /deployers/jsf.deployer/META-INF/jsf-integration-deployer-jboss-beans.xml. JBoss bundles Mojarra 1.2, 2.0 and MyFaces 2.0 by default.
> However, if one changes this, JBoss tools keeps putting the two hardcoded libs in /deployers/jsf.deployer/Mojarra-2.0/jsf-libs on the IDE's lookup path. This means that stepping through JSF source code is totally broken then.
> A workaround is to copy the libs from the other configuration to /deployers/jsf.deployer/Mojarra-2.0/jsf-libs and rename them to jsf-api-2.0.3-b05.jar and jsf-impl-2.0.3-b05.jar. This works, but there is something unsettling of having e.g. the 2.1.2 libs called 2.0.3 just for the sake of the ability to debug.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira