Hello, Am Wed, 5 Feb 2014 09:55:18 +0000 schrieb sebb <seb...@gmail.com>: > On 4 February 2014 20:25, Bernd Eckenfels <e...@zusammenkunft.net> > wrote: > > Am Tue, 21 Jan 2014 16:10:35 +0000 > > schrieb sebb <seb...@gmail.com>: > > > >> I have done some work on this.I can fix up the poms so that the > >> Commons "release" profile works. > >> And it looks like the distribution module is not really needed. The > >> assembly plugin can be run from the top level pom. > > > > (sorry for picking this mail for quote, I wanted to stay within a > > thread but it is not a specific answer to sebb) > > > > The current state looks pretty messed up. I have been trying to > > debug some strange bundle-plugin behaviour but I could not really > > with that complicated commons parent. > > > > This parent is not really suited for multi-module builds and even > > if it was it still does quite a few things too much IMHO. > > Which things are excessive? > The intention was to use the pom for common items, and allow it to be > configured (with properties)/overridden by the component poms if > necessary. > But needing to override should be rare.
Well, the main thing I noticed is, that the VFS-project (parent) produces a target/osgi/MANIFEST.MF. There is a second antrun regarding APIdoc. But other than that - looking at the build log again - it seems not much more is actually executed. > > Would it be > > possible to have a "policy commons" parent and a derieved parent > > which also adds "build convinience"? > > > > Currently the VFS project POM is building (unwanted and empty) JAR > > files. > > What command are you using, and what are these jar files? I was running mvn install, but I can no longer reproduce the problem. With trunk rev. 1565946 and linux I dont see those JARs any more. Have to check later if it is a windows related problem. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
