Hi Vladimir, I am aware of https://issues.apache.org/jira/browse/MANTTASKS-206 <https://issues.apache.org/jira/browse/MANTTASKS-206>, but this is not the problem we are having.
Our problem only happens in the downloadAndConfigureMaven branch, where any other setting is ignored and the default hardcoded central repo HTTP url is injected. This default repo does not come from AbstractArtifactWithRepositoryTask#getDefaultRemoteRepository (even though it should be changed there also, to https), but it comes from the very maven project definition that is in org.apache.maven:maven-project:2.2.1 (which also keeps using http). If that would change to HTTPS, it would be used. I forked the repo, created a feature branch and submitted a PR to the main repo. Hope it is useful. Cristi C. > On 16 Jan 2020, at 23:53, Vladimir Sitnikov <[email protected]> > wrote: > > Cristi>Is there any place to contribute the change? > > Here: > https://github.com/apache/maven-ant-tasks/blob/ed4d9a3bd1a41613791f2466f19c225898d45519/src/main/java/org/apache/maven/artifact/ant/AbstractArtifactWithRepositoryTask.java#L55 > > PS. https://issues.apache.org/jira/browse/MANTTASKS-206 seems to specify > the way to override the URL. > > Vladimir
