You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@omid.apache.org by "Igor Katkov (JIRA)" <ji...@apache.org> on 2016/05/20 22:24:13 UTC
[jira] [Comment Edited] (OMID-32) Publish omid jars to Apache maven
repository
[ https://issues.apache.org/jira/browse/OMID-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294388#comment-15294388 ]
Igor Katkov edited comment on OMID-32 at 5/20/16 10:23 PM:
-----------------------------------------------------------
Created https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11955
--------------
Project name: Omid (incubation)
The parent pom references correct apache parent pom
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>18</version>
</parent>
We prepared release (no -SNAPSHOT) and trying to deploy according to http://www.apache.org/dev/publishing-maven-artifacts.html
Settings test passes
mvn clean install -Papache-release
When we try to publish jars into apache maven with
mvn deploy -DrepositoryId=apache.staging.https -Prelease_profile,hbase-0
we get 400 bad request.
No idea what might be the reason.
Then I tried to manually upload to repository.apache.org via web UI and the following error showed up
"Artifact upload failed.
Cannot find a matching staging profile"
Do we need to have the staging profile created?
was (Author: ikatkov):
https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11955
> Publish omid jars to Apache maven repository
> --------------------------------------------
>
> Key: OMID-32
> URL: https://issues.apache.org/jira/browse/OMID-32
> Project: Apache Omid
> Issue Type: Improvement
> Reporter: Daniel Dai
> Assignee: Igor Katkov
> Fix For: 0.8.2.0
>
>
> It would be better to publish omid jars to Apache maven repository instead (or in addition to) bintray.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)