> It shouldn't require that the plugins have maven as their > groupId, i.e. if > it's javaapp:blah, and the javaapp plugin is
Yeah, the extra groupId is only needed if there is a conflict I imagine. And the maven one can take precedence :) > At the moment we're waiting on Brett checking in a new > PluginManager so > that the download can be slotted in there, right? > Unless you are making widesweeping changes, no need to wait. I've kept it up to date so far and can continue to do so. As much as possible I haven't changed the public interface of PluginManager (except to make some public parts private/package when they aren't actually used/needed publicly). But I've just discussed this with Jason and it should be ready "real soon now" anyway. - Brett
