[ https://issues.apache.org/jira/browse/CONNECTORS-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229554#comment-14229554 ]
Maurizio Pillitu edited comment on CONNECTORS-1105 at 12/1/14 8:55 AM: ----------------------------------------------------------------------- First feedback: 1. Instead of targeting Maven Central, I'd follow Apache guidelines and deploy into https://repository.apache.org/index.html ; the repo is public and easily accessible; as soon as we have a proper deployment/release process, we can decide to sync with Maven Central (just a matter of overriding some configurations) 2. org.apache.apache (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20AND%20a%3A%22apache%22) Maven Parent POM already provides all configurations needed to run a Maven deployment/release On rev. 1642650 I've updated org.apache.apache version to 16. To run a deployment you can simply run {noformat}mvn deploy -Papache-release{noformat} Currently it fails with the following error {noformat} Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.084714-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.084714-1.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] {noformat} I will investigate on how to get write access to repository.apache.org was (Author: maoo): First feedback: 1. Instead of targeting Maven Central, I'd follow Apache guidelines and deploy into https://repository.apache.org/index.html ; the repo is public and easily accessible; as soon as we have a proper deployment/release process, we can decide to sync with Maven Central (just a matter of overriding some configurations) 2. org.apache.apache (http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache%22%20AND%20a%3A%22apache%22) Maven Parent POM already provides all configurations needed to run a Maven deployment/release On rev. 1642650 I've updated org.apache.apache version to 16. To run a deployment you can simply run [noformat]mvn deploy -Papache-release[noformat] Currently it fails with the following error [noformat] Could not transfer artifact org.apache.manifoldcf:mcf-parent:pom:2.0-20141201.084714-1 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/manifoldcf/mcf-parent/2.0-SNAPSHOT/mcf-parent-2.0-20141201.084714-1.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] [noformat] I will investigate on how to get write access to repository.apache.org > Add maven delivery targets to poms > ---------------------------------- > > Key: CONNECTORS-1105 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1105 > Project: ManifoldCF > Issue Type: Improvement > Components: Build > Affects Versions: ManifoldCF 1.8 > Reporter: Karl Wright > Assignee: Maurizio Pillitu > Fix For: ManifoldCF 2.0 > > > We've been asked to deliver mcf jars and wars to maven central repository by > some developers. This ticket represents that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)