[snip] > Next I want to host Centipede Cents and Maven plugins. > My best bet is a jakarta-alexandria/plugins dir with > > jakarta-alexandria/plugins/cents > jakarta-alexandria/plugins/maven I'm -1 on this. If Alexandria is to be a commons like place, I'd rather not host other projects plugins here, I'd prefer the code behind the plugins to be in alexandria and the plugins be in their own projects.
As well, not all maven plugins are about documenting and analysing source code, so I don't think it's appropriate they all be hosted here. I'd much rather: a) Maven was a top-level project (jakarta-maven) b) Maven's plugins were a top-level project (jakarta-maven-plugins) But that's a discussion for turbine-maven-dev. > Jason has access to CVS here, and he can take care of making/committing > the MAven plugins in the jakarta-alexandria/plugins/maven dir. > > These are the main points, any suggestions? AFAIK, there's be no discussion about moving plugins to alexandria on the turbine-maven-dev list. And personally, since it's about moving source code from one project to another, I'd expect the developers on that project to agree first. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
