A number of my users are confused by the project nesting m2e has to do. I've tried to use the "Hide folders of physically nested modules" feature but there are a number of limitations to it that I don't think can be solved with the present approach.
Should I bother submitting issues for this feature? * Not Hiding new sub modules after initial import. * Not able to turn it off without re-importing the project. To name a few. I noticed Fred implemented this feature: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385422 could a similar approach be used for hiding the nested projects in a more dynamic manner? I believe the SpringSource guys use this type of approach with their Gradle plugin. Mike
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
