pom_set_parent – set parent POM reference in POM file Synopsis %pom_set_parent groupId*:*artifactId[*:*version] [POM-location] Description This macro patches specified POM file setting reference to parent POM to specified groupId, artifactId and version. This macros first removes parent POM reference and then adds a new one. It’s (more or less) equivalent to call to %pom_remove_parent followed by…
pom_remove_plugin – remove Maven plugin invocation from POM file Synopsis %pom_remove_plugin [groupId]:[artifactId] [POM-location] Description This macro patches specified POM file not to contain invocations of given Maven plugin. groupId and artifactId are identifiers of Maven group and artifact of the plugin which invocation is to be removed. If they are ommited then all identifiers are…
pom_remove_parent – remove parent POM reference from POM file Synopsis %pom_remove_parent [POM-location] Description This macro patches specified POM file removing reference to parent POM. POM location can be either a full path to the POM file, or a path to the directory containing pom.xml. If POM location is not given then pom.xml from current working…
pom_remove_dep – remove dependency on Maven artifact from POM file Synopsis %pom_remove_dep [groupId]:[artifactId] [POM-location] Description This macro patches specified POM file not to contain dependencies on given Maven artifact. groupId and artifactId are identifiers of Maven group and artifact of the module on which dependency is to be removed. If they are ommited then all…
pom_disable_module – disable given project module in POM file Synopsis %pom_disable_module module-name [POM-location] Description This macro patches specified POM file not to contain reference to given project module. Module name is the exact name of the module to be disabled. It must not be ommited. POM location can be either a full path to the…
pom_change_dep – change dependency in Maven POM file or Ivy module Synopsis %pom_change_dep [OPTIONS] SOURCE_ARTIFACT CHANGED_ARTIFACT [POM-location]… [extra-XML] %pom_change_dep [OPTIONS] SOURCE_ARTIFACT CHANGED_ARTIFACT [Ivy-module-location]… [extra-XML] Options -r Work in recursive mode. That means that given dependency is also changed in all enabled submodules of given POM file(s). Has no effect if the file is not Maven…
pom_add_plugin – add plugin invocation to POM file Synopsis %pom_add_plugin groupId*:*artifactId[*:*version] [POM-location] [extra-XML] Description This macro patches specified POM file adding plugin invocation of given groupId and artifactId. groupId and artifactId are identifiers of Maven plugin artifact of which invocation is to be added. groupId may be ommited, in which case value of "org.apache.maven.plugins" is…
pom_add_parent – add parent POM reference to POM file Synopsis %pom_add_parent groupId*:*artifactId[*:*version] [POM-location] Description This macro patches specified POM file adding a reference to parent POM with specified groupId, artifactId and version. groupId and artifactId are identifiers of Maven group and artifact of the POM to be referenced as parent POM. They must be specified….
pom_add_dep – add dependency to POM file Synopsis %pom_add_dep groupId*:*artifactId[:*version[:*scope]] [POM-location] [extra-XML] %pom_add_dep_mgmt groupId:articId[:*version[:*scope]] [POM-location] [extra-XML] Description These macros patch specified POM file adding a dependency on given version of artifactId from groupId, with given scope (if any). pom_add_dep adds the dependency to <dependencies> XML node, while pom_add_dep_mgmt adds it to dependencyManagement. groupId and artifactId…
po4a – framework to translate documentation and other materials Introduction The po4a (PO for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. Table of content This document is organized as follow: 1 Why should I use po4a?…
po4a-runtime – po4a and runtime gettext translation without Autotools Introduction With po4a-build, po4a also includes support for adding translation of runtime script output messages using gettext but without requiring the package to adopt Autotools and the typical ./configure process. Using example Makefile snippets, packages can harness intltool with minimal effort. Layout Documentation translation should NOT…
po-debconf – introduction Description The goal of "debconf" was to make package configuration user-friendly. In order to achieve this, it is important to ensure that users will get the question in their own language. Translators need a framework to easily work on translations without having to track package development; "po-debconf" was designed to be able…
PMIx Constants Synopsis #include <pmix_common.h> Overview PMIx relies on the following types of constants: Maximum Sizes : In order to minimize malloc performance penalties, PMIx utilizes constant-sized arrays wherever possible. These constants provide the user with the maximum size of the various array types. Attributes : . Errors : PMIx uses negative error constants, with…
Process Management Interface – Exascale Synopsis #include <pmix.h> Overview The Process Management Interface (PMI) has been used for quite some time as a means of exchanging wireup information needed for interprocess communication. Two versions (PMI-1 and PMI-2) have been released as part of the MPICH effort. While PMI-2 demonstrates better scaling properties than its PMI-1…
pkeys – overview of Memory Protection Keys Description Memory Protection Keys (pkeys) are an extension to existing page-based memory permissions. Normal page permissions using page tables require expensive system calls and TLB invalidations when changing permissions. Memory Protection Keys provide a mechanism for changing protections without requiring modification of the page tables on every permission…
pipe – overview of pipes and FIFOs Description Pipes and FIFOs (also known as named pipes) provide a unidirectional interprocess communication channel. A pipe has a read end and a write end. Data written to the write end of a pipe can be read from the read end of the pipe. A pipe is created…
pilot-link – A suite of tools for communicating with Palm handhelds, such as those made by Palm, Handspring, Handera, TRGPro, Sony or other Palm Compatible Handheld PDA device. Section Pilot-link: Overview Description The pilot-link suite of tools contains a series of conduits, libraries, and language bindings for moving information to and from your Palm device…
pigeonhole – Overview of the Pigeonhole project’s Sieve support for the Dovecot secure IMAP and POP3 server Description The Pigeonhole project <http://pigeonhole.dovecot.org> adds support for the Sieve language (RFC 5228) and the ManageSieve protocol (RFC 5804) to the Dovecot Secure IMAP and POP3 Server (dovecot(1)). In the literal sense, a pigeonhole is a a hole…
pid_namespaces – overview of Linux PID namespaces Description For an overview of namespaces, see namespaces(7). PID namespaces isolate the process ID number space, meaning that processes in different PID namespaces can have the same PID. PID namespaces allow containers to provide functionality such as suspending/resuming the set of processes in the container and migrating the…
persistent-keyring – per-user persistent keyring Description The persistent keyring is a keyring used to anchor keys on behalf of a user. Each UID the kernel deals with has its own persistent keyring that is shared between all threads owned by that UID. The persistent keyring has a name (description) of the form _persistent.<UID> where <UID>…