apache / apache/camel-quarkus

xml-jaxp: not used in xtokenize, lacks description, possibly to be removed from the catalog

Open
#4,075 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
302
Forks
232
Avg merge
1d 20h
Merged PRs (30d)
114

Description

Fix of the camel [issue](https://issues.apache.org/jira/browse/CAMEL-18320) removed `xml-jaxp` from the catalog's xtokenizer module (see [commit](https://github.com/apache/camel/commit/925395258b1bb8c001dcf7ef571e09c0eb748221) in camel).

This change brought a problem into `prepare-catalog-quarkus` plugin execution from the branch `camel-main`, where description of the `xml-jaxp` was taken from `xtokenize` module.
Quick fix uses

```
Camel XML JAXP
```

(as is present in Camel).

Further investigation is required (possible solution may be the removal of `xml-jaxp` from the catalog)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the prepare-catalog-quarkus plugin execution and the catalog's xtokenizer module, then compare the referenced CAMEL-18320 issue and Camel commit 925395258b1bb8c001dcf7ef571e09c0eb748221. Determine whether xml-jaxp should be removed from the catalog or given its own description, and verify that catalog preparation succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, xml
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.