In any case, I didn't plan on adding the multiple source folder support in m2e core. I'd prefer adding a conversion participant to m2eclipse-buildhelper, as I explained in the wiki, but if you're absolutely opposed to that, it could be implemented elsewhere.
Encouraging and supporting multiple sources directories is diametrically contradicts and fundamental notion of one source tree produces one artifacts and system works via composition. Dealing with multiple source directories creates a combinatorical explosion of logic in plugins, the system itself and to me indicates something is wrong with your setup and infrastructure if you require it. So yes, I would be very opposed to supporting this in any way shape or form in m2e. As for having a generic refactoring tool, although it sounds cool on paper, I'm afraid it might make things more complex while integrating that into m2e (but I don't know squat about refactoring, so I'm probably wrong)
As long as it's hooked into a another general extension point and conversion as a function isn't baked into m2e that's fine.
_______________________________________________ m2e-dev mailing list m2e-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/m2e-dev
Thanks,
Jason
---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven
the course of true love never did run smooth ...
-- Shakespeare
|