You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used a fairly-large multimodule project. It seems to involve an EAR, with maybe 15 modules incl. WARs and JARs altogether. There are a bit less than 100 transitive dependencies.
When I expand the twistie under "Default" in the Source Lookup view:
nothing appears to happen. It seems like maybe the mouse click didn't even register and I should click again?
But actually the UI content is simply taking a long time to be calculated and to populate.
Maybe about 15 seconds? (I didn't time it carefully.)
Perhaps we could calculate this proactively in the background once debug is launched, rather than lazily when it's expanded?
We wouldn't want to slow down the Debug startup path too much and lose the benefits of doing things lazily, only-as-needed.
I don't think we'd want to do the calculation too early, say on project import, since then we have to worry about the dependencies having changed.
The text was updated successfully, but these errors were encountered:
I used a fairly-large multimodule project. It seems to involve an EAR, with maybe 15 modules incl. WARs and JARs altogether. There are a bit less than 100 transitive dependencies.
When I expand the twistie under "Default" in the Source Lookup view:
nothing appears to happen. It seems like maybe the mouse click didn't even register and I should click again?
But actually the UI content is simply taking a long time to be calculated and to populate.
Maybe about 15 seconds? (I didn't time it carefully.)
Perhaps we could calculate this proactively in the background once debug is launched, rather than lazily when it's expanded?
We wouldn't want to slow down the Debug startup path too much and lose the benefits of doing things lazily, only-as-needed.
I don't think we'd want to do the calculation too early, say on project import, since then we have to worry about the dependencies having changed.
The text was updated successfully, but these errors were encountered: