Eclipse plugin doesn't find all gradle projects #104

Activity

1. philwebb

   added

   type: bug

   on May 28, 2019
2. wilkinsona commented on Jun 25, 2019

   

   wilkinsona

   on Jun 25, 2019

   Contributor

   More actions

   Part of the problem for me was that the Eclipse plugin needs Buildship 3.0 (although its Require-Bundle manifest entry does not constrain the version) and I had 2.2.1 installed. Buildship 3.1 is the current latest. I think we should upgrade to that and see where it leaves us.
3. wilkinsona commented on Jun 25, 2019

   

   wilkinsona

   on Jun 25, 2019

   Contributor

   More actions

   See #117 for the Buildship upgrade.
4. wilkinsona commented on Jun 25, 2019

   

   wilkinsona

   on Jun 25, 2019

   Contributor

   More actions

   This is working for me now with Eclipse 2019-06 and a 0.0.13 snapshot of the Eclipse plugin.

   I've noticed that it takes a while after importing or refreshing a Gradle project for the project's settings to be customized. That seems to be because every project in the workspace is processed, rather than just the newly imported or refreshed project.
5. philwebb commented on Jun 25, 2019

   

   philwebb

   on Jun 25, 2019

   ContributorAuthor

   More actions

   Spring Framework suffers a bit with import times and I wonder if it's related to our plugin. Perhaps there's a better way.
6. philwebb

   added this to the 0.0.x milestone on Dec 4, 2019