Alvex meta repository
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
assembly-descriptors
img
master-poms
repo
scripts
share
.gitignore
.travis.yml
README.md Update README.md Jan 23, 2018
pom.xml

README.md

Component build status (latest version):

Component Component State Build Status
Utils Ready to use Build Status
Orgchart Ready to use Build Status
Manager dashboard tasks Ready to use Build Status
Uploader Ready to use Build Status
Inform policy Ready to use Build Status
Workflow permissions Ready to use Build Status
Infavorites document association Ready to use Build Status
Datagrid Unstable Build Status
Masterdata Unstable Build Status
Middle name Ready to use Build Status
Business calendar Ready to use Build Status
Aikau Components Ready to use Build Status
Registers In development Build Status
Project management (deprecated) Deprecated Build Status
Custom workflows (deprecated) Deprecated Build Status
Meta Build Status

Alvex

This repository contains all Alvex components as dependencies. This repository is supposed to be used to package pre-built jars into a single zip file that contains only required components.

Build

There are several ways to build Alvex.

Note: this project requires Maven 3.3.9 at least.

RECOMMENDED WAY: Include Alvex to your project via maven configuration

To include Alvex to your Alfresco Maven SDK project, add the following configuration to the repo-side pom.xml:

<dependencies>
  <dependency>
    <groupId>com.alvexcore.repo</groupId>
    <artifactId>utils</artifactId> // use here artifactId of the component you want to use
    <version>1.19-SNAPSHOT</version> // chech the current version of the component
    <classifier>installable</classifier>
  </dependency>
  ... // other dependencies
</dependencies>

<repositories>
    <repository>
        <id>alvex-public</id>
        <url>http://nexus.itdhq.com/content/repositories/snapshots/</url>
    </repository>
</repositories>

For share-side pom.xml use similar configuration:

<dependencies>
  <dependency>
    <groupId>com.alvexcore.share</groupId>
    <artifactId>utils</artifactId> // use here artifactId of the component you want to use
    <version>1.19-SNAPSHOT</version> // chech the current version of the component
    <classifier>installable</classifier>
  </dependency>
  ... // other dependencies
</dependencies>

<repositories>
    <repository>
        <id>alvex-public</id>
        <url>http://nexus.itdhq.com/content/repositories/snapshots/</url>
    </repository>
</repositories>

Build component from source

Although in most cases there is no need to build a single component from source, one may use the following steps to do it:

  1. Clone desired component repository (e.g. orgchart) and checkout specific release tag (or just HEAD to build latest version).
  2. Run mvn clean install or mvn -P make-jar clean install to build amp or jar respectively and install it to local repository. Note, that almost every component has repo and share extension, thus previous command has to be run two times in different folders. Also not that JAR produced by make-jar profile does not contain all component dependencies (if any) thus usage of such single JAR most probably will break an Alfresco installation.

Since Alvex components use Alfresco Maven SDK 2.x it's possible to use all facilities provided by SDK (e.g. -P amp-to-war integration-test).

Package pre-built jars

The simplest and recomended way to build Alvex is to package pre-built jars from Nexus into single zip archive. One can do it using the following steps:

  1. Clone this repository and checkout specific release tag (or just HEAD to build latest version).
  2. Produce single zip file using command mvn -P <COMPONENTS> clean package, where <COMPONENTS> is a comma-separated list of Alvex components to include into archive. At the moment following components are available:

Final zip archive contains two folders repo and share with jars that should to be copied to $ALF_DIR/modules/platform and $ALF_DIR/modules/share folders respectively.