> sure, that's possible. you loose the inheritance then > though. Then you > need the add the xml file to every project and keep all in > sync.
That's an awsome thing with the current checkstyle plugin. I personally would like to have each checkstyle configuration XML maintained and packaged in a separate artifact. Just like the internal ones are packaged in the jar and retrieved via classloader. So one could easily add a dependency to let's say a org.apache.myfaces:myfaces-checkstyle-1.0.jar and voila you can add <configLocation>config/myfaces_checks.xml</configLocation> to the parent poms maven-checkstyle-plugin which will then be available in ALL depending projects. Sounds good, or is there any problem I do not see yet? LieGrue, strub ---------------------------------------------------------------- “Multiple exclamation marks are a sure sign of a diseased mind!” (Sir Terry Pratchett) --- Milos Kleint <[email protected]> schrieb am Do, 8.1.2009: > Von: Milos Kleint <[email protected]> > Betreff: Re: [mojo-dev] code formatting proposal > An: [email protected] > Datum: Donnerstag, 8. Januar 2009, 8:03 > On Wed, Jan 7, 2009 at 11:39 PM, Benjamin Bentmann > <[email protected]> wrote: > > Milos Kleint wrote: > > > >> [...] The default placement for the rules is an > xml > >> file added to the project, but since version 6.5 > inetbeans is also > >> capable of pulling the formatting settings form > the pom file. [...] you > >> can check the properties and the > >> compexity added to the pom here: > >> > http://svn.codehaus.org/mojo/trunk/mojo/nbm-maven-plugin/pom.xml > > > > Adding a bunch of IDE specific stuff into the POM > doesn't look right to me. > > If the intention is to keep the formatting rules > inside the project's SVN > > location, one could as well just check in the > equivalent XML file. > > sure, that's possible. you loose the inheritance then > though. Then you > need the add the xml file to every project and keep all in > sync. > > > > > To share this XML file via a common parent, the > NetBeans Maven Plugin could > > also attach the file as ArtifactMetadata to the main > artifact just like the > > Site Plugin attaches the site.xml for later resolution > in sub projects. > > there is no netbeans maven plugin. > > > Though still not sure how nice it is to have the > parent deploy IDE-specific > > stuff. > > > > Another approach could be to add a single property to > a POM that gives the > > URL for the XML file with the formatting. > > might be possible for future versions, however the > currently released > IDE does a simple delegation to the project's model > only > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
