Stefan Seifert created SLING-8833:
-------------------------------------
Summary: sling-bundle-parent: Disable
includeDistributionManagement for bnd-baseline-maven-plugin
Key: SLING-8833
URL: https://issues.apache.org/jira/browse/SLING-8833
Project: Sling
Issue Type: Improvement
Components: General
Affects Versions: Bundle Parent 35
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Fix For: Bundle Parent 36
the bnd-baseline-maven-plugin has a strange feature enabled by default: when
resolving the latest release versions it does not only check in the maven
repository configured in the maven environment (e.g. maven central), but tries
also to download them form the URLs configured as distribution management.
this is normally nothing you want to to - and in our case leads to warnings in
the build like
{noformat}
[INFO] --- bnd-baseline-maven-plugin:4.2.0:baseline (bnd-baseline) @
org.apache.sling.servlet-helpers ---
[INFO] Determining the baseline version for
org.apache.sling:org.apache.sling.servlet-helpers:jar:(,1.3.1-SNAPSHOT) using
repositories [apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2, default,
releases+snapshots), central (https://nexus.pvtool.org/content/groups/default,
default, releases+snapshots)]
Downloading from apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/sling/org.apache.sling.servlet-helpers/maven-metadata.xml
[WARNING] Could not transfer metadata
org.apache.sling:org.apache.sling.servlet-helpers/maven-metadata.xml from/to
apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2): Failed to
transfer file:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/sling/org.apache.sling.servlet-helpers/maven-metadata.xml.
Return code is: 400 , ReasonPhrase:Bad Request.
{noformat}
we should just disable this feature (luckily there is a switch for it).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
