JAXB plugin v3.x roadmap · Issue #233 · highsource/jaxb-tools (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Models New Manage and compare prompts
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Current plans for v3.x roadmap:

Features

1. Release a jakarta compatible v3.x release
2. Migrate to new groupId/artifactId org.jvnet.jaxb/jaxb-maven-plugin (more recent maven standard)
3. Align plugin version with jaxb release version as much as possible
4. Migrate jaxb plugin-plugin projects (and maybe jaxb2-basics) to be child modules of this tree
5. Add toolchain awareness

Deprecation

1. JDK 1.6 and 1.7 support
2. Dropping plugin-2.0, 2.1 and 2.2 support.

The goal of this is to make it more straight forward to consume the modules (esp plugin-plugins) and know if versions are compatible in light of the major JEE/Jakarta changes. Support for multiple versions aligning to various jaxb versions (too complicated and confusing to users in light of jakarta change)

Please use this ticket for comments, discussion and questions.

Thanks!