Can someone please remove MODULES-105? As far as I can tell there is absolutely no relationship between this bug and that, and the BZ<->JIRA integration is causing every status change and comment to be reflected in JIRA, annoyingly.
(In reply to comment #5)
> Can someone please remove MODULES-105? As far as I can tell there is
> absolutely no relationship between this bug and that, and the BZ<->JIRA
> integration is causing every status change and comment to be reflected in
> JIRA, annoyingly.
I removed MODULES-105.
However there is a relation, as the fix for MODULES-105 was intended to resolve an issue (out of date .index.jar files in the modules directory) that still exists in some situations in EAP6.
Okay, that's fair. I am separately requesting that an enhancement be enacted to prevent all status changes and comments from cross-propagating between the two trackers though. Hopefully that will cut down on things.
Jodi, the doc text is not accurate. The initial suggestion to fix the issue was to remove the out of date indexes as you describe in the doc text, but that was rejected. Instead of removing the out of date indexes what we are doing is making a copy of the JBoss modules directory (a shallow copy, using symlinks) but excluding the indexes. Then we use this copy instead of the original, thus there is no problem even if the indexes are out of date.
Juan - thank you very much for reviewing my doc text, it's greatly appreciated.
Can you please take a look at the new doc text and confirm I've worded it correctly?
Jodi, the doc text is accurate now in my opinion. Thanks for the prompt reaction!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.