Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Modularized Maven Core / Plugins (JPMS) #75

Open
khmarbaise opened this issue Jul 26, 2024 · 3 comments
Open

WIP: Modularized Maven Core / Plugins (JPMS) #75

khmarbaise opened this issue Jul 26, 2024 · 3 comments

Comments

@khmarbaise
Copy link
Collaborator

khmarbaise commented Jul 26, 2024

Goals

  • The idea is to modularized the Maven Core as well all core plugins
  • Setting clear boundaries which packages/classes will be exposed and which will not
  • Plugins can only use exposed packages/interfaces

Non-Goals

  • XXX

Questions

  • What about extensions?
@khmarbaise khmarbaise self-assigned this Jul 26, 2024
@khmarbaise khmarbaise changed the title Modularized Maven Core / Plugins (JPMS) WIP: Modularized Maven Core / Plugins (JPMS) Jul 26, 2024
@gnodet
Copy link

gnodet commented Nov 19, 2024

I think that's one big reason why we now have a clean API in Maven 4.
Basically, everything inside org.apache.maven.api package coming from org.apache.maven:maven-api-xxx artifacts is the API. Anything else is not.

@rmannibucau
Copy link
Collaborator

think jpms would be too restrictive cause some plugins will then break but it can be enabled with the mvn 4 API and recent changes

@desruisseaux
Copy link

JPMS could be experimented in branch. The clean separation in Maven 4 should make that easier. Whether the experiment would be merged to master or not would be discussed after we can see how it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants