andreaTP commented on PR #3994: URL: https://github.com/apache/camel-k/pull/3994#issuecomment-1398477467
> who is going to consume such new configurations Here we are publishing standard Java Artifacts (i.e. a `jar` file and additional metadata) not configuration. Users that want to programmatically access camel-k Custom Resources with a typed interface using Java can add the dependency to their project and use it as shown in the snippet above. > how the jar will end up into `com.github.andreaTP:camel-k:0.0.2-SNAPSHOT` `com.github.andreaTP` comes from the fact that I published using my fork of this project, if you decide to merge this PR the published artifacts will be named: `com.github.apache:camel-k:<version-released>`, this is an intrinsic of https://jitpack.io/ > I suppose you have some process that will use this configuration for publishing the artifact, is it so? that's jitpack.io , you can publish the library to Maven Central but this will require more setup/credentials etc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
