Home application where the project to build and its dependencies
+will be temporary deployed. Default value is: ${project.build.directory}/ivyBuildApp.
Define a compiler settings file to configure compilation warnings.
+Such file can be created in the Designer: Window - Preferences -
+Java - Compiler - Errors/Warnings, the corresponding file can
+be found in:
+designer-workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.core.prefs
+
+If left empty the plugin will try to load the project specific
+settings file project/.settings/org.eclipse.jdt.core.prefs
+
+These settings are only active when
+AbstractProjectCompileMojo.compilerWarnings is set to
+true. Default value is: .settings/org.eclipse.jdt.core.prefs. User property is: ivy.compiler.settings.
Specifies the default encoding for all source files. By default
+this is the charset of the JVM according to
+Charset.defaultCharset(). You may set it to another
+value like 'UTF-8'. User property is: ivy.compiler.encoding.
Set to true to bypass the generation of ivy data
+classes+webservice processes and compilation of java
+sources. Default value is: false. User property is: ivy.compiler.skip.
Define a compiler settings file to configure compilation warnings.
+Such file can be created in the Designer: Window - Preferences -
+Java - Compiler - Errors/Warnings, the corresponding file can
+be found in:
+designer-workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.core.prefs
+
+If left empty the plugin will try to load the project specific
+settings file project/.settings/org.eclipse.jdt.core.prefs
+
+These settings are only active when
+AbstractProjectCompileMojo.compilerWarnings is set to
+true.
Specifies the default encoding for all source files. By default
+this is the charset of the JVM according to
+Charset.defaultCharset(). You may set it to another
+value like 'UTF-8'.
The auto deployment directory of the engine. Must match the ivy
+engine system property 'deployment.directory' Default value is: deploy. User property is: ivy.deploy.dir.
The path to the Axon Ivy Engine to which we deploy the file.
+The path can reference a remote engine by using UNC paths e.g.
+\\myRemoteHost\myEngineShare Default value is: ${ivy.engine.directory}. User property is: ivy.deploy.engine.dir.
The file to deploy. Can either be a *.iar project file or a *.zip
+file containing a full application (set of projects). By default
+the packed IAR from the IarPackagingMojo.GOAL is used. Default value is: ${project.build.directory}/${project.artifactId}-${project.version}.iar. User property is: ivy.deploy.file.
Id of server configured in settings.xml that specifies the
+administrator user name and password used to authenticate in case
+of HTTP deployment. If you're using an encrypted maven password
+with a settings-security.xml, you may need to define the location
+of this file with the property 'settings.security' (default
+location is ~/.settings-security.xml) User property is: ivy.deploy.server.id.
The target file format as which the project will be deployed into
+the process model version (PMV).
+
+
+
+
AUTO: Keep the format of the origin project file
+if possible. Deploys IAR or ZIP projects into a ZIP process model
+version.
+But if the target PMV already exists as expanded directory, the new
+version will be expanded as well.
+
+
PACKED: Enforce the deployment of a project as
+zipped file. Normal (expanded) project directories will be
+compressed into a ZIP during deployment.
+
+
EXPANDED: Enforce the deployment of a project as
+expanded file directory.
+This is recommended for projects that change the project files at
+runtime. E.g. projects that use the Content Management (CMS) write
+API.
+The expanded format behaves exactly like projects deployed with
+Axon Ivy 7.0 or older. You might choose to deploy expanded projects
+in order to avoid ReadOnlyFileSystemException at
+runtime.
+Warning: Expanded projects will perform slower at
+runtime and are therefore not recommended.
+
Default value is: AUTO. User property is: ivy.deploy.target.file.format.
If set to true then test users defined in the projects
+are deployed to the engine. If set to auto then test
+users will only deployed when engine runs in demo mode. Should only
+be used for testing.
+
+
This option is only in charge if security system is set to
+Ivy Security System. This means if the security system is
+Active Directory or Novell eDirectory test users will never
+deployed.
Default value is: AUTO. User property is: ivy.deploy.test.users.
The maximum amount of seconds that we wait for a deployment result
+from the engine Default value is: 30. User property is: ivy.deploy.timeout.seconds.
Configure if the test engine gets copied to the maven target
+folder. With this you can start each test cycle with a clean
+engine. Integration tests may leave resources like deployed
+projects behind which may lead to unwanted side effects on the next
+test cycle.
+
+
+
+
COPY_FROM_CACHE = copy the engine if it comes from
+the engineCacheDirectory.
+
+
MODIFY_EXISTING = don't copy the engine, this
+could lead to unforeseen behaviour if the same engine is used
+multiple times.
+
+
COPY_FROM_TEMPLATE = always copy the engine. If
+you have a preconfigured engine in the engineDirectory
+it will be copied as well.
+
+
+
+
Note: that we advise you to move
+the configuration of such engine to the build cycle itself instead
+of using a preconfigured one.
+
+
+
Default value is: COPY_FROM_CACHE. User property is: ivy.test.engine.
The path to the Axon Ivy Engine to which we deploy the file.
+The path can reference a remote engine by using UNC paths e.g.
+\\myRemoteHost\myEngineShare
The file to deploy. Can either be a *.iar project file or a *.zip
+file containing a full application (set of projects). By default
+the packed IAR from the IarPackagingMojo.GOAL is used.
Id of server configured in settings.xml that specifies the
+administrator user name and password used to authenticate in case
+of HTTP deployment. If you're using an encrypted maven password
+with a settings-security.xml, you may need to define the location
+of this file with the property 'settings.security' (default
+location is ~/.settings-security.xml)
The target file format as which the project will be deployed into
+the process model version (PMV).
+
+
+
+
AUTO: Keep the format of the origin project file
+if possible. Deploys IAR or ZIP projects into a ZIP process model
+version.
+But if the target PMV already exists as expanded directory, the new
+version will be expanded as well.
+
+
PACKED: Enforce the deployment of a project as
+zipped file. Normal (expanded) project directories will be
+compressed into a ZIP during deployment.
+
+
EXPANDED: Enforce the deployment of a project as
+expanded file directory.
+This is recommended for projects that change the project files at
+runtime. E.g. projects that use the Content Management (CMS) write
+API.
+The expanded format behaves exactly like projects deployed with
+Axon Ivy 7.0 or older. You might choose to deploy expanded projects
+in order to avoid ReadOnlyFileSystemException at
+runtime.
+Warning: Expanded projects will perform slower at
+runtime and are therefore not recommended.
If set to true then test users defined in the projects
+are deployed to the engine. If set to auto then test
+users will only deployed when engine runs in demo mode. Should only
+be used for testing.
+
+
This option is only in charge if security system is set to
+Ivy Security System. This means if the security system is
+Active Directory or Novell eDirectory test users will never
+deployed.
Configure if the test engine gets copied to the maven target
+folder. With this you can start each test cycle with a clean
+engine. Integration tests may leave resources like deployed
+projects behind which may lead to unwanted side effects on the next
+test cycle.
+
+
+
+
COPY_FROM_CACHE = copy the engine if it comes from
+the engineCacheDirectory.
+
+
MODIFY_EXISTING = don't copy the engine, this
+could lead to unforeseen behaviour if the same engine is used
+multiple times.
+
+
COPY_FROM_TEMPLATE = always copy the engine. If
+you have a preconfigured engine in the engineDirectory
+it will be copied as well.
+
+
+
+
Note: that we advise you to move
+the configuration of such engine to the build cycle itself instead
+of using a preconfigured one.
If set to true, the 'deployFile' will automatically be
+replaced with an ZIP file that contains all IAR dependencies of the
+project.
+This change will only be applied if 'deployFile' has it's default
+value and at least one IAR dependency has been declared. Default value is: true. User property is: ivy.deploy.deps.as.app.
The file to deploy. Can either be a *.iar project file or a *.zip
+file containing a full application (set of projects). By default
+the packed IAR from the IarPackagingMojo.GOAL is used. Default value is: ${project.build.directory}/${project.artifactId}-${project.version}.iar. User property is: ivy.deploy.file.
The target file format as which the project will be deployed into
+the process model version (PMV).
+
+
+
+
AUTO: Keep the format of the origin project file
+if possible. Deploys IAR or ZIP projects into a ZIP process model
+version.
+But if the target PMV already exists as expanded directory, the new
+version will be expanded as well.
+
+
PACKED: Enforce the deployment of a project as
+zipped file. Normal (expanded) project directories will be
+compressed into a ZIP during deployment.
+
+
EXPANDED: Enforce the deployment of a project as
+expanded file directory.
+This is recommended for projects that change the project files at
+runtime. E.g. projects that use the Content Management (CMS) write
+API.
+The expanded format behaves exactly like projects deployed with
+Axon Ivy 7.0 or older. You might choose to deploy expanded projects
+in order to avoid ReadOnlyFileSystemException at
+runtime.
+Warning: Expanded projects will perform slower at
+runtime and are therefore not recommended.
+
Default value is: AUTO. User property is: ivy.deploy.target.file.format.
If set to true then test users defined in the projects
+are deployed to the engine. If set to auto then test
+users will only deployed when engine runs in demo mode. Should only
+be used for testing.
+
+
This option is only in charge if security system is set to
+Ivy Security System. This means if the security system is
+Active Directory or Novell eDirectory test users will never
+deployed.
Default value is: AUTO. User property is: ivy.deploy.test.users.
The maximum amount of seconds that we wait for a deployment result
+from the engine Default value is: 30. User property is: ivy.deploy.timeout.seconds.
Configure if the test engine gets copied to the maven target
+folder. With this you can start each test cycle with a clean
+engine. Integration tests may leave resources like deployed
+projects behind which may lead to unwanted side effects on the next
+test cycle.
+
+
+
+
COPY_FROM_CACHE = copy the engine if it comes from
+the engineCacheDirectory.
+
+
MODIFY_EXISTING = don't copy the engine, this
+could lead to unforeseen behaviour if the same engine is used
+multiple times.
+
+
COPY_FROM_TEMPLATE = always copy the engine. If
+you have a preconfigured engine in the engineDirectory
+it will be copied as well.
+
+
+
+
Note: that we advise you to move
+the configuration of such engine to the build cycle itself instead
+of using a preconfigured one.
+
+
+
Default value is: COPY_FROM_CACHE. User property is: ivy.test.engine.
If set to true, the 'deployFile' will automatically be
+replaced with an ZIP file that contains all IAR dependencies of the
+project.
+This change will only be applied if 'deployFile' has it's default
+value and at least one IAR dependency has been declared.
The file to deploy. Can either be a *.iar project file or a *.zip
+file containing a full application (set of projects). By default
+the packed IAR from the IarPackagingMojo.GOAL is used.
The target file format as which the project will be deployed into
+the process model version (PMV).
+
+
+
+
AUTO: Keep the format of the origin project file
+if possible. Deploys IAR or ZIP projects into a ZIP process model
+version.
+But if the target PMV already exists as expanded directory, the new
+version will be expanded as well.
+
+
PACKED: Enforce the deployment of a project as
+zipped file. Normal (expanded) project directories will be
+compressed into a ZIP during deployment.
+
+
EXPANDED: Enforce the deployment of a project as
+expanded file directory.
+This is recommended for projects that change the project files at
+runtime. E.g. projects that use the Content Management (CMS) write
+API.
+The expanded format behaves exactly like projects deployed with
+Axon Ivy 7.0 or older. You might choose to deploy expanded projects
+in order to avoid ReadOnlyFileSystemException at
+runtime.
+Warning: Expanded projects will perform slower at
+runtime and are therefore not recommended.
If set to true then test users defined in the projects
+are deployed to the engine. If set to auto then test
+users will only deployed when engine runs in demo mode. Should only
+be used for testing.
+
+
This option is only in charge if security system is set to
+Ivy Security System. This means if the security system is
+Active Directory or Novell eDirectory test users will never
+deployed.
Configure if the test engine gets copied to the maven target
+folder. With this you can start each test cycle with a clean
+engine. Integration tests may leave resources like deployed
+projects behind which may lead to unwanted side effects on the next
+test cycle.
+
+
+
+
COPY_FROM_CACHE = copy the engine if it comes from
+the engineCacheDirectory.
+
+
MODIFY_EXISTING = don't copy the engine, this
+could lead to unforeseen behaviour if the same engine is used
+multiple times.
+
+
COPY_FROM_TEMPLATE = always copy the engine. If
+you have a preconfigured engine in the engineDirectory
+it will be copied as well.
+
+
+
+
Note: that we advise you to move
+the configuration of such engine to the build cycle itself instead
+of using a preconfigured one.
The maximum length of a display line, should be positive.
+
+
+
+
Type: int
+
+
Required: No
+
+
User Property: lineLength
+
+
Default: 80
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/snapshot/11.4/images/accessories-text-editor.png b/snapshot/11.4/images/accessories-text-editor.png
new file mode 100644
index 00000000..abc3366e
Binary files /dev/null and b/snapshot/11.4/images/accessories-text-editor.png differ
diff --git a/snapshot/11.4/images/add.gif b/snapshot/11.4/images/add.gif
new file mode 100644
index 00000000..1cb3dbf9
Binary files /dev/null and b/snapshot/11.4/images/add.gif differ
diff --git a/snapshot/11.4/images/apache-maven-project-2.png b/snapshot/11.4/images/apache-maven-project-2.png
new file mode 100644
index 00000000..a44db6ed
Binary files /dev/null and b/snapshot/11.4/images/apache-maven-project-2.png differ
diff --git a/snapshot/11.4/images/application-certificate.png b/snapshot/11.4/images/application-certificate.png
new file mode 100644
index 00000000..cc6aff61
Binary files /dev/null and b/snapshot/11.4/images/application-certificate.png differ
diff --git a/snapshot/11.4/images/contact-new.png b/snapshot/11.4/images/contact-new.png
new file mode 100644
index 00000000..ebc4316d
Binary files /dev/null and b/snapshot/11.4/images/contact-new.png differ
diff --git a/snapshot/11.4/images/document-properties.png b/snapshot/11.4/images/document-properties.png
new file mode 100644
index 00000000..34c2409a
Binary files /dev/null and b/snapshot/11.4/images/document-properties.png differ
diff --git a/snapshot/11.4/images/drive-harddisk.png b/snapshot/11.4/images/drive-harddisk.png
new file mode 100644
index 00000000..d7ce475f
Binary files /dev/null and b/snapshot/11.4/images/drive-harddisk.png differ
diff --git a/snapshot/11.4/images/fix.gif b/snapshot/11.4/images/fix.gif
new file mode 100644
index 00000000..b7eb3dc4
Binary files /dev/null and b/snapshot/11.4/images/fix.gif differ
diff --git a/snapshot/11.4/images/icon_error_sml.gif b/snapshot/11.4/images/icon_error_sml.gif
new file mode 100644
index 00000000..12e9a01a
Binary files /dev/null and b/snapshot/11.4/images/icon_error_sml.gif differ
diff --git a/snapshot/11.4/images/icon_help_sml.gif b/snapshot/11.4/images/icon_help_sml.gif
new file mode 100644
index 00000000..aaf20e6e
Binary files /dev/null and b/snapshot/11.4/images/icon_help_sml.gif differ
diff --git a/snapshot/11.4/images/icon_info_sml.gif b/snapshot/11.4/images/icon_info_sml.gif
new file mode 100644
index 00000000..b7763267
Binary files /dev/null and b/snapshot/11.4/images/icon_info_sml.gif differ
diff --git a/snapshot/11.4/images/icon_success_sml.gif b/snapshot/11.4/images/icon_success_sml.gif
new file mode 100644
index 00000000..0a195279
Binary files /dev/null and b/snapshot/11.4/images/icon_success_sml.gif differ
diff --git a/snapshot/11.4/images/icon_warning_sml.gif b/snapshot/11.4/images/icon_warning_sml.gif
new file mode 100644
index 00000000..ac6ad6ad
Binary files /dev/null and b/snapshot/11.4/images/icon_warning_sml.gif differ
diff --git a/snapshot/11.4/images/image-x-generic.png b/snapshot/11.4/images/image-x-generic.png
new file mode 100644
index 00000000..ab49efb3
Binary files /dev/null and b/snapshot/11.4/images/image-x-generic.png differ
diff --git a/snapshot/11.4/images/internet-web-browser.png b/snapshot/11.4/images/internet-web-browser.png
new file mode 100644
index 00000000..307d6aca
Binary files /dev/null and b/snapshot/11.4/images/internet-web-browser.png differ
diff --git a/snapshot/11.4/images/logos/build-by-maven-black.png b/snapshot/11.4/images/logos/build-by-maven-black.png
new file mode 100644
index 00000000..919fd0f6
Binary files /dev/null and b/snapshot/11.4/images/logos/build-by-maven-black.png differ
diff --git a/snapshot/11.4/images/logos/build-by-maven-white.png b/snapshot/11.4/images/logos/build-by-maven-white.png
new file mode 100644
index 00000000..7d44c9c2
Binary files /dev/null and b/snapshot/11.4/images/logos/build-by-maven-white.png differ
diff --git a/snapshot/11.4/images/logos/maven-feather.png b/snapshot/11.4/images/logos/maven-feather.png
new file mode 100644
index 00000000..b5ada836
Binary files /dev/null and b/snapshot/11.4/images/logos/maven-feather.png differ
diff --git a/snapshot/11.4/images/network-server.png b/snapshot/11.4/images/network-server.png
new file mode 100644
index 00000000..1d12e193
Binary files /dev/null and b/snapshot/11.4/images/network-server.png differ
diff --git a/snapshot/11.4/images/package-x-generic.png b/snapshot/11.4/images/package-x-generic.png
new file mode 100644
index 00000000..8b7e9e67
Binary files /dev/null and b/snapshot/11.4/images/package-x-generic.png differ
diff --git a/snapshot/11.4/images/profiles/pre-release.png b/snapshot/11.4/images/profiles/pre-release.png
new file mode 100644
index 00000000..d448e850
Binary files /dev/null and b/snapshot/11.4/images/profiles/pre-release.png differ
diff --git a/snapshot/11.4/images/profiles/retired.png b/snapshot/11.4/images/profiles/retired.png
new file mode 100644
index 00000000..f89f6a29
Binary files /dev/null and b/snapshot/11.4/images/profiles/retired.png differ
diff --git a/snapshot/11.4/images/profiles/sandbox.png b/snapshot/11.4/images/profiles/sandbox.png
new file mode 100644
index 00000000..f88b3626
Binary files /dev/null and b/snapshot/11.4/images/profiles/sandbox.png differ
diff --git a/snapshot/11.4/images/remove.gif b/snapshot/11.4/images/remove.gif
new file mode 100644
index 00000000..fc65631c
Binary files /dev/null and b/snapshot/11.4/images/remove.gif differ
diff --git a/snapshot/11.4/images/rss.png b/snapshot/11.4/images/rss.png
new file mode 100644
index 00000000..a9850ee2
Binary files /dev/null and b/snapshot/11.4/images/rss.png differ
diff --git a/snapshot/11.4/images/update.gif b/snapshot/11.4/images/update.gif
new file mode 100644
index 00000000..b2a6d0bf
Binary files /dev/null and b/snapshot/11.4/images/update.gif differ
diff --git a/snapshot/11.4/images/window-new.png b/snapshot/11.4/images/window-new.png
new file mode 100644
index 00000000..0e12ef95
Binary files /dev/null and b/snapshot/11.4/images/window-new.png differ
diff --git a/snapshot/11.4/img/glyphicons-halflings-white.png b/snapshot/11.4/img/glyphicons-halflings-white.png
new file mode 100644
index 00000000..3bf6484a
Binary files /dev/null and b/snapshot/11.4/img/glyphicons-halflings-white.png differ
diff --git a/snapshot/11.4/img/glyphicons-halflings.png b/snapshot/11.4/img/glyphicons-halflings.png
new file mode 100644
index 00000000..a9969993
Binary files /dev/null and b/snapshot/11.4/img/glyphicons-halflings.png differ
diff --git a/snapshot/11.4/index.html b/snapshot/11.4/index.html
new file mode 100644
index 00000000..30edddd0
--- /dev/null
+++ b/snapshot/11.4/index.html
@@ -0,0 +1,90 @@
+
+
+
+
+
+
+
+ Axon Ivy Project Build Plugin –
+
+
+
+
+
+
+
+
+
+
+
+
+
Axon Ivy Project Build Plugin
+
+
+
+
+
+
+
+
+
Last Published: 2024-05-01|
+
+
Version: 11.4.0-SNAPSHOT
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Introduction
+
The project-build-plugin is a Maven plugin that can build Ivy Projects on a developer machine or on a continuous integration server. The plugin provides the following main features:
+
+
Compilation of Ivy Projects
+
Testing of unit and integration-tests against an Ivy Project or the Ivy core classes
+
Packaging of built Ivy Projects as IAR (ivy archive) artifacts
+
Installation of IAR artifacts into the local Maven repository
+
Deployment of single projects or full applications to an Axon Ivy Engine
Enables the automatic installation of an ivy Engine in the
+engineDirectory. If there is yet no engine installed,
+or the ivyVersion does not match, the engine will be
+downloaded from the engineDownloadUrl and unpacked
+into the engineDirectory. Default value is: true. User property is: ivy.engine.auto.install.
Enables the engine artifact download via maven plugin repositories.
+If set to false, the default URL download approach is
+used (see engineDownloadUrl and
+engineListPageUrl properties).
+
+
As there exist no official maven repository containing the
+axonivy engine, it must be published manually to an accessible
+plugin repository. The expected artifact descriptor is:
URL where a packed ivy Engine can be downloaded. E.g.
+https://developer.axonivy.com/download/6.0.10/AxonIvyEngine6.0.10.55478_Windows_x64.zip User property is: ivy.engine.download.url.
URL where a link to the ivy Engine in the expected
+ivyVersion exists. The URL will be used to download
+the required engine if it does not yet exist. The URL should point
+to a site providing HTML content with a link to the engine
+e.g. <a
+href="https://developer.axonivy.com/download/6.0.10/AxonIvyEngine6.0.10.55478_Windows_x64.zip">
+the engine</a> Default value is: https://developer.axonivy.com/download/maven.html. User property is: ivy.engine.list.url.
Engine type that will be downloaded if
+autoInstallEngine is set and the engine must be
+retrieved from the engineListPageUrl. Possible values
+are:
+
+
+
+
All_x64
+
+
Slim_All_x64
+
+
Windows_x64
+
+All_x64 supports Linux and Windows. Slim_All_x64 supports Linux and
+Windows only with the necessary features (e.g. without demo-portal
+or axis). Default value is: Slim_All_x64. User property is: ivy.engine.os.arch.
Enables the automatic installation of an ivy Engine in the
+engineDirectory. If there is yet no engine installed,
+or the ivyVersion does not match, the engine will be
+downloaded from the engineDownloadUrl and unpacked
+into the engineDirectory.
Enables the engine artifact download via maven plugin repositories.
+If set to false, the default URL download approach is
+used (see engineDownloadUrl and
+engineListPageUrl properties).
+
+
As there exist no official maven repository containing the
+axonivy engine, it must be published manually to an accessible
+plugin repository. The expected artifact descriptor is:
URL where a link to the ivy Engine in the expected
+ivyVersion exists. The URL will be used to download
+the required engine if it does not yet exist. The URL should point
+to a site providing HTML content with a link to the engine
+e.g. <a
+href="https://developer.axonivy.com/download/6.0.10/AxonIvyEngine6.0.10.55478_Windows_x64.zip">
+the engine</a>
Engine type that will be downloaded if
+autoInstallEngine is set and the engine must be
+retrieved from the engineListPageUrl. Possible values
+are:
+
+
+
+
All_x64
+
+
Slim_All_x64
+
+
Windows_x64
+
+All_x64 supports Linux and Windows. Slim_All_x64 supports Linux and
+Windows only with the necessary features (e.g. without demo-portal
+or axis).
Shares the classpath of the built ivy project and it's engine as
+public property and tries to auto-configure 'maven-surefire-plugin'
+to use this classpath.
+
+
Attributes:
+
+
+
+
Requires a Maven project to be executed.
+
+
Requires dependency resolution of artifacts in scope: test.
+
+
The goal is not marked as thread-safe and thus does not support parallel builds.
+ 