Community
Participate
Working Groups
There is no way to associate source and javadoc to libraries associated with a web project via the J2EE configuration. This is a problem for those who want to use the web tools server launching / module deployment but don't want to keep their jars in WEB-INF/lib on the file system (or more importantly, version control)... a very common scenario I would think. I really think there's an opportunity to rework how simple web-app (.war producing) projects manage their jar dependencies. It doesn't seem as clear and intuitive as it could be (consider the competition's handling of this). I think the fact that "Web App Libraries" storing of javadoc/source in a non standard location (see #159838) is also a sign that maybe things could be handled more consistently.
mass update to remove target for all those targeted to 1.5.3 that were "normal" severity and "priority 3" (on the surface those dont' seem serious enough to fix in a maintenance release). If I have made an error pleasae reset target and set priority appropriately.
The code needed to fix this will be essentially the same as needed for bug 159838. However, since this is not exactly the same this is not being duplicated.
Any progress on this?
Assigning to Carl for evaluation
In the case of EAR AppContent/APP-INF/lib jars (that is, jars that are included in the EAR project and "inherited" by the EJB and WAR projects, it would be nice to be able to associate the Javadoc/source with the jar in the EAR project, and have the association be "inherited" by the other projects. (This is probably hard, since the EAR project doesn't even have a build path.) If anyone can note some workarounds, it would be helpful.
Please look into this and 159838 once again?
