Hi Bernd, Bernd Eckenfels 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. 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. We could move the compiler and jar plugin into an own profile of the parent, that is automatically activated if src/main/java exists. That, however, enforces Maven 3 and standard layout for all Java projects. Regards, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
