-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.4 Enterprise, 4.0 Enterprise
-
Fix Version/s: 4.2 Enterprise
-
Component/s: artifacts.alfresco.com
-
Security Level: external (External user)
-
Labels:None
-
Environment:artifacts.alfresco.com
Maven artifacts normally come with proper dependency declarations in POM files.
At the moment we only publish Alfresco binary artifacts only with generated empty POMs (https://wiki.alfresco.com/wiki/Alfresco_Artifacts_Repository#A_note_on_3rd_party_dependencies).
Having at least declared in POMs:
- license
- dependencies
for each delivered JAR/WAR would allow a number of automated process like:
- Extensions unit testing
- Legal overlook for Alfresco deployments in controlled Enterprise environments
- Full blown SDKs based on the Maven repository layout (e.g. Maven, Gradle, Ivy)
- Making Alfresco available on Maven Central (http://repo1.maven.org)
This mainly comprise of few sub-tasks:
1. Identify GA dependencies specific to each alfresco module
2. Identify Alfresco patched dependencies specific to each alfresco module
3. Make deps at #2 available (with sources) on artifacts.alfresco.com
4. Declare transitive dependencies (for JARs and WARs) in POM files (and maintain them across releases)
5. Add POM deployment to the procedure of ALF-11027
An intermediate attempt (simplified) could be:
1. Define a plaftform-pom which represents the full SDK
2. Add in this platform POM the alfresco-* dependencies and all the well known transitive dependencies in a flattened fashion
3. Deploy this per release
- is cloned by
-
MNT-7581 CLONE - Alfresco Enterprise artifacts in artifacts.alfresco.com do not provide POM files / dependencies declarations
- Closed