People seem to be okay with this. An example of how the site build has to be configured for sandbox components when inheriting from commons parent (instead of commons sandbox parent) can be reviewed in BeanUtils2 [1].
I'll update the other sandbox components, when I find the time. Regards, Benedikt [1] http://svn.apache.org/viewvc/commons/sandbox/beanutils2/trunk/pom.xml?revision=1575534&view=markup 2014-03-08 13:04 GMT+01:00 Benedikt Ritter <[email protected]>: > Hi, > > I'd like to get rid of Sandbox parent pom. The only thing it adds IMHO is > that the site build picks up the correct URLs by setting some properties. > We always have to release a new sandbox parent when commons parent is > released. > > How about overriding the said properties in the sandbox component poms and > let them in turn inherit from commons parent? That would introduce a bit > redundancy but changes in parent pom can be picked up by the sandbox > components more easily. > > Thoughts? > Benedikt > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
