User development, A new message was posted in the thread "Adding JBoss AS source to a project": http://community.jboss.org/message/522969#522969 Author : arjan tijms Profile : http://community.jboss.org/people/atijms Message: -------------------------------------------------------------- I tried exactly what you said, but it doesn't seem to work. It seems like this only works for directories containing .java files, not for directories containing .jar files.   When I click on "Edit Source Lookup..." again, then my source directory "jboss-5.1.0.GA-src" has indeed been added, and when I unfold it I can see all directories of the source archive, but unlike the "Default" source lookup path, not a single jar file is listed.   I think a big problem regarding JBoss AS sources is that the structure of the source archive is *completely* different from that of the compiled product. For instance, suppose you were looking for the sources of jboss-web-service.jar. This file is located in the binary distribution at /server/default/deploy/jbossweb.sar/jboss-web-service.jar. There is *no* way the source code location even remotely resembles this. Even if the path would not exactly match (since it's actually /server/*/deploy/jbossweb.sar/jboss-web-service.jar), then still one would expect some file called jboss-web-service-src.jar.   Again, this is not how the source is organized. Maybe the source of jboss-web-service-src.jar is within an archive located in thirdpary/jboss/foo/bar/kaz-all.jar. You just don't know... and -that- is the problem.   Maybe a solution is to recursively unjar every .jar file to a central location and then jar it up again. I don't know... but I do know that the current situation leaves a lot to be desired. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/522969#522969