Upgrade to Apache Camel 3

[davsclaus]

Beware I was not able to test this locally as I get some error about missing fonts.

[INFO]  ERROR #11321  PLUGIN
[INFO]
[INFO] "gatsby-plugin-prefetch-google-fonts" threw an error while running the onPreBootstrap lifecycle:
[INFO]
[INFO] ENOENT: no such file or directory, stat '.cache/google-fonts//fonts'
[INFO]

[INFO]
[INFO]   Error: ENOENT: no such file or directory, stat '.cache/google-fonts//fonts'
[INFO]
[INFO] ⠹ onPreBootstrap
[ERROR] error Command failed with exit code 1.
[INFO] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

So maybe you guys can check this.

In Apache Camel v3 we have changed the groupId for our spring boot starters, from org.apache.camel to org.apache.camel.springboot. Therefore I created a new camel3 entry in the yaml file. Not sure if this is the correct way if we want to have support for older Camel 2.x on earlier Spring Boot versions.

[snicoll]

Thanks for the PR. We are aware of the font issue and are investigating it.

[snicoll]

Thanks for the PR. There are a number of problems with it.

Is there a place where I can read more about the groupId change in Camel 3?

[snicoll]

Please revert this. I am happy to discuss how to update the description but this shouldn't be part of a dependency upgrade.

[davsclaus]

Okay so I can open another PR with just description change?

[snicoll]

I don't know if we'll change the description to what you've suggested but that discussion should happen independently. Either a dedicated PR or an issue is fine, thank you.

[davsclaus]

Well surely the 3rd party project maintainers should influence what the description is for their project

[snicoll]

I didn't shut it down, did I? Of course, any suggestion to improve the description of an entry is much welcome.

[davsclaus]

Yeah thanks as the one that is currently is a very old description that is out of date and a bit confusing.

How about using what's on the main website

Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data.

https://camel.apache.org/

[snicoll]

We can't have two separate entries for the same artifact. If the artifactId has changed, you can define that as part of the mapping entry (i.e. at the same level you map the version, you can also specify a different groupId).

[davsclaus]

Ah okay so maybe we can just specify the new groupId instead

[davsclaus]

Thanks @snicoll I did some updates, let me know if we are getting closer. The PR can be cleaned up later, or you are surely welcome to squash and put a nice git commit message.

[davsclaus]

And you can read here about the groupId change
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_spring_boot_starters_maven_coordinate_change

[snicoll]

Thanks @davsclaus. I had a look to that link. Unfortunately that doesn't explain why the starter was relocated in a different groupId. Is there some more information about that?

[davsclaus]

Thanks @davsclaus. I had a look to that link. Unfortunately that doesn't explain why the starter was relocated in a different groupId. Is there some more information about that?

Its because Apache Camel v3 are having modules separated more. Its been discussed on the JIRA and Camel mailing lists.

https://issues.apache.org/jira/browse/CAMEL-13643
https://camel.465427.n5.nabble.com/DISCUSS-Changing-the-Maven-group-ID-for-Spring-Boot-starters-td5836268.html

[snicoll]

@davsclaus thanks for the PR, I've polished the proposal so that the mapping is not required going forward, please see 573c1ff.

Feel free to open a PR for additional metadata improvements on the Camel entry.