Surely the commons build plugin is only needed to simplify setting up some files?
If it were not there, the files could still be updated manually. The doc page [1] makes it clear that the only _potential_ build-time dependency is the copy-javadoc-files goal. However AFAIK that is not used anywhere. So it is not actually used at build time currently. [1] http://commons.apache.org/proper/commons-build-plugin/index.html On 22 November 2016 at 07:29, Jörg Schaible <joerg.schai...@bpm-inspire.com> wrote: > Hi Gary, > > Gary Gregory wrote: > >> I was thinking the parent POM just had stuff that needed to be inherited >> but since I have not looked it sounds like there is actual code in there? > > Just ressources, but they are referenced in the plugins' classpaths. > >> I am about to push a new version of commons-build-plugin. Is that what you >> are referring to? > > Yes and no. Yes for the release procedure and no for the component itself. > Look into svn, there's also an old commons-build. > > Cheers, > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
