Hi, I just erased Rafal's response to Dion's checkin but I'll respond directly here ... As for specifying the resources in each Plugin, right now it is necessary as each of the plugins are slightly different and the inherititance isn't quite optimal yet.
One possible solution I was talking to Dion about was to have a standard directory in the plugin structure where all the resources are specified so that we can use inheritance. Right now where a plugin finds it's resources is a bit willy-nilly. But we could standardize on a directory, say plugin-resources, and that's where all things like velocity templates, sample sources or whatever. This way we wouldn't need to explicity exclude things like maven.xml and the .cvsignore and we could pick up everything that's needed by a plugin in one fell swoop. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
