Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Generate classes with Jakarta namespace #253

Closed
joaomiguelsoares opened this issue Jan 4, 2023 · 5 comments
Closed

Generate classes with Jakarta namespace #253

joaomiguelsoares opened this issue Jan 4, 2023 · 5 comments
Labels
jakarta maven-plugin Issue concerns maven plugin
Milestone
3.0.0

Comments

@joaomiguelsoares
Copy link

Hi, how can i generate my classes with the "jakarta.*" namespace?
@johnsgithubaccount
Copy link

Switch to the forked project https://github.com/phax/maven-jaxb2-plugin

See sample project https://github.com/SingingBush/jaxb-example

@laurentschoelens
Copy link
Collaborator

Just made a pull request to add jakarta jaxb support (jaxb3 / jaxb4)
#255

apupier added a commit to apupier/compas-core that referenced this issue May 5, 2023
@apupier
Work In progress - Migrating to Quarkus 3.0
aae5dcc 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/compas-core that referenced this issue May 5, 2023
@apupier
Work In progress - Migrating to Quarkus 3.0
c6d9481 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/compas-core that referenced this issue May 5, 2023
@apupier
Migrating to Quarkus 3.0
09f1706 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@apupier apupier mentioned this issue May 5, 2023
Merged
apupier added a commit to apupier/compas-core that referenced this issue May 26, 2023
@apupier
Migrating to Quarkus 3.0
08f24cb 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253
- updated xjb files:
  - namespace from `http://java.sun.com/xml/ns/jaxb` to
`https://jakarta.ee/xml/ns/jaxb`
  - version from 1.2 to 3.0 (which is mandatory in accordance to the
namespace)

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/compas-core that referenced this issue May 26, 2023
@apupier
Migrating to Quarkus 3.0
c573615 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253
- updated xjb files:
  - namespace from `http://java.sun.com/xml/ns/jaxb` to
`https://jakarta.ee/xml/ns/jaxb`
  - version from 1.2 to 3.0 (which is mandatory in accordance to the
namespace)
- Remove com.sun.xml.bind:jaxb-impl no more needed dependency

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/compas-core that referenced this issue Jun 26, 2023
@apupier
Migrating to Quarkus 3.0
e27e8a4 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253
- updated xjb files:
  - namespace from `http://java.sun.com/xml/ns/jaxb` to
`https://jakarta.ee/xml/ns/jaxb`
  - version from 1.2 to 3.0 (which is mandatory in accordance to the
namespace)
- Remove com.sun.xml.bind:jaxb-impl no more needed dependency

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier added a commit to apupier/compas-core that referenced this issue Jun 28, 2023
@apupier
Migrating to Quarkus 3.0
141d41c 
the main change is migrating from JavaEE to JakartaEE.

- update Quarkus bom from io.quarkus:quarkus-universe-bom to
io.quarkus.platform:quarkus-bom as it was deprecated since Quarkus 2.1
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.1#quarkus-universe-bom-is-deprecated
(and it is required to use the Quarkus migration tool)
- launched quarkus `quarkus update --stream=3.0` as mentioned in
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.0#automatic-update-tool
which dealt with a fair part of the migration. Then it remained few
little tasks.
- Updated one package-info annotation
- Updated from jakarta.websocket:jakarta.websocket-api to
io.quarkus:quarkus-websockets (another alternatives might be to add
jakarta.websocket:jakarta.websocket-client-api)
- Updated Jaxb generation. Moving from
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin to
com.helger.maven:jaxb40-maven-plugin. Jaxb 3+ is supporting Jakarta.
using a fork which has implemented the support of Jacxb4. The initial
repository is not very active despite issue raised and a PR is proposed:
see highsource/jaxb-tools#253
- updated xjb files:
  - namespace from `http://java.sun.com/xml/ns/jaxb` to
`https://jakarta.ee/xml/ns/jaxb`
  - version from 1.2 to 3.0 (which is mandatory in accordance to the
namespace)
- Remove com.sun.xml.bind:jaxb-impl no more needed dependency

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@laurentschoelens
Copy link
Collaborator

Before official release of v3 plugin, you can use #233 (comment)

@laurentschoelens
Copy link
Collaborator

Linked to #199

@laurentschoelens laurentschoelens added maven-plugin Issue concerns maven plugin jaxb3 Issue with jaxb 3.x jaxb4 Issue with jaxb 4.x labels Aug 16, 2023
@laurentschoelens laurentschoelens added this to the 3.0.0 milestone Aug 16, 2023
@laurentschoelens laurentschoelens added jakarta and removed jaxb3 Issue with jaxb 3.x jaxb4 Issue with jaxb 4.x labels Aug 20, 2023
@mattrpav
Copy link
Collaborator

#389

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
jakarta maven-plugin Issue concerns maven plugin
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
4 participants
@mattrpav @joaomiguelsoares @laurentschoelens @johnsgithubaccount