[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9309:
--------------------------------------
Couldn't you simply point to a server runtime and get the info
from there ?
If the "Automatically add the JBoss AS source container to all JBoss AS launch
configurations" preference is checked, the JBoss AS source container is automatically
added. A runtime is recognized from the launch configuration.
If the "Automatically add the JBoss AS source container to all JBoss AS launch
configurations" preference is unchecked, it is possible to do the following:
- if the user adds the JBoss Source container to a JBoss AS launch configuration, we can
find a runtime on the basis of the configuration. The user doesn't have to enter
anything, he only needs to add the source container
- if the user adds the JBoss Source container to some other launch configuration, we would
show a dialog with a list of available runtimes where the user can select a runtime and a
button with which the user would be able to point to some AS home directory if there
isn't any appropriate runtime.
TODO
- add source containers for JBoss AS 6, AS 5, EAP, EPP, SOA-P. Not sure if it is possible
to find maven coordinates automatically for all libraries in these servers; some JBoss AS
5/6 libraries contain the META-INF/maven directory, but that doesn't apply to all
libraries.
- add source containers that will find sources based on some pom.xml in a file system,
workspace ... or based on the maven coordinates (GAV); this could be contributed to m2e;
m2e doesn't find sources for WTP/JBT servers and remote configurations if maven
libraries aren't associated with some Eclipse Java project.
This way, we could define all maven libraries used within some application (JBoss AS
4,5,6, EAP/EPP/SOA-P, glassfish server, eclipse, maven build ...) in some pom.xml. The
user could add such a container to a launch configuration.
I suppose EAP/SOA/EPP require a separate maven repository.
Easily adding full JBoss AS source
----------------------------------
Key: JBIDE-9309
URL: https://issues.jboss.org/browse/JBIDE-9309
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.M3
The JBoss AS server runtime from JBoss tools adds a library container to the classpath of
an Eclipse project. This container provides a large amount of jar files that make up JBoss
AS itself and the Java EE services it offers.
Attaching the source code for this is notoriously difficult. Because it concerns a large
amount of jar files, attaching source code for each jar is a rather tedious job.
For JBoss AS 5, the fact that the location of jars in the source archive was completely
different from the structure exposed in Eclipse or the binary build of JBoss AS, made it
very hard to actually locate the correct source jar. Sometimes even names were different,
making it even harder.
For JBoss AS 6, the source archive does not even contain the source for the majority of
the JBoss AS artifacts. Source for 'core functionality' (from the point of view of
the Java EE developer), like Servlet and JSF is missing. The user has to hunt the Internet
to find the correct source for the correct version that JBoss AS 6 uses. This makes an
already tedious job even more tedious.
I would like to request functionality where the user can point to a single
_jboss-src.xyz_ file that contains all sources. JBoss tools should then automatically
attach the right source from the archive to the right jar from the library container.
Alternatively the user could point to a maven repository (but this should not make the
Eclipse project dependent on maven).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira