Github user lresende commented on the issue:
    @srowen @rxin My understanding is that the mvn deploy is what takes care of 
actually publishing the files to maven staging repository :
      $MVN -DzincPort=$ZINC_PORT --settings $tmp_settings -DskipTests 
      ./dev/ 2.10
      $MVN -DzincPort=$ZINC_PORT -Dscala-2.10 --settings $tmp_settings \
        -DskipTests $PUBLISH_PROFILES clean deploy
    So, the suggested fix to remove Kinesis from the $PUBLISH_PROFILES should 
take care or making sure Kinesis won't show up in the maven staging repository 
for the release. 
    @srowen Do you have other concerns ?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to