> Not Fabrizio's doing at all, I'm just asking that you be > careful in what you apply because the xdoc plugin is going to > be one of the first bridges between component land, and with > it maintainability, and the maven1 plugins.
Yep, will do. > Who cares if it's spectacular or not, if Arnaud ever only > works on the PDF plugin and does a good job I'm not going to > fault him for that. As with everything you're going to get a > mix, people people who work specificially on a particular > plugin and those like you and Dion who might not know much > about a particular plugin but about plugins in general. It's a good point. My only concern is whether we end up with a whole bunch of committers only working on one thing they are interested in... As long as there is communication then its fine. A lot of the plugins are (and probably will continue to be when in components) interrelated. > At any rate a list of core versus other plugins as this might > not be much of an issue if a lot of the plugins are pushed > out. Just glancing at the list I think half of them could be > pushed out easily. I'd like to see that list. There are definitely a lot that can go (from the top, antlr, aspectj, aspectwerkz to other projects, from the bottom wizard might become "dead" where it stays as is). But I'm wary about culling it too much - especially the reporting ones as people have probably come to use them. - Brett
