Gregory Amerson

Its pretty easy to reproduce if you have a large jar coming from a AetherRepository, you can see it hang the UI. The slowness is understood if its a large...

Bndtools goes to great efforts to make sure the classpath seen by the projects in eclipse is exactly the same classpath that is seen at build time in cli/gradle/CI etc....

I agree it is annoying. But as I said earlier, from the commiters standpoint, this is "less annoying" than having a lack of fidelity between Eclipse classpath and actual bnd/gradle...

hey @rotty3000 can you show me a reproducible test case and maybe I could have a look? This fix seems it may be papering over something important.

I too have seen this recently. Whoever can nail down a set a reproducible steps post it here and I can take a look.

I think we can address this along with other "import" use-cases by using the new Neon Smart Import framework. https://wiki.eclipse.org/E4/UI/Smart_Import

agree, @bjhargrave could we add smart importer to a new bundle? and that bundle can be marked as optional so it bndtools plugin will still resolve in non-neon installs?

hmm, i see, its hard to have both repos setup in bndtools build.

@rotty3000 and I discussed this and it would be a great improvement to dev experience with bndtools+m2e/maven and I'm willing to try to add this feature to the bndtools.m2e bundle.

Seems like there are two issues here - [ ] add validation to builder to alert users if they have gotten out of sync (.project name doesn't match directory) thus...