Usage

See also the Best Practices and Examples document.

When building a "solaris" artifact the plugin will perform these operations:

Copy Resources

The plugin will copy all the resources specified as resources in the POM into the packageRoot directory. Thus the plugin will by default copy anything from src/main/resources into the root of the assembled pkg.

In addition to copying the normal resources it supports a special src/main/resources-solaris directory which is copied in a similar fasion to the normal resources. Having two separate directories make it easier for the developer to separate the Solaris specific files from the files shared between all packaging formats (like RPM and dpkg). Most builds should have the pkginfo and prototype files in this directory.

The special file pkginfo from src/main/resources-solaris will be filtered with the following values:

  • ${project.artifactId}
  • ${project.version}
  • ${project.name}
  • ${project.description}

Note that the plugin does not offer special support for encodings nor filtering of the resources.

Generate Prototype

The generatePrototype configuration element in addition to the default* control the generation of the prototype file. See the Prototype Generation Example section in the examples document for an example and Prototype Generation Reference document for the complete reference.

Note that the ordering in the generatePrototype element is significant. If an object (file, directory etc.) is included in more than one collection or listed explicitly in an entry the last listing of the object will win and be included in the generated prototype.

Create and Package

Install

The standard Install plugin will install the .pkg file into the local repository just like any JAR file.

Deploy

The standard Deploy plugin will deploy the .pkg file into the remote repository just like any JAR file.