META-INF.eosgi-dist.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of eosgi-maven-plugin Show documentation
Show all versions of eosgi-maven-plugin Show documentation
A Maven plugin that runs Integration Tests inside OSGi containers and collects OSGi Bundle dependencies to be able to use them inside any IDE.
The schema of the XML that describes the distribution environment. The XML file is parsed with Velocity before processing. The folling variables can be used:
- distributableArtifacts: List of DistributableArtifact objects
- environment: An EnvironmentConfiguration object
- copyMode: The default copy mode that should be used during distributing artifacts
- escapeTool: A simply utility class that can be used to do escapes
- distUtil: A class that contains util functions that help creating a distribution package.
Artifacts that should be resolved (downloaded and copied) into the distribution package.
Start command is necessary to be able to start integration tests on server.
A maven artifact with additional information.
In case this is an OSGi bundle, additional behavior can be defined.
The target folder where the artifact should be copied to inside the distribution package.
The target name of the artifact file. If not specified, the target file will have the same name as the maven artifact file.
Either creating a symbolic link or copying the artifact file.
A file that will be parsed with Velocity after distributing the artifacts. The following variables can be used:
The schema of the XML that describes the distribution environment. The XML file is parsed with Velocity before processing. The folling variables can be used:
- distributableArtifacts: List of DistributableArtifact objects
- environment: An EnvironmentConfiguration object
- distributionPackage: The content of the distribution package XML (that is described by this schema)
- escapeTool: A simply utility class that can be used to do escapes
- distUtil: A class that contains util functions that help creating a distribution package.
Path of the parseable file.
The encoding of the parseable file.
The command that starts the framework. The framework should be started in the way that it will be stopped by sending a SIGTERM signal.
The type of the operating system.
The path of the working directory where the command should be executed.
Symbolic name of the bundle
Version of the bundle
The file URI that can be used to update/install the bundle. It might start with "reference:file:" or "file:".
An action that should be done with the bundle
Start level of the bundle (optional)