Mauro Botelho wrote:
It makes sense, but in what cases would that code be activated then?
If you run m2 eclipse in the top level directory it will successfully
generate project descriptors in level 1 subdirectories that contain Java
(jar) projects. These can be imported into an eclipse workspace
(should be in different physical location that the checked code) using
"Import existings projects into workspace".
You can go into maven-plugins and run m2 eclipse in there, and import
the additional projects into the workspace. Unfortunately they will not
be cross linked in eclipse with core projects generated in the previous
run (they'll depend on jars in the repo, instead of eclipse projects)
m2 -r eclipse does not work because drills down the whole source tree
for poms and it picks up one that is unbuildable. This might be an
error, but not necessarily - the tests can contain unbuildable poms
quite legitimately.
R.
PS. hope my expalinations are useful - I'm just feeling my way around
too ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
