-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Milos,
> >> mvn eclipse:eclipse does perform a build (partially) and might even produce >> 1 eclipse project for multiple maven projects (correct me if I'm wrong) No it does not. But I hope it will one finest day. And it will definitely do NOT compile or invoke tests. All it does is invoking phases for code-generation. > >> In NetBeans (IDE I use and develop maven integration for) no build is >> performed and we rely entirely on maven metadata when it comes to project >> representation. Doing a build is out of questions, opening of projects would >> be too slow. And it's a perfectly sound to assume that one wants to open >> just a single maven project from apache geronimo codebase without actually >> building the 200+ multiproject. I am absolutely with you that you do NOT want to build entire geronimo if just one module changes. What I was thinking about is that if "mvn somegoal" is invoked in module some-module maven scans the pom.xml of some-module. Currently it resolves all parents up to toplevel starting from some-module. What it does NOT do is to go down from toplevel and scan (NOT build!) recursively the entire project tree so all modules are available to maven's internals (that what I named the reactor) but that does NOT mean, that the goal is invoked on all of the modules but still only on some-module. But now the invoked plugins could resolve what other-module in the tree is about. I was suggesting to have this feature disabled by default but have a command-line option to enable this. Ask someone why you have to invoke eclipse:eclipse on toplevel everytime. If the dependency of some-module has changed, you can NOT invoke eclipse:eclipse just on some-module since the plugin then wants to resolve the dependencies from the repository and adds JAR-Dependencies to the IDE project. Further ask someone why you can not build some-module if it depends on other-module but thats not already installed. It can be on the local disc and the knowledge how to build some-module is available to maven but it is simply too stupid to do it. You have to go and invoke install on other-module yourself and then on some-module afterwards. Now try to explain this to somebody new to maven. Next there might be some tests that fail in other-module so you cant install it but still want to build some-module. >> Even with brutal performance hacks the 200 projects take about 10 minutes to >> open, while the single project is just a snap. Surely. > >> I'm not sure what the "auto-reactor" feature in eclipse does, Maybe my post was missleading, but I was talking about a vision not about what already works. > but in general >> and especially for large projects it's hard to figure automatically what the >> "reactor" is.. is it just the geronomo plugins pom, or we need all of >> geronimo, or just geronimo aspectj plugin parent? if you are the geronimo >> dev you might know, but will everyone figure that out? Well let me say so. I am suggesting a new feature to maven that is 100% downward compatible. Nobody has to use it if he does NOT like it. But it would solve the problems of many users and make maven even better. > >> Milos Regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoLHgoACgkQmPuec2Dcv/+L0gCZAfkMoCLgf8608h4vKxmGka7C F0MAnRoehAtfciJHGFSFdyQLDI/cWCyi =CpO/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
