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

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

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.

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.

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.

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 Components: Seam Affects Versions: 2.0.1 Environment: Linux Reporter: Denis Golovin Assigned To: Viacheslav Kabanovich Fix For: 2.1 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.

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 Components: Seam Affects Versions: 2.0.1 Environment: Linux Reporter: Denis Golovin Assigned To: Viacheslav Kabanovich Fix For: 2.1.0.beta1 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.