Christian Grobmeier wrote: > OK, then the mvn eclipse plugin 2.8 will fail when building it because > it does not support ".." path. Should we nail down the mvn-eclipse > version to 2.7 in the pom? We have something similar for the idea > plugin in the parent pom. > > The other question is, if it is really a good idea to depend a sub > project to a top project (just because of two files). Wouldn't it be > better to copy LICENSE/NOTICE to core, examples and sandbox too?
Actually I was always tempted to create a profile active for eclipse project generation that will omit the resource path for those two files. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
