[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1811) Seam model cannot find components from jars under Maven2 Dependencies classpath container

[Viacheslav Kabanovich (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1811?page=comments#action_12400272 ] 
            
Viacheslav Kabanovich commented on JBIDE-1811:
----------------------------------------------

if(path.startsWith("/") && path.indexOf("/", 1) > 1) 

That was a recent change I did to include references to resources from other projects in workspace, like /otherProjectName/pathInOtherProject. Obviously, I forgot that absolute paths in Unix have the same pattern. I will fix it.

> Seam model cannot find components from jars under Maven2 Dependencies classpath container
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-1811
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1811
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>         Environment: Linux
>            Reporter: Denis Golovin
>         Assigned To: Viacheslav Kabanovich
>         Attachments: Screenshot-Seam - seam-maven1-src-pkg1-Test.java - Eclipse SDK .png, seam-maven-win.png
>
>
> It works fine under Windows, but it dosen't under linux
> It should handle all kind of classpath elements correctly. Don't forget that if path starts from "/" it doesn't mean resource is in current eclipse workspace. It is live issue for linux :)
> I case if there is a project in workspace with a name that matches and folder under "/" under Linux, project in workspace has higher priority.
> This issue must have testcase that covers most relevant kinds of class path entries:
> 1. external jar
> 2. Jar from eclipse workspace
> 3. in case when project name coincide  with folder in root under linux, project must come first
> As an option it would be nice remove so called "well known classpath containers" from result list. For instance, there are no seam components in jars from jre classpath container, so there is no reason even look into.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira