Projects are pretty large-grained things at Eclipse. Plug-ins like this one feel like they should just be part of the PDT project. I don't see how making it a separate project adds any value.
I do, however, see exactly how making valuable extensions like this a natural part of the PDT project does add value. It makes PDT more complete which makes it easier for the community to get what they need from a single source. More community generally translates into more contributions, more diversity, and a stronger project overall. Wayne On 07/13/2012 11:33 AM, Martin Eisengardt wrote: > So for me personally: I provide php-maven. Currently including some > phpunit support but this should be removed in favor of Sevas solution? > The maven parts itself: there may be some interest in eclipse > foundation I guess. Because eclipse itself and jdt get more deeper > maven support, this could be migrated to eclipse. I personally do not > mind if this is a lonesome eclipse plugin or an official eclipse > project being part of pdt-extensions. However I have zero experience > with project proposals or eclipse foundation rules. :-) > -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects <http://www.eclipse.org/projects>
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
