Public

<init>

value

Creating JSON documents from java classes using gson

A class for turning a byte stream into a character stream. Data read from the
source input stream is

java.io.InputStreamReader

An immutable arbitrary-precision signed integer.FAST CRYPTOGRAPHY
This implementation is efficient f

java.math.BigInteger

A linear collection that supports element insertion and removal at both ends.
The name deque is shor

java.util.Deque

LinkedHashMap is an implementation of Map that guarantees iteration order. All
optional operations a

java.util.LinkedHashMap

Breaks a string into tokens; new code should probably use String#split.>  
// Legacy code: 
StringTo

java.util.StringTokenizer

A TimeUnit represents time durations at a given unit of granularity and provides
utility methods to 

java.util.concurrent.TimeUnit

onCreateOptionsMenu

getResourceAsStream

getSystemService

/**
 * An internal class specifying a P2 ContextProvider for rendering a Web Item.
 */

/**
 * Models an XWork action contained in its own XWork Package. Includes support for modelling result types and
 * interceptors.
 *
 * Note that this bean is not publicly exposed, and thus does not contain user-facing javadocs.
 */

/**
     * Builds a context-relative URL to the action modelled by this bean.
     *
     * @return the URL of the action
     */

/**
 * Defines a text field which may appear in control extension points such as the property panel
 *
 * <h2>Example</h2>
 *
 * @exampleJson {@link com.atlassian.plugin.connect.modules.confluence.beans.ConnectConfluenceJsonExamples#CONTROL_EXAMPLE}
 * @schemaTitle TextControl
 */

/**
     * The type field must be set to 'text'
     */

/**
     * The Macro Parameter identifier used to store the text
     */

/**
 * <p>The add-on descriptor is a JSON file (<code>atlassian-connect.json</code>) that describes the add-on to the Atlassian application.
 * The descriptor includes general information for the add-on, as well as the modules that the add-on wants to use or
 * extend.</p>
 *
 * <p>If you're familiar with Java add-on development with previous versions of the Atlassian Plugin Framework, you may already be
 * familiar with the `atlassian-plugin.xml` descriptors. The `atlassian-connect.json` serves the same function.</p>
 *
 * <p>The descriptor serves as the glue between the remote add-on and the Atlassian application. When an administrator for a
 * cloud instance installs an add-on, what they are really doing is installing this descriptor file, which
 * contains pointers to your service. You can see an example below.</p>
 *
 * <p>For details and application-specific reference information on the descriptor please refer to the "jira modules"
 * and "confluence modules" sections of this documentation. But we'll call out a few highlights from the example here.</p>
 *
 * <p>Since Atlassian Connect add-ons are remote and largely independent from the Atlassian application, they can be changed
 * at any time, without having to create a new version or report the change to the Atlassian instance. The changes are
 * reflected in the Atlassian instance immediately (or at least at page reload time).</p>
 *
 * <p>However, some add-on changes require a change to the descriptor file itself. For example, an add-on could be modified
 * to have a new page module. Since this requires a page module declaration in the descriptor, it means making an updated
 * descriptor available. Until that updated descriptor is re-installed into the Atlassian Product that change in the descriptor
 * file will not take effect. To propagate a change in the descriptor to the Atlassian products, you need to create a new version
 * of the add-on in its Marketplace listing. The Marketplace will take care of the rest: informing administrators
 * and automatically installing the available update. See [Upgrades](../developing/upgrades.html) for more details.</p>
 *
 * <div class="aui-message aui-message-info">
 *     <p class="title">
 *         <strong>Validating your descriptor</strong>
 *     </p>
 *     <p>You can validate your descriptor using this <a href="https://atlassian-connect-validator.herokuapp.com/validate">handy tool</a>.</p>
 * </div>
 *
 * <h2>Example</h2>
 *
 * @exampleJson {@link com.atlassian.plugin.connect.modules.beans.ConnectJsonExamples#ADDON_EXAMPLE}
 * @schemaTitle Add-On Descriptor
 * @since 1.0
 */

// The below constants are limits of the db columns,

// check in the components/core/src/main/resources/db/connect-migrations/V0004_0*.sql files before changing!

/**
     * A unique key to identify the add-on.
     * This key must be <= 80 characters, must only contain alphanumeric characters, dashes, underscores, and dots.
     */

// for now this feature is not publicly available

/**
     * The human-readable name of the add-on
     */

/**
     * <b>NOTE</b> This field is reserved for Atlassian Marketplace. Any value provided will be ignored.
     *
     * The version of the add-on. Upon registration of a new add-on version in Atlassian Marketplace, a value for this
     * field is generated and subsequently provided to the Universal Plugin Manager.
     */

/**
     * The API version is an OPTIONAL integer. If omitted we will infer an API version of 1.
     *
     * The intention behind the API version is to allow vendors the ability to beta test a major revision to their Connect add-on as a private version,
     * and have a seamless transition for those beta customers (and existing customers) once the major revision is launched. 
     *
     * Vendors can accomplish this by listing a new private version of their add-on, with a new descriptor hosted at a new URL. 
     *
     * They use the Atlassian Marketplace's access token facilities to share this version with customers (or for internal use). 
     * When this version is ready to be taken live, it can be transitioned from private to public, and all customers will be seamlessly updated.
     *
     * It's important to note that this approach allows vendors to create new versions manually, despite the fact that in the common case, the versions are automatically created.
     * This has a few benefits-- for example, it gives vendors the ability to change their descriptor URL if they need to 
     * (the descriptor URL will be immutable for existing versions)
     */

/**
     * A human readable description of what the add-on does. The description will be visible in the `Manage Add-ons`
     * section of the administration console. Provide meaningful and identifying information for the instance administrator.
     */

/**
     * The vendor who is offering the add-on
     */

/**
     * A set of links that the add-on wishes to publish
     *
     * @exampleJson {@see com.atlassian.plugin.connect.modules.beans.ConnectJsonExamples#LINKS_EXAMPLE}
     */

/**
     * Allows the add on to register for plugin lifecycle notifications
     */

/**
     * The base url of the remote add-on, which is used for all communications back to the add-on instance. Once the add-on is installed in a product, the add-on's baseUrl
     * cannot be changed without first uninstalling the add-on. This is important; choose your baseUrl wisely before making your add-on public.
     *
     * The baseUrl must start with ``https://`` to ensure that all data is sent securely between our [cloud instances](../developing/cloud-installation.html)
     * and your add-on.
     *
     * Note: each add-on must have a unique baseUrl. If you would like to serve multiple add-ons from the same host, consider adding a path prefix into the baseUrl.
     */

/**
     * Defines the authentication type to use when signing requests between the host application and the connect add on.
     */

/**
     * Whether or not to enable licensing options in the UPM/Marketplace for this add on
     */

/**
     * Set of [scopes](../scopes/scopes.html) requested by this add on
     *
     * @exampleJson {@see com.atlassian.plugin.connect.modules.beans.ConnectJsonExamples#SCOPES_EXAMPLE}
     */

/**
     * The list of modules this add-on provides.
     */

// Only used for shallow schema generation

/**
     * A unique key to identify the add-on.
     * This key must be <= 80 characters.
     */

How to useSchemaIgnore in com.atlassian.json.schema.annotation

Best Java code snippets using com.atlassian.json.schema.annotation.SchemaIgnore (Showing top 8 results out of 315)

How to use
SchemaIgnore
in
com.atlassian.json.schema.annotation