Am 12.12.2016 um 21:32 schrieb Tibor Digana: > The IDEs like Eclipse, IDEA etc must adapt to versionless parent. > > @Christian > Execution of large projects and parent version depends on development team. > Nowadays they are going to be Microservices very small and isolated in > build time and runtime as well. > It really depends on the needs. For instance nowadays I can non-recursively > -N release a parent and a specific child -pl can be released separately and > release plugin will ask me what is the release version of parent. > > If Maven had continuous build based on SCM information, I would not care if > I run the build from the root even if I want to build only changed child > somewhere deeply in the tree. > Actually this is the feature I am missing in Maven and installing Jenkins > for that, no developer would do. > > But logically if such large structure will always be built from root > because of such coupling and because of all WAR file always will be > deployed to JBoss together at the same time because they have common > database model, then it makes perfect sense not to have intermediate Parent > sections because this is one big consistent structure and always will be.
You wouldn't need an artifact based build system for this. One big 'src' folder and one big 'classes' folder and packages build based on directory/package names. You'll loose all kind of scoping that way, of course. You are never deploying artifacts to a repository? So you only deploy the final WAR files and that's it? > And again if a developer wants to build a part of that then still can do > that in the same manner but continuous Maven core should ask SCM for > changes after last build time and build always only changed modules which > would be perfect, would not it be? Job of the CI system, IMHO. It's a matter of how you use to work. I am used to only checkout what I need to work on and rely on Maven to download the missing pieces from repositories for me. Makes a lot of sense. If this will no longer be possible, I simply would not know how to open such a project in my IDE of choice. Before Maven, there was no way to just open a project in the IDE. You always needed to setup some kind of project for each and every bit. Maven has made life so much easier. I haven't had to manually setup a project in the IDE since years. This is a must have for me. I am not objecting your use case. I just would not want an artifact based build system to go the "monolithic project structure" way. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
