5:58 p.m.
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: Rob Stryker
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
5:58 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
SBS JIRA Integration updated JBIDE-9309:
----------------------------------------
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was: http://community.jboss.org/thread/146325)
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: Rob Stryker
Labels: debugging, source
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
4:21 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9309:
---------------------------------------
Assignee: Snjezana Peco (was: Rob Stryker)
Fix Version/s: 3.3.0.M3
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
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
4:21 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
snjezana - any suggestions on the possibilty to have a source path computer that can work
as a fallback for any jar and if nothing else is found (i.e. m2eclipse will handle some)
then we look in the meta-inf/maven/* or maybe just the manifist.mf and if there are maven
coordinates we will get them with Aether or similar to fetch source from maven repo?
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
1:59 a.m.
New subject: [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:
--------------------------------------
I have created a feature that contains a source container for adding the source code of
JBoss AS servers.
Currently, the feature supports JBoss AS 7.
The plugin requires Eclipse 3.7, JBoss AS Tools and m2e 1.0.
Usage:
If you want to debug JBoss AS sources, you need to add the "JBoss AS7 Source
Container" to a launch configuration (the JBoss AS 7 launch configuration or Remote
Java Application launch configuration). The source container requires you to enter JBoss
AS 7 home. All you need to do is to download the binary distribution of JBoss AS 7, unpack
it to some directory and enter the directory when adding the source container. It is not
necessary to download any source code. The source container will automatically download
the JBoss AS 7 sources when they are required.
It is recommended to add this container to the end of the source container list, since it
searches a lot of jars and can affect performance.
You have to set the JBoss Maven repository to the global maven settings file or create at
least one project containing the JBoss Maven Repository
(https://repository.jboss.org/nexus/content/groups/public-jboss/).
The source container works the following way:
- examines if a class is included in a binary jar within the JBoss AS distribution.
Currently it searches jboss-modules.jar and all the jars in the bundles and modules
directory.
- if such a jar is found, the container tries to find maven coordinates using the Nexus
indexer. If they aren't found using the Nexus indexer, it tries to find them in
META-INF/maven/*/*/pom.properties. If the library is created with maven, this file
contains its maven coordinates
- when the maven coordinates are found, the source container configures the source
artifact of the library, downloads it if necessary and adds it to the source container of
the type external archive. This new source container will be further used for source
lookup.
You can automatically add the JBoss AS7 Source Container to all JBoss AS7 launch
configurations using the Window>Preferences>JBoss Tools>Source Lookup preferences
page.
When debugging the server using the Remote Java Application or JBoss Tools Remote Debug
plugin (JBIDE-8548), the container has to be added manually.
The update site is here:
https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.too...
The source code: https://github.com/snjeza/jbossas-sourcelookup
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
10:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
For this to work it should be integrated with our AS adapter - then it would also be able
to provide the runtime location so its not an extra burden for the user.
Couldn't you simply point to a server runtime and get the info from there ?
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
6:31 p.m.
New subject: [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
6:40 p.m.
New subject: [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:
--------------------------------------
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.
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
I have added these functionalities.
When adding the source container to some non JBoss AS7 launch configuration, it can't
always find the correct source.
For instance,
The com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery class is placed in
jbossjts.jar (org.jboss.jbossts:jbossjts:<version>).
The Nexus indexer can find the corresponding artifact in JBoss AS 7
(org.jboss.jbossts:jbossjts:.4.15.2.Final) and JBoss AS 6.1 Snapshot
(org.jboss.jbossts:jbossjts:.4.14.0.Final). JBoss AS 6.1 Snapshot contains the
jbossjts.jar file which is the same as the jbossjts-4.14.0.Final.jar file from the maven
repository.
In JBoss AS 6.0.0.Final, the jbossjts.jar contains the MANIFEST.MF file including:
...
Implementation-Version: 6.0.0.Final
...
arjuna-scm-revision: JBOSSTS_4_14_0_Final
...
Specification-Version: 6.0.0.Final
This file is different from the jbossjts-4.14.0.Final.jar file from the maven repository.
The Nexus indexer can't resolve the artifact.
I will try to create a Maven Source container so that the user can add a source based on
maven GAV or pom.xml.
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
10:29 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-9309:
---------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
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.M4
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
7:10 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-9309:
---------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M4)
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
henk de boer commented on JBIDE-9309:
-------------------------------------
One point of concern maybe: how is this work exactly influenced by the problems outlined
here: http://community.jboss.org/thread/173954
The problem is that the JBoss server runtime for AS7 doesn't put any implementation
class on the .classpath, but only API classes. Will this new concept of the source
container automatically solve that problem, or will it be blocked by it since there is
(almost) nothing to attach sources to?
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:30 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
You can try the source code attachment for JBoss AS 7 in the following way:
- install the JBoss Tools Source Lookup feature from
https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.too...
- create a JBoss AS 7 server
- debug it
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:04 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
Henk, what snjezana showed will make it possible to locate the source of classes found
while debugging based on the source/class path setup in the server launch config.
Your usecase of being able to access the classes based of the project classpath would not
be affected by this - meaning you would not be able to lookup the source of the internal
classes unless you add it manually.
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-9309:
---------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M5)
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 a.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
I have updated the JBoss Source Lookup plugin.
The use of this plugin is described in
https://community.jboss.org/community/tools/blog/2012/01/24/jboss-source-...
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
This is starting to look good but looking at the source i'm seeing a few problems:
1) String url =
"https://repository.jboss.org/nexus/service/local/data_index?sha1=";
Why is this hardcoded to jboss.org index ?
EAP source code won't be in here. It is also not necessarily available/correct if you
are using your own main nexus or artifactory server.
Can't it just use whatever mechanism standard m2e uses to search for these across the
repositories ?
2) it looks like it adds all *.jar's found in the various AS* directories - how do we
handle/cope duplicate content ? ...will it look in the project classpath's first ?
i.e. JSF .jars exist in both v1 and v2 editions.
3) in context of #1 should we request that our EAP maven repo download contains such
generated index ?
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-9309:
---------------------------------
Attachment: jbide-9309a.png
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
1) String url =
"https://repository.jboss.org/nexus/service/local/data_index?sha1=";
Why is this hardcoded to jboss.org index ?
EAP source code won't be in here. It is also not necessarily available/correct if you
are using your own main nexus or artifactory server.
Is there any EAP Nexus indexer? If there is, we can add it.
It is also possible to add a preference so that a user could add some other Nexus indexer
in the case we plan to use this plugin to debug other, non-JBoss servers.
Can't it just use whatever mechanism standard m2e uses to search
for these across the repositories ?
That would be great, but m2e can't find sources if an archive isn't in the Maven
classpath container.
The Source lookup plugin works this way:
- tries to find an artifact using a local maven repository indexer
- tries to find an artifact using all the global maven repositories
M2e also uses such a searching mechanism, but attaches the source only to those archives
that are within the Maven classpath container.
The JBoss Source plugin additionally searches the source in the following way:
- checks if maven coordinates are defined in the META-INF/maven directory
- searches the JBoss Nexus repository (https://repository.jboss.org/nexus/)
GAV, for instance, for jbossjts-4.16.0.Final.jar that is used in the JBoss AS 7.1 can
only be found using the https://repository.jboss.org/nexus/. m2e won't find the source
for this archive unless you specify GAV in the pom.xml. See the thread with subject
"JBoss Nexus Repository Indexer".
- when the user debugs a server, the JBoss Source Lookup plugin will try to find a class
in an archive within a JBoss AS distribution.
M2e won't search source for an archive that is not in the Maven Classpath (archives
defined in a JBoss AS Runtime container, for instance).
M2e doesn't try to search sources for any archive that isn't on the classpath when
debugging.
2) it looks like it adds all .jar's found in the various AS
directories - how do we handle/cope duplicate content ? ...
When debugging some server (JBoss AS), we only know the FQN of a class. The plugin
searches all the libraries in a distribution and assumes that the class is placed in the
first archive it encounters. If there are more versions of the class with the same FQN, we
can't know what jar is used.
will it look in the project classpath's first ? i.e. JSF .jars
exist in both v1 and v2 editions.
Yes, it will.
If the user defines the version of a jar in the pom.xml or adds an archive to the
classpath in another way, the JBoss Source Lookup will find the correct version in the
project's classpath and won't use JBoss AS Container.
!jbide-9309a.png!
If no, we would be to search all archives within a distribution. If we find a class with
the same FQN in two or more archives, we could show a dialog to the user in which he would
be able to choose what archive to use.
3) in context of #1 should we request that our EAP maven repo
download contains such generated index ?
Do you mean jboss-eap-6.0.0.DR11-maven-repository.zip? Sources for most of the artifacts
aren't contained by it.
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:11 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9309:
------------------------------------
Snjeza, I just had a quick look at your demo and it looks nice.
I also looked at the code quickly and just FYI, you can remove the boilerplate code in
JBossSourceContainer.getArtifactFromMetaInf(...) by using something like
{code:java}
File jar = ...
org.apache.maven.shared.runtime.MavenRuntime r = new DefaultMavenRuntime();
MavenProjectProperties projectProperties = r.getProjectProperties(jar.toURL());
{code}
We'll probably want to reuse the identification logic from this plugin to implement
JBIDE-8973, so you should probably try to start refactoring that part into a separate
package. I'll create a JIRA to externalize it to a "common" plugin in the
future.
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:48 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
> 1) String url =
"https://repository.jboss.org/nexus/service/local/data_index?sha1=";
> Why is this hardcoded to jboss.org index ?
> EAP source code won't be in here. It is also not necessarily available/correct if
you are using your own main nexus or artifactory server.
Is there any EAP Nexus indexer? If there is, we can add it.
No, but users might be using their own nexus and they might not have access to the
jboss.org location.
>It is also possible to add a preference so that a user could add
some other Nexus indexer in the case we plan to use this plugin to debug other,
non->>JBoss servers.
mkay.
> Can't it just use whatever mechanism standard m2e uses to
search for these across the repositories ?
That would be great, but m2e can't find sources if an archive
isn't in the Maven classpath container.
Yes I know that - but i'm pretty sure they don't use jboss.org specific index to
resolve either and it seem to still work if you have it on maven classpath..
The Source lookup plugin works this way:
tries to find an artifact using a local maven repository indexer
tries to find an artifact using all the global maven repositories
M2e also uses such a searching mechanism, but attaches the source only to those archives
that are within the Maven classpath container.
The JBoss Source plugin additionally searches the source in the
following way:
checks if maven coordinates are defined in the META-INF/maven
directory
searches the JBoss Nexus repository (https://repository.jboss.org/nexus/)
GAV, for instance, for jbossjts-4.16.0.Final.jar that is used in the JBoss AS 7.1 can only
be found using the https://repository.jboss.org/nexus/. m2e >won't find the source
for this archive unless you specify GAV in the pom.xml. See the thread with subject
"JBoss Nexus Repository Indexer".
this sounds like a bug elsewhere...should find the root for that before I would accept we
add in specific jboss.org specific search.
when the user debugs a server, the JBoss Source Lookup plugin will try
to find a class in an archive within a JBoss AS distribution.
M2e won't search source for an archive that is not in the Maven Classpath (archives
defined in a JBoss AS Runtime container, for instance).
M2e doesn't try to search sources for any archive that isn't on the classpath when
debugging.
no, that is fine - thats why we add this but lets not add too much magic if we can avoid
it.
> 2) it looks like it adds all .jar's found in the various AS
directories - how do we handle/cope duplicate content ? ...
When debugging some server (JBoss AS), we only know the FQN of a
class. The plugin searches all the libraries in a distribution and assumes that the
>class is placed in the first archive it encounters. If there are more versions of the
class with the same FQN, we can't know what jar is used.
will it look in the project classpath's first ? i.e. JSF .jars
exist in both v1 and v2 editions.
Yes, it will.
If the user defines the version of a jar in the pom.xml or adds an archive to the
classpath in another way, the JBoss Source Lookup will find the >correct version in the
project's classpath and won't use JBoss AS Container.
If no, we would be to search all archives within a distribution. If we
find a class with the same FQN in two or more archives, we could show a dialog >to the
user in which he would be able to choose what archive to use.
This sounds like a good thing - do we actually cache an index for this or are we searching
all the time ?
> 3) in context of #1 should we request that our EAP maven repo
download contains such generated index ?
Do you mean jboss-eap-6.0.0.DR11-maven-repository.zip? Sources for
most of the artifacts aren't contained by it.
Snjezana - that is something we should report then - it should be added then.
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
>Is there any EAP Nexus indexer? If there is, we can add it.
No, but users might be using their own nexus and they might not have
access to the jboss.org location.
I will add a preference to enable a user to add his own or whatever Nexus Indexer he
wants.
It will be necessary to add sources to the EAP repository.
>That would be great, but m2e can't find sources if an archive
isn't in the Maven classpath container.
Yes I know that - but i'm pretty sure they don't use jboss.org specific index to
resolve either and it seem to still work if you have it on maven classpath..
...
this sounds like a bug elsewhere...should find the root for that
before I would accept we add in specific jboss.org specific search.
If you add an artifact to the Mavent classpath, you have to define its GAV. After that,
all you have to do is to find source for that artifact.
When you search for some artifact, m2e uses all the project's repositories and all
global repositories to find it. However, that doesn't work always because m2e uses a
minimized index that doesn't include all artifacts.
I have tried to create a full m2e index for the JBoss Nexus Repository, but creating it
takes too long and always freezes Eclipse. I suppose the m2e team removed the Search
action for a class because it requires a full indexer that is almost unusable.
I am using the JBoss Nexus indexer because it contains all the JBoss artifacts and many
other artifacts.
Now, the JBoss Source Lookup plugin can find sources for all archives in JBoss AS
7.x/6.1.
The next version will have a possibility to add other Nexus indexers.
no, that is fine - thats why we add this but lets not add too much
magic if we can avoid it.
Your suggestions are very welcome.
This sounds like a good thing - do we actually cache an index for
this or are we searching all the time ?
When the JBoss Source Lookup plugin finds source, it adds source attachment to the build
path and doesn't search that artifact again. It won't download the artifact unless
the user removes it from a local repository.
We could add artifacts to the m2e indexer, but this indexer requires the project's
context that doesn't exist when debugging. Besides, that index would be removed when
m2e updates its own indexer.
I have tried caching , but that doesn't help.
>Do you mean jboss-eap-6.0.0.DR11-maven-repository.zip? Sources
for most of the artifacts aren't contained by it.
Snjezana - that is something we should report then - it should be
added then.
OK. Then, we have to add a preference that will enable adding new Nexus indexers.
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
I have updated the JBoss Source Lookup plugin.
Update site:
https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/org.jboss.too...
Blog: https://community.jboss.org/community/tools/blog/2012/01/24/jboss-source-...
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 a.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
Max,
Will we include the JBoss Source Lookup plugin in JBT 3.3.0.Beta1?
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/Servers
Reporter: arjan tijms
Assignee: Snjezana Peco
Labels: debugging, source
Fix For: 3.3.0.Beta1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9309:
---------------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta1)
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Labels: debugging, source
Fix For: 3.3.0.CR1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
This shuold have made it in but too late for b1.
Snjezana - we need to find the best way to get this added.
Thus:
Which module should contain it ? inside common jdt or mvn ?
what plugns/features will it introduce/be best merged into ?
Can this be done without requiring m2e to be installed? (i.e. just use aether for
fetching/checking sources or are we fully dependent on mvn for this?
All the EAP/SOA-P specific detection in these classes - is this really where it belongs ?
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Labels: debugging, source
Fix For: 3.3.0.CR1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
Which module should contain it ? inside common jdt or mvn ?
what plugns/features will it introduce/be best merged into ?
The Source Lookup feature includes two plugins:
org.jboss.tools.as.sourcelookup.core
org.jboss.tools.as.sourcelookup.ui
and one feature:
org.jboss.tools.as.sourcelookup.feature
Can this be done without requiring m2e to be installed? (i.e. just
use aether for fetching/checking sources or are we fully dependent on mvn for this?
The plugin requires m2e because we first use the m2e indexer to find source artifacts.
Currently the plugin uses m2e to download artifacts, but that can be changed.
That means the plugin can be added as a separate component or within the maven component.
All the EAP/SOA-P specific detection in these classes - is this
really where it belongs ?
There is no anything specific related to EAP/SOA-P except a different repository. Will we
include the source for EAP/SOA-P? They aren't open source.
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Labels: debugging, source
Fix For: 3.3.0.CR1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:52 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9309:
--------------------------------------------
EAP/SOA-P are fully opensource.
the bundled maven repository have the -source zips.
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Labels: debugging, source
Fix For: 3.3.0.CR1
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] (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:
--------------------------------------
I have upgraded the Source Lookup plugin to be compatible with JBoss Tools 3.3.0.Beta1.
Since the JBoss AS plugin has changed its API, this plugin isn't compatible with JBoss
Tools 3.3.0.M5 anymore.
There was also a problem with recognizing the EAP6 server. It's fixed now.
The plugin works with JBoss EAP 6 if the EAP 6 maven repository is configured.
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Labels: debugging, source
Fix For: 3.3.0.Beta3
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:29 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9309:
---------------------------------------
Priority: Blocker (was: Major)
Forum Reference: http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325 (was:
http://community.jboss.org/message/518182#518182,
http://community.jboss.org/thread/146325)
putting this as a blocker feature - this one is important for us to get in.
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Priority: Blocker
Labels: debugging, source
Fix For: 3.3.0.Beta3
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 a.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-9309.
----------------------------------
Resolution: Done
I have added the org.jboss.tools.maven.sourcelookup.feature feature to the build.
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Priority: Blocker
Labels: debugging, source
Fix For: 3.3.0.Beta3
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 p.m.
New subject: [JBoss JIRA] (JBIDE-9309) Easily adding full JBoss AS source
[
https://issues.jboss.org/browse/JBIDE-9309?page=com.atlassian.jira.plugin...
]
Martin Malina closed JBIDE-9309.
--------------------------------
Verified in JBT 3.3.0.Beta3b. (But is not included in JBDS.)
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/Servers
Reporter: arjan tijms
Assignee: Max Rydahl Andersen
Priority: Blocker
Labels: debugging, source
Fix For: 3.3.0.Beta3
Attachments: jbide-9309a.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4549
days inactive
4865
days old
jbosstools-issues@lists.jboss.org
30 comments
10 participants
participants (10)
-
arjan tijms (JIRA) -
Fred Bricon (JIRA)
-
henk de boer (Commented) (JIRA)
-
Martin Malina (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (JIRA)
-
SBS JIRA Integration (JIRA)
-
Snjezana Peco (Commented) (JIRA)
-
Snjezana Peco (JIRA)
-
Snjezana Peco (Updated) (JIRA)