Hiteshsai007 opened a new pull request, #12260:
URL: https://github.com/apache/maven/pull/12260

   # MNG-11966: Update lifecycles reference to point to LifecycleRegistry
   
   ### Proposed Changes
   This PR addresses issue **#11966** ("Update documentation at - Introduction 
to the Build Lifecycle").
   
   In PR #11916, legacy Plexus XML descriptors (`components.xml` and 
`default-bindings.xml`) were removed from the `maven-core` module as part of 
the migration of the core to JSR-330 / `javax.inject`.
   
   Consequently, the source file for the generated references page 
(`lifecycles.apt.vm`) was still pointing to the old package 
`org.apache.maven.lifecycle.providers` for the 3 lifecycles, which is no longer 
the source of truth. 
   
   This change updates `lifecycles.apt.vm` to point to the new public 
`org.apache.maven.api.services.LifecycleRegistry` where the lifecycles are 
registered and queried in Maven 4.
   
   ### Checklist
   
   - [x] Your pull request should address just one issue, without pulling in 
other changes.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body.
   - [ ] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. (N/A: Documentation-only change)
   - [ ] Run `mvn verify` to make sure basic checks pass. (N/A: 
Documentation-only change)
   - [ ] You have run the [Core IT][core-its] successfully. (N/A: 
Documentation-only change)
   
   - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to