[jbosstools-issues] [JBoss JIRA] (JBIDE-13850) Filtering libraries in Source Lookup plugin

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771092#comment-12771092 ] 

Snjezana Peco commented on JBIDE-13850:
---------------------------------------

{quote}
based on what ? for some projects this is the right library.
{quote}

Newer versions are included by default. To include older versions, a user can change a filter using the JBoss Source Lookup preferences page.
See the first comment at https://community.jboss.org/en/tools/blog/2012/01/24/jboss-source-lookup

{quote}
And what is the problem that occurs for these ? That we find the wrong version for a specific class ?
{quote}

Right. Currently, the JBoss Source Lookup returns the first class it finds (older versions, usually). 

{quote}
Instead of making it for specific libraries could we have a general mechanism that says for AS7 modules we will consider the newest version if we have no other info ?
Then over time add logic to handle some better mapping ?
{quote}

Filtering is a general mechanism. You can exclude/include any library using a regular expression. The feature isn't JBoss AS specific, the defaults are only set to use newer versions of Hibernate/JSF according to Lukáš's comment in https://community.jboss.org/en/tools/blog/2012/01/24/jboss-source-lookup. 
Since the debugging is intended for the advanced users, using regular expressions shouldn't be a problem.



                
> Filtering libraries in Source Lookup plugin
> -------------------------------------------
>
>                 Key: JBIDE-13850
>                 URL: https://issues.jboss.org/browse/JBIDE-13850
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: maven
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Snjezana Peco
>            Assignee: Snjezana Peco
>             Fix For: 4.1.0.Beta1
>
>
> jsf 1.2 and hibernate 3 will be excluded by default for the JBoss AS Container

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