EMP-Connector
EMP-Connector copied to clipboard
forcedotcom
push to maven?
My apologies. I will try to see if I can get this done - at least in SNAPSHOT mode - soonish (safe harbor n' all that). I would hope to get the crank turned at least once by the end of the week.
@sfdc-hhildebrand thanks that would be great. If anyone wants to reference jar locally here is the workaround. Point the systemPath to where your jar is.
<dependency>
<groupId>com.salesforce.conduit</groupId>
<artifactId>emp-connector</artifactId>
<version>0.0.1-SNAPSHOT</version>
<systemPath>${project.basedir}/lib/emp-connector-0.0.1-SNAPSHOT-phat.jar</systemPath>
</dependency>
Apologies. We're a few weeks away from release and there's a lot going on, unfortunately. This would have been done already, but our internal CIs are restricted and protected (of course) and can't build external systems and such. Thus, I have to go do some external stuff and it's a decent amount of bureaucratic stuff to deal with.
Any update on this? I couldn't seem to find emp-connector on maven.
@tmichels-brightplan - Could you please share the jar file that you have created to reference it locally. Also, I request you to provide the steps to be followed for creating the local jar file. Thanks!
@prudhvikonda when you do mvn clean install the jar should be built, follow these steps to deploy the jar into your project: https://thysmichels.com/2017/06/04/heroku-deploy-local-jar-to-maven-dependencies/
You can use jitpack as workaround for this: https://jitpack.io/#forcedotcom/EMP-Connector
push a jar to maven
@tuddman What do you mean push to maven? How do you exactly want to implement this? Do you mean pushing the EMP-Connector JAR to maven repository and referencing it in your POM.xml file? As others have pointed out, you can just reference this locally..
@madzskill by 'push to maven': yes, I meant pushing the JAR to maven repository ... so that any & all projects in the world that may want to include the EMP-Connector as a dependency can do so in a deterministic, version-ed way that can be built and tested in all sorts of CI/CD or cloud based environments.
I'll leave it to others to cite the many reasons why this approach is universally preferred to 'just reference this locally'
@sfdc-hhildebrand any update on this? It seems this is package definitely has enough traffic so as to publish it to maven. I would definitely not prefer to host this jar locally. We need this package for our production SalesForce workflow. Please advise.
