Skip to content

Fix CamelGroovyXMLIT test#1719

Open
apupier wants to merge 1 commit intoapache:mainfrom
apupier:fixCamelGroovyXmlIT
Open

Fix CamelGroovyXMLIT test#1719
apupier wants to merge 1 commit intoapache:mainfrom
apupier:fixCamelGroovyXmlIT

Conversation

@apupier
Copy link
Contributor

@apupier apupier commented Mar 19, 2026

the camel-groovy-xml module has been merged in camel-groovy

@apupier apupier changed the title Fix CamelGroovyIT test Fix CamelGroovyXMLIT test Mar 19, 2026
@apupier
Copy link
Contributor Author

apupier commented Mar 19, 2026

I'm wondering if it should not be better to delete this class CamelGroovyXMLIT and move the single method test inside CamelGroovyIT

@apupier apupier force-pushed the fixCamelGroovyXmlIT branch from 0204442 to d5acc92 Compare March 19, 2026 14:17
the camel-groovy-xml module has been merged in camel-groovy
there is also groovyJson new dataformat

Signed-off-by: Aurélien Pupier <apupier@ibm.com>
@apupier apupier force-pushed the fixCamelGroovyXmlIT branch from d5acc92 to 3040484 Compare March 19, 2026 14:17
@apupier
Copy link
Contributor Author

apupier commented Mar 19, 2026

I'm wondering if it should not be better to delete this class CamelGroovyXMLIT and move the single method test inside CamelGroovyIT

By writing it, I was even more convinced to do it this way. It also allows to add the check for the dataformat for groovyJson which was added

@apupier apupier requested a review from oscerd March 19, 2026 14:18
@apupier
Copy link
Contributor Author

apupier commented Mar 20, 2026

the failure on the PR sound sunrelated. The output log of the maven build is saying "success" but there are weird messages from othe rpart of the github action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants