Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Document Properties Marker
overridefalse
Short DescriptionThe plugin is part of a development process. Therefore there are some prerequisites to get started.
Doctypetopichide
NamePrerequisites
Short Name
Parent
Parent Property
propertyParent
property-nameName

Audience

Name List
doctyperole
render-no-hits-as-blanktrue
namesMaven Plugin Developer
propertyAudience


Level of Experience

Name List
doctypeexperience-level
render-no-hits-as-blanktrue
namesNovice
propertyLevel of Experience


Expected Duration
Subject
Name List
doctypesubject
propertySubject

Categories
Name List
doctypecategory
propertyCategories

Tags
Tag List
propertyTags

Iteration

Iteration
valuefinished

hide
Type
Name List
doctypetopic-type
render-no-hits-as-blanktrue
propertyType

Sponsors
Name List
doctypestakeholder
render-no-hits-as-blanktrue
propertySponsors

Sort Keyhide
Section
show-titlefalse
titleDescription

Using the DTSMP to create doctypes for the PDAC1 requires expertise in a number of fields.

Section
titleSummary

Section
titlePrerequisites

Section
titleConfluence

Users need also know how page and space blueprints for Confluence work.

The plugin does not support many details in dealing with them, so expect to be opening the atlassian-plugin.xml, JavaScript, CSS, and Soy files.

Section
titleMaven

We assume readers are familiar with Maven, especially POM files and the concept of archetypes.

Section
titleLicense Plugin

Since the license plugin for maven is configured with the generated POM file, you need to apply license file headers (mvn initialize license:format) before running mvn install.

Section
titleMaven Settings

To run the short form of commands shown in this usage scenario, the plugin group de.smartics.maven.plugin needs to be registered in the Maven Settings file.

Code Block
languagexml
<settings
  xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <pluginGroups>
    ...
    <pluginGroup>de.smartics.maven.plugin</pluginGroup>
    ...
  </pluginGroups>
</settings>
Section
titleAtlassian SDK

You also need to have the Atlassian Software Development Kit (SDK) and to know how to work with it.

Section
titleAtlassian Artifact Server

This includes access to the Atlassian artifact server since the POM file declares dependencies to Atlassian artifacts.

Section
titleAccess Maven Plugin

The Doctypes Maven Plugin (and the archetype it uses) is available on the public smartics Artifact server.

Section
titleprojectdoc Artifacts

You'll also need to manually install the projectdoc artifacts to your local artifact repository. This may be an internal artifact server.

Content Marker
idManually install projectdoc Artifacts

To actually compile and start the project, you need to have the references artifacts on your artifact repository. Access to Atlassian's artifacts should already been configured when you have installed the Atlassian SDK.

You need to download the projectdoc artifacts and install them manually since they are currently not available on a public repository.

Here are the coordinates of the compile time dependency (download trial version of the projectdoc Toolbox from the Atlassian Marketplace).

Code Block Placeholder
    <dependency>
      <groupId>de.smartics.atlassian.confluence</groupId>
      <artifactId>smartics-projectdoc-confluence</artifactId>
      <version>${version.smartics-projectdoc-confluence}</version>
    </dependency>

And this is the additional runtime dependency (download free version of the projectdoc Core Blueprints Add-on from the Atlassian Marketplace).

Code Block Placeholder
<pluginArtifact>
  <groupId>de.smartics.atlassian.confluence</groupId>
  <artifactId>smartics-projectdoc-confluence-space-core</artifactId>
  <version>${version.smartics-projectdoc-confluence-space-core}</version>
</pluginArtifact>
Section
titlePlugin Configuration

The project settings allow to specify defaults (for instance groupId and artifactIdPrefix) for the creation of new projects.

It is recommended to store the organization specific defaults in that file.

Section
titleSubordinate Topics
Display Table
doctypetopic
render-no-hits-as-blanktrue
selectName, Short Description
restrict-to-immediate-childrentrue
sort-bySort Key, Name
Section
required-permissionswrite-access
titleNotes

Section
titleReferences

Section
titleResources