📝 Set documentation version to Camel Quarkus 2.5.x

[zbendhiba]

No description provided.

[zbendhiba]

I wonder if this one works as this apache/camel-website#691 not merged yet

[zbendhiba]

I fixed the qute.json file
But I'm skeptical that this could work. Every time I build the project, the antora.yaml file is updated. The version goes from 2.5.x to next. So I'm expecting the mvn install to fail.

[jamesnetherton]

The version goes from 2.5.x to next.

Ah yeah the update script sees SNAPSHOT in the project version and will use next.

I think we should just merge this PR. It's pretty unlikely anyone is going to do a full build the 2.5.x anyway. We can fix up the antora update script and try to make it smarter later.

[djencks]

For 2.4.x I updated the groovy scripts to not update antora.yml: efda8ea

I'd recommend doing that here too.

[zbendhiba]

I don't know how we could address this in the release process. Is there a way to change automagically those files ?

[zbendhiba]

I guess I can merge this. Thanks for reviews

[djencks]

I couldn't think of an automated way of detecting a non-next branch.

Would it be possible for the release process to add a pom property saying "released" and the groovy script not update the Antora stuff on a released branch?

[ppalaga]

Could please somebody create an issue describing what should happen on release?

[zbendhiba]

@ppalaga Yes, I'd create one to explain all I did. on my TODO list

[ppalaga]

For the record, the issue is here: #3350