On 05/15/2016 08:16 PM, Stefan Oehme
wrote:
I have to admit that I wasn't aware of this complexity in BuildShip.
I was expecting it to behave more like m2e -adding natures, builders
and classpath containers to project-, and not recreating an abstract
structure of projects just for Eclipse. To be honest, given how
tricky BuildShip seems to be internally, I'm wondering whether the
Smart Import can match, or even should match.
As long as BuildShip is so different, it seems like users of Gradle
in Eclipse will not be able to use Smart Import (at least until
Oxygen).
Why does BuildShip need to rename all of them? Wouldn't it work with
the generated names?
But for sure the names may not be perfect. Maybe another convention
should be preferred in the importer directly, one that works better
in general. What do you use in BuildShip?
Right.
The possibility to update multiple projects at once is something
that is missing in the IDE at the moment.
Auto-build is disabled during import, and updating Maven
configuration does the whole configuration at once. So even with 500
projects, it's going OK.
The fact that users can browse the code and project structure very
fast while projects are being asynchronously configured is actually
a very important thing. Users can see that the project are still
being configured in the Progress Bar but can already do many things.
For the projects I tried (mainly Maven projects, such as WildFly),
the import returns early; and while Maven is processing the newly
imported projects, I can browse code, make a search, code on the
projects that are already configured... So yeah, my import is not
complete, but I can do other things. If the Maven configuration
(including downloading dependencies locally), I would have to stare
at a wizard for an hour with wildfly from master on a clean Maven
repo.
The Smart Import is indeed more designed to have a good enough way
to import any project quickly and always with the same workflow/UI.
If some project are in a tricky state, it's possible that it may not
be the best way to import it. People who know very well their
project can and should prefer to select a dedicated import wizard if
they're not satisfied with the proposals of Smart Import.
In the case of a project which has still pom and build.gradle, and
which cannot copy with both in an IDE, then the user should get to
the import wizard and select either m2e or BuildShip dedicated
import.
All that is definitely interesting. The ability for contributors to
recommend a name would be a nice addition. Can you please open a
feature request and make me a CC ?
But to be honest, Smart Import works for several established Eclipse
projects, and we're in the RC cycle for Platform. So the API is very
unlikely to change at all before Oxygen.
|