+1. Strict parsing is only on for projects you build, its off for poms in the repository.
This should be a change on trunk only, and the model version should be changed to 4.1.0, right? We need to now start looking into dealing with projects differently based on the model version. Given that this is a model change - why not add categories and tags to the POM itself? - Brett Jason van Zyl wrote: > John Casey wrote: >> so, how do you gain access to the custom section? Would you have to >> re-parse the whole pom? Also, would <custom/> be subject to any sort >> of inheritance, or would it simply be invisible to the project builder? > > After some more chatting in IRC I think that if a <custom/> element was > added to the MDO then the strict parsing can be left on. Essentially the > <custom/> element would be processed like a plug-in configuration. That > would probably make more sense and be safer. > >> -john >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
