Feature request: Support build of single maven module in multi-module maven projects

[steinarb]

In maven multi module builds, I frequently want to build only the module I'm currently working in (because that's a lot faster than building the entire reactor build).

It would be nice if projectile had a command to build just the current maven module.

I guess it would be nice to have current-module specific versions of much of the functionality that currently takes you to the top of the projects (e.g. open dired on the module top).

But what I'm primarily missing is building just the current module.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

[steinarb]

Any chance of this feature being implemented?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

[steinarb]

I think this is a useful feature and that it should be implemented

[github-actions]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed soon if no further activity occurs. Thank you for your contribution and understanding!

[steinarb]

As before: since most of my projects are multi-module projects and I'm usually working in the context of a single module, since building the entire project takes enough time that I only do it when I have to, I still think this is a useful feature.

[bbatsov]

I haven't worked with Maven for ages, so I've kind of forgotten the layout of its projects. A PR will be appreciated, otherwise this is probably going to stay on the backlog for a while.

[steinarb]

A typical maven multimodule project will look something like this

someproject/
 pom.xml
  modulefoo/
   pom.xml
    src/
     main/
      java/
       Foo.java
  modulebar/
   pom.xml
    src/
     main/
      java/
       Bar.java

Currently if we do C-c p c when working on Foo.java we set someproject as the working directory and run mvn -B clean install there.

It would be nice to be able to do e.g. C-c p M (C-c p m would have been the natural choice, but it was already taken...) and what I would expect from that is that projectils skips up to the directory of the first pom.xml it finds and then run mvn -B clean install in that directory.

I.e. basically the same thing as C-c p c does today, but do it in a different directory (the directory of the first pom.xml file encountered when going up from the source file towards the project directory).