Hi everyone,

My name is Abdul Hannan. I am a Computer Science student and an Apache
Maven contributor. I have previously contributed to the Maven codebase,
including PR #13086.

I am planning to apply for GSoC 2027 with Apache Maven and have been
exploring Maven issue #13518 – Mojo configuration introspection without
execution <https://github.com/apache/maven/issues/13518>, originally raised
by Guillaume Nodet.

The problem is that IDE integrations such as Eclipse m2e need access to
resolved Mojo parameter values without actually executing the Mojo.
Currently, MojoExecution.configuration() provides the merged XML
configuration, but not the fully resolved and converted parameter values.

I have been investigating how this could be addressed using Maven's
existing configuration infrastructure and have developed an initial
implementation of an experimental MojoConfigurationService.

The service accepts a Project and MojoExecution and returns resolved
parameter values as a Map<String, Object>, without instantiating or
executing the root Mojo.

Some of the main areas I have worked on include:

   -

   Reusing PluginParameterExpressionEvaluatorV4 for expression evaluation
   and typed parameter conversion.
   -

   Extending EnhancedCompositeBeanHelper to extract converted values
   without assigning them to the root Mojo or invoking its setters.
   -

   Extracting the existing configuration interpolation logic into a shared
   PluginConfigurationInterpolator, used by both DefaultMavenPluginManager
   and the new service.
   -

   Handling plugin realm setup using the supplied project context and a
   cloned Maven session.

The current implementation focuses on V4 Mojos and handles defaults,
aliases, nested configuration, collections and expression evaluation. It
also documents its current restrictions, including the requirement for
DefaultProject and DefaultMojoExecution.

I have added tests covering these areas, including a typed URI conversion
regression test. The full Maven reactor test suite passed with 3,127 tests,
zero failures and zero errors (17 skipped). Maven Core Checkstyle and git
diff --check also passed.

I haven't opened a PR yet because I would first like to get feedback from
the community on the approach.

I have a few questions:

   1.

   Does this implementation align with the original motivation and intended
   direction of issue #13518?
   2.

   Would a separate experimental MojoConfigurationService be an appropriate
   API design, or should this functionality be exposed through an existing
   Maven service?
   3.

   Are there any concerns with the current V4-only scope, plugin realm
   setup or project/session handling?
   4.

   Do you think this would be substantial enough for a GSoC 2027 project,
   or would it be more appropriate as a regular contribution?
   5.

   Would any committer or experienced contributor be interested in
   discussing or potentially mentoring this work?

I would like to make sure the approach fits Maven's architecture before
taking it further. Any feedback or suggestions would be very helpful.

Thank you for your time.

Best regards,

Abdul Hannan

GitHub: https://github.com/abdulhannansyed548-cmd

Reply via email to