-
Bug
-
Resolution: Fixed
-
Major
-
1.1.4
-
None
-
-
Empty show more show less
-
6.2 Ramp-up 20
PUBLISHING-69 updated the compatibility baseline from Magnolia 5.7.3 / BOM 5.7.2 which were publicly available, to Magnolia 5.7.6 / BOM 5.7.5, which were released after the 5.7 branch entered maintenance mode (thus artifacts are only in maintenance repos on Nexus, only available for enterprise customers).
A Magnolia Community project on 6.1.4, 6.1.5 or 6.2-SNAPSHOT doesn't depend on those artifacts per se, but they are part of the dependency tree, and maven needs to resolve their dependencyManagement imports in order to construct the whole tree.
[INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:30 min [INFO] Finished at: 2020-03-25T18:34:41+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project archetest-webapp: Could not resolve dependencies for project me.mkgl.archetest:archetest-webapp:war:1.0-SNAPSHOT: Failed to collect dependencies at info.magnolia.bundle:magnolia-community-webapp:pom:6.2-SNAPSHOT -> info.magnolia:magnolia-empty-webapp:pom:6.2-SNAPSHOT -> info.magnolia.publishing:magnolia-publishing-core:jar:1.1.4: Failed to read artifact descriptor for info.magnolia.publishing:magnolia-publishing-core:jar:1.1.4: Could not find artifact info.magnolia.boms:magnolia-external-dependencies:pom:5.7.5 in magnolia.nexus.public (https://nexus.magnolia-cms.com/content/groups/public/) -> [Help 1]
- caused by
-
PUBLISHING-69 Publishing large objects consumes lots of resources when using Java 11
- Closed
- relates to
-
PUBLISHING-59 Publishing 1.0 branch depends on a maintenance core release
- Closed