Files
alfresco-community-repo/README.md
Eva Vasques e02722af37 Migrate to GHA and Update License Headers (#2603)
* ACS-4653 Migrate to GHA on release/7.2.1 (#1758)

* Remove travis configuration files
* Added property dependency.alfresco-transform-core.version
* Added github action configuration for 7.2.1
* Add missing scripts and adjust start-compose.sh
* Give execution permissions to scripts

* ACS-3841 Add missing logs for WebDAV TAS tests (#1629)
* ACS-3841 Add missing logs
* ACS-3841 Reformat code + fix grep

(cherry picked from commit cdbe3292e0)

* Move ags ci getLogs script. Update badge on readme

(cherry picked from commit 309f6baae3)

* ACS-4653 GHA - Fix mySQL tests (#1765)

* Added missing mysql params for older version. Test [db]

(cherry picked from commit 7a504a0292)

* Fix readme - status for 7.2.N

* Update license headers

* ACS-4776 Finalize deprecation of BitlyUrlShortenerImpl (#1787)

(cherry picked from commit 906a812ea5)

---------

Co-authored-by: Domenico Sibilio <domenicosibilio@gmail.com>
2024-04-22 13:48:59 +01:00

3.6 KiB

alfresco-community-repo

Build Status

Alfresco Core

Alfresco Core is a library packaged as a jar file which contains the following:

  • Various helpers and utils
  • Canned queries interface and supporting classes
  • Generic encryption supporting classes

Alfresco Data Model

Data model is a library packaged as a jar file which contains the following:

  • Dictionary, Repository and Search Services interfaces
  • Models for data types and Dictionary implementation
  • Parsers

Alfresco Repository

Repository is a library packaged as a jar file which contains the following:

  • DAOs and SQL scripts
  • Various Service implementations
  • Utility classes

Alfresco Remote API

Remote API is a library packaged as a jar file which contains the following:

Artifacts

The artifacts can be obtained by:

<dependency>
  <groupId>org.alfresco</groupId>
  <artifactId>alfresco-core</artifactId>
  <version>version</version>
</dependency>

<dependency>
  <groupId>org.alfresco</groupId>
  <artifactId>alfresco-data-model</artifactId>
  <version>version</version>
</dependency>

<dependency>
  <groupId>org.alfresco</groupId>
  <artifactId>alfresco-repository</artifactId>
  <version>version</version>
</dependency>

<dependency>
  <groupId>org.alfresco</groupId>
  <artifactId>alfresco-remote-api</artifactId>
  <version>version</version>
</dependency>

<dependency>
    <groupId>org.alfresco</groupId>
    <artifactId>content-services-community</artifactId>
    <version>version</version>
    <type>war</type>
</dependency>

and Alfresco maven repository:

<repository>
  <id>alfresco-maven-repo</id>
  <url>https://artifacts.alfresco.com/nexus/content/groups/public</url>
</repository>

The SNAPSHOT versions of the artifact are not published.

Setting up and building your development environment

See the Development Tomcat Environment page which will show you how to try out your repository changes in a local tomcat instance. If you wish to use Docker images, take a look at the aliases ending in D and the docker-compose files in this project's test modules.

Branches

This project has a branch for each ACS release. For example the code in ACS 6.2.1 is a branch called releases/6.2.2. In addition to the original 6.2.2 release it will also contain Hot Fixes added later. The latest unreleased code is on the master branch. There are also .N branches, such as releases/7.1.N on which we gather unreleased fixes for future service pack releases. They do not indicate that one is planned.

For historic reasons the version of artifacts created on each branch do not match the ACS version. For example artifact in ACS 7.2.0 will be 14.<something>.

The enterprise projects which extend the alfresco-community-repo use the same branch names and leading artifact version number.

Contributing guide

Please use this guide to make a contribution to the project.