Skip to content

Next release #287

Closed as not planned
Closed as not planned

Description

@ascopes

Hello

Just wondering if there is a timeframe for a new update to be pushed to Maven central? There are a few fixes within this repo that will enable me to perform updates on my own components that provide a large quality of life improvement, so I am definitely looking forward to using this in anger 🙂 once Maven can depend upon it.

Thanks in advance.

Activity

  1. ascopes commented on Oct 19, 2025

    @ascopes
    ContributorAuthor

    @cstamas I saw you were active here as well... is there plans to continue to use the latest version of QDox in maven-plugin-plugin once released?

  2. cstamas commented on Oct 19, 2025

    @cstamas
    Contributor
  3. slawekjaranowski commented on Oct 19, 2025

    @slawekjaranowski

    @ascopes I'm preparing for release m-plugin-plugi soon ... so yes

  4. slawekjaranowski commented on Oct 19, 2025

    @slawekjaranowski
  5. ascopes commented on Oct 19, 2025

    @ascopes
    ContributorAuthor

    That'll be great. Look forward to the fix!

  6. slawekjaranowski commented on Oct 19, 2025

    @slawekjaranowski

    @paul-hammant can you do next release .... 😄

  7. ascopes commented on Nov 29, 2025

    @ascopes
    ContributorAuthor

    Hello, just checking if there is any update on this (or any possibility of the fixed build for this dependency being shaded into Maven until a fix is able to be released?)

  8. ascopes commented on Nov 30, 2025

    @ascopes
    ContributorAuthor

    @slawekjaranowski, @cstamas small FYI, looks like #292 is another issue regarding the handling of type parameters that may impact users of maven-plugin-plugin and maven-compiler-plugin.

  9. added 2 commits that reference this issue on Dec 20, 2025
  10. ascopes commented on Mar 1, 2026

    @ascopes
    ContributorAuthor

    @paul-hammant hi, is there any possibility of this being released? Would be great if I could unblock some stuff on my side 👍🏻

  11. paul-hammant commented on Mar 1, 2026

    @paul-hammant
    Owner

    I don't think so in the end. Users should migrate to other technologies now. Other BETTER technologies. If a team that would consume this is really really sure they want to consume it they should fork it and change group com.thoughtworks.qdox to com.theirCompany.theirApp

  12. ascopes commented on Mar 1, 2026

    @ascopes
    ContributorAuthor

    @cstamas @slawekjaranowski looks like Apache Maven will have to totally migrate off of this stack given it has just been deprecated. Is there anything tracking this on Apache side?

    Shame this has been immediately deprecated like this given a large number of things are still reliant on it 😔.

  13. paul-hammant commented on Mar 1, 2026

    @paul-hammant
    Owner

    Some weeks ago, I discussed the future of QDox with Robert Scholte and Hervé Boutemy who are closer to core Maven team than me. One option was to move QDox to Plexus team ownership (Apache's Maven can't take it cos it would be impossible to go back to all contributors for a copyright grant).

  14. added a commit that references this issue on Mar 6, 2026
  15. added 3 commits that reference this issue on Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions