3c55c1a9a0
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* ACS-3402 Camel upgrade
* Revert "ACS-3402 Camel upgrade"
This reverts commit 124e188027.
* Moving all netty dependencies up to community-repo
These dependencies are a re/declaration of transitive/optional camel dependencies used in dependant projects.
They must be in sync with camel version of community repo, hence declaring them in other projects just causes unnecessary confusion.
* Fixing new versions of netty
They were updated through transitive update of camel from .73.Final to .79.Final, along with netty-transport-native-unix-common library that went to .79.Final
* Had extreme collisions on netty-transport-native-unix-common
Moved to approach with just declaring additional non-provided netty libraries and moving version numbers to community-repo.
Even mentioning netty-transport-native-unix-common in pom.xml seems to crash tests no matter which version is taken or if it's a transitive dependency of netty-handler. Since I can't add it either way, then partial additions of libraries make no sense. I've adjusted comments next to version numbers to make it easier to differentiate what they are responsible for and need to keep track of. Version numbers should still be placed in community-repo
* 3.18.2 was released recently, doesn't modify netty versions, so I'll use the latest one
Co-authored-by: pzurek <Piotr.Zurek@hyland.com>
alfresco-community-repo
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:
- REST API framework
- WebScript implementations including V1 REST APIs
- OpenCMIS implementations
Artifacts
The artifacts can be obtained by:
- downloading from Alfresco maven repository
- as Maven dependency by adding the dependency to your pom file:
<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.