Hi Craig
Thanks for the help.
We may also consider switching to a more friendly protobuf maven plugin
https://issues.apache.org/jira/browse/CAMEL-20788
You are welcome to take a look at that too
On Sat, May 18, 2024 at 12:31 AM Craig Ziesman wrote:
> Unlike camel-salesforce, camel-grpc doesn'
Unlike camel-salesforce, camel-grpc doesn't actually compile any protobuf
definitions, so protoc never gets called.
I think that the upshot here is that the Camel build will fail on
Windows/ARM, but since the official release isn't built there anyway it's
not a major concern.
I did file a feature
Maybe take a look at camel-grpc to see how protoc is handled for the
various platforms & CPU architectures:
https://github.com/apache/camel/blob/main/components/camel-grpc/pom.xml
--
James
On Thu, 16 May 2024 at 19:17, Craig Ziesman wrote:
> I opened an issue (https://issues.apache.org/jira/br
Hi
The intent is not for end users to build their own camel distribution.
The source code is built and released to maven central as JARs, where end
users will consume the releases.
If there are odd combinations of osx and cpu arch where some camel
components cannot build special code like protobu
I opened an issue (https://issues.apache.org/jira/browse/CAMEL-20706) to
address the fact that the camel-salesforce component build fails on Windows
running on ARM.
It turns out that the source builds without errors, but the test build
fails because the protoc executable is unavailable on Windows/
