Hi Pontus, first of all, thank you :) Yeah, I would love to do that, but it brings along another set of other questions: is it up to me/us or Salesforce to publish the jar in Maven central? And to what coordinates, Camels?
That kinda feels more wrong to me :( zoran On Mon, Feb 20, 2017 at 9:48 PM, Pontus Ullgren <[email protected]> wrote: > Hi, > > Would it not be a better solution to publish the jar ourself to maven > central ? > Similare to what SMX project does for other 3rd party libraries that are > not osgi compatible bundles ? > > Just my $0.02 > // Pontus > > > On Mon, 20 Feb 2017 at 15:07 Zoran Regvart <[email protected]> wrote: > >> Hi Cameleers, >> what do you think about adding 3rd party jars to the git repo (as binary >> blobs)? >> >> Background: integration tests for Salesforce component require >> deployment of customizations to the your Salesforce instance, so in >> order to run them you need to make a number of manual steps >> beforehand[1]. >> >> Salesforce publishes a Migration tool[2] as a set of Ant tasks. These >> are packaged as a jar file that is not available on Maven central, so >> in order to use them the user needs to download supply the jar to the >> Maven build. >> >> I would like to automate that and to prescribe the way of managing >> this customizations for future tests, so I think it would be best to >> put that jar in our git repository. >> >> I think this would encourage contributions and allow everyone to run >> the integration tests, for instance in CI. >> >> The license is very liberal, it just requires the inclusion of the >> copyright & disclamer notice. >> >> What do you think? >> >> zoran >> >> [1] >> https://github.com/apache/camel/tree/master/components/camel-salesforce/camel-salesforce-component#running-the-integration-tests >> [2] >> https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/forcemigrationtool_install.htm >> -- >> Zoran Regvart >> -- Zoran Regvart
