Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pom_xpath_inject(7) [centos man page]

POM_XPATH_INJECT(7)						Java Packages Tools					       POM_XPATH_INJECT(7)

pom_xpath_inject - inject XML code into POM file SYNOPSIS
%pom_xpath_inject XPath [XML-code] [POM-location] DESCRIPTION
This macro patches specified POM file appending some code as childreen of all XML nodes described by the XPath expression. XPath is an expression describing a set of XML nodes in the POM file to which child code is to be appended. It must be a properly formated XPath 1.0 expression, as described in 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 directory is used. EXAMPLES
%pom_xpath_inject pom:project "<packaging>war</packaging>" - this call sets packaging of POM in current working directory to war. BUGS
POM files use a specific namespace - Currently this namespace needs to be explicitly specified in all XPath POM macros by prefixing all node names with pom:. AUTHOR
Written by Mikolaj Izdebski. REPORTING BUGS
Bugs should be reported through Red Hat Bugzilla at SEE ALSO
pom_add_dep(7), pom_add_parent(7), pom_add_plugin(7), pom_disable_module(7), pom_remove_dep(7), pom_remove_parent(7), pom_remove_plugin(7), pom_set_parent(7), pom_xpath_remove(7), pom_xpath_replace(7), pom_xpath_set(7). JAVAPACKAGES
06/10/2014 POM_XPATH_INJECT(7)

Check Out this Related Man Page

MAVEN(1)							   User Commands							  MAVEN(1)

Maven - Patches one POM file using the Maven dependency rules. SYNOPSIS
mh_patchpom [option]... [pom] [backup] DESCRIPTION
Transform the POM using the transformation rules. Where [pom] is the location of the POM file to transform. Default to pom.xml [backup] is the backup file for the pom. Default to OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this POM file -o --no-parent: don't inherit from a parent POM -k --keep-pom-version: keep the original version of the POM but convert all other versions in dependencies and plugins. If there is a parent POM, keeps its version except when the parent is already registered in the Maven repository -e<version>, --set-version=<version>: set the version for the POM, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules -R<rule>, --extra-rule=<rule>: extra rule to apply when cleaning the POM May occur multiple times, instead of or in addition to -r -u<rules> --published-rules=<rules>: path to the file containing the extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/ lishedRules -U<rule>, --extra-published-rule=<rule>: extra rule to publish May occur multiple times, instead of or in addition to -u -i<rules> --ignore-rules=<rules>: path to the file containing the rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules -I<rule>, --extra-ignore-rule=<rule>: extra rule used to remove dependencies from the transformed POM May occur multiple times, instead of or in addition to -i -c<rules> --clean-ignore-rules=<rules>: path to the file containing the rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is debian/maven.cleanIgnoreRules -s --no-rules: don't apply any rules for converting versions, do not even convert versions to the default 'debian' version --no-publish-used-rule: don't publish the rule used to transform a POM's own attributes in debian.mavenRules -d --debian-build: transform during a Debian build, which means that some POM elements will be removed -b --build-no-docs: if the build doesn't need to build documentation, use this option to remove some POM elements (in particular plugins) which are useless here and may require extra dependencies and make the packaging harder. -m<repo root>--maven-repo=<repo root>: location of the Maven repository, used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results See also: mh_installpom(1), mh_patchpoms(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)
Man Page