Hi Andy, > 2/ Using the Apache standard project as parent, I'm getting a warning:
This occurs since m2e 1.0. The reasons are really well explained here: http://wiki.eclipse.org/M2E_plugin_execution_not_covered A quick workaround consists in clicking on the warning icon to generate a configuration section in the pom file for the m2e plugin. Laurent On Wed, Sep 7, 2011 at 8:50 PM, Andy Seaborne <[email protected]> wrote: > Maven/eclipse experts, > > I have tried setting up a multi-module project ... some questions ... > > > 1/ Flat vs hierarchical directories. > > Hierarchical is maven preference and m2eclispe generates them but isn't this > a problem with SVN? if the parent is checked out, all the modules get > checked out. Isn't that a bit of a pain? > > Do any tools break with (1) Hierarchical (2) flat modes? > > What is the real-world practical experience here? (not the theory) > > > 2/ Using the Apache standard project as parent, I'm getting a warning: > > maven-remote-resources-plugin (goal "process") is ignored by m2e. > > > Warnings are bad - they need to be checked to make sure they are benign on > every release and risk hiding warnings that do matter. Jena is too big to > have some 'acceptable' warnings. > > Can this be turned off somehow? I can't see anything but there are lots of > places it might be. > > Andy >
