Date: Fri, 29 Mar 2024 00:32:41 +0100 (CET) Message-ID: <1545078992.17567.1711668761708@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17566_1430003773.1711668761707" ------=_Part_17566_1430003773.1711668761707 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Import project informatio= n from Maven POM files. Provides information about required configuration t= o get this import running.
It is possible to import project information from Maven POM<= /a> files. The information is usually added as document or space properties (or both) and m= ade available for reference within the space.
Use the Display Space Property Macro or one of the display properties macros = to reference one of the imported properties.
To get the import of POMs to work, it is currently required to add a settings.xml
. This file is =
looked up in the .m2
directory of the user's home. Where user =
is the user that started the server.
Future versions may allow to attach the settings file to a Confluence pa= ge or provide administration pages to add the settings information. But cur= rently this file is required.
It is not required to install Maven on the serv= er.
To apply changes to the settings.xml you need to deactivate and reactiva= te the add-on.
There are use cases where it is not appropriate to copy all POM properti=
es to a Conflunce page (usually a Metadata document). To skip properties from being imported, add i=
gnore elements to the properties section of your settings.xml
.=
You may ignore properties by a given key or value pattern.
The properties have to be defined in a profile with an identifier of
Here is an example with one key and one value pattern.
<pro= file> <id>de.smartics.projectdoc</id> <properties> <ignore-property-keys> <item>.*password.*</item> <item>gpg.*</item> </ignore-property-keys> <ignore-property-values> <item>\w:.*</item> </ignore-property-values> </properties> </profile>
Each pattern is the content of an item element. Since Maven does not all= ow complex content in a property tag, the tag delimiters have to be escaped= . Here is the unescaped version of the XML above that is better readable (b= ut unfortunately only the above escaped syntax will work).
<pro= file> <id>de.smartics.projectdoc</id> <properties> <ignore-property-keys> <item>.*password.*</item> <item>gpg.*</item> </ignore-property-keys> <ignore-property-values> <item>\w:.*</item> </ignore-property-values> </properties> </profile>
The key pattern will skip any key with the sequence password
in it or starting with gpg
. The value pattern will filter al=
l Window paths (a letter followed by a colon and then any characters).
Per default there is no ignore pattern defined.
The following add-ons provide space blueprints that allow to import POM = information:
A collection of blueprints for Confluence to create and work with docume= ntation for Maven projects.
The following doctypes allow to import POM information: