This repository contains code for the Java version (currently in preview) of the Microsoft Bot Framework SDK, which is part of the Microsoft Bot Framework - a comprehensive framework for building enterprise-grade conversational AI experiences.

This SDK enables developers to model conversation and build sophisticated bot applications using JavaScript. SDKs for .NET, Python and JavaScript are also available.

To get started building bots using the SDK, see the Azure Bot Service Documentation. If you are an existing user, then you can also find out what's new with Bot Framework.

For more information jump to a section below.

• Build status
• Getting started
• Getting support and providing feedback
• Contributing and our code of conduct
• Reporting security sssues

Build Status

Branch	Description	Build Status	Coverage Status
Main	Preview 8 Builds

Getting Started

To get started building bots using the SDK, see the Azure Bot Service Documentation.

The Bot Framework Samples includes a rich set of samples repository.

If you want to debug an issue, would like to contribute, or understand how the Bot Builder SDK works, instructions for building and testing the SDK are below.

Prerequisites

• Git
• Java
• Maven

Clone

Clone a copy of the repo:

git clone https://github.com/Microsoft/botbuilder-java.git

Change to the SDK's directory:

cd botbuilder-java

Now at the command prompt type:

mvn clean install

Build and test locally

Any IDE that can import and work with Maven projects should work. As a matter of practice we use the command line to perform Maven builds. If your IDE can be configured to defer build and run to Maven it should also work.

• Java

  • We use the Azul JDK 8 to build and test with. While not a requirement to develop the SDK with, it is recommended as this is what Azure is using for Java 1.8. If you do install this JDK, make sure your IDE is targeting that JVM, and your path (from command line) and JAVA_HOME point to that.

• Visual Studio Code

  • Extensions
    • Java Extension Pack by Microsoft
    • EditorConfig for VS Code by EditorConfig (Recommended)

• IntelliJ

  • Extensions
    • Checkstyle by IDEA
  • Recommended setup
    • When importing the SDK for the first time, make sure "Auto import" is checked.

Linting rules

This project uses linting rules to enforce code standardization. These rules are specified in the file bot-checkstyle.xml with CheckStyle and are hooked to Maven's build cycle.

INFO: Since the CheckStyle and PMD plugins are hooked into the build cycle, this makes the build fail in cases where there are linting warnings in the project files. Errors will be in the file ./target/checkstyle-result.xml and ./target/pmd.xml.

CheckStyle is available in different flavours:

• Visual Studio Code plugin
• IntelliJ IDEA plugin
• Eclipse plugin
• CLI Tool

INFO: Be sure to configure your IDE to use the file bot-checkstyle.xml instead of the default rules.

Getting support and providing feedback

Below are the various channels that are available to you for obtaining support and providing feedback. Please pay carful attention to which channel should be used for which type of content. e.g. general "how do I..." questions should be asked on Stack Overflow, Twitter or Gitter, with GitHub issues being for feature requests and bug reports.

Github issues

Github issues should be used for bugs and feature requests.

Stack overflow

Stack Overflow is a great place for getting high-quality answers. Our support team, as well as many of our community members are already on Stack Overflow providing answers to 'how-to' questions.

Azure Support

If you issues relates to Azure Bot Service, you can take advantage of the available Azure support options.

Twitter

We use the @botframework account on twitter for announcements and members from the development team watch for tweets for @botframework.

Gitter Chat Room

The Gitter Channel provides a place where the Community can get together and collaborate.

Contributing and our code of conduct

We welcome contributions and suggestions. Please see our contributing guidelines for more information.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT License.