5:08 a.m.
[
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