You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Suresh Marru (Created) (JIRA)" <ji...@apache.org> on 2011/11/10 02:45:51 UTC
[jira] [Created] (INFRA-4109) Nexus access for Airavata - Incubator
adding to repository.apache.org
Nexus access for Airavata - Incubator adding to repository.apache.org
---------------------------------------------------------------------
Key: INFRA-4109
URL: https://issues.apache.org/jira/browse/INFRA-4109
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: LDAP, Nexus
Reporter: Suresh Marru
Assignee: Brian Demers
Priority: Blocker
I am running into similar issue as https://issues.apache.org/jira/browse/INFRA-3718, should I be added manually to repository since it is mentioned that incubator is not managed by LDAP? (my id is smarru). I am also waiting on https://issues.apache.org/jira/browse/INFRA-4093, that may be an issue as well. The following is the error I get:
Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project airavata: Failed to deploy artifacts: Could not transfer artifact org.apache.airavata:airavata:pom:0.1-incubating 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/airavata/airavata/0.1-incubating/airavata-0.1-incubating.pom. Return code is: 400
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4109) Nexus access for Airavata - Incubator
adding to repository.apache.org
Posted by "Brian Demers (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Demers closed INFRA-4109.
-------------------------------
Resolution: Duplicate
> Nexus access for Airavata - Incubator adding to repository.apache.org
> ---------------------------------------------------------------------
>
> Key: INFRA-4109
> URL: https://issues.apache.org/jira/browse/INFRA-4109
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: LDAP, Nexus
> Reporter: Suresh Marru
> Assignee: Brian Demers
> Priority: Blocker
>
> I am running into similar issue as https://issues.apache.org/jira/browse/INFRA-3718, should I be added manually to repository since it is mentioned that incubator is not managed by LDAP? (my id is smarru). I am also waiting on https://issues.apache.org/jira/browse/INFRA-4093, that may be an issue as well. The following is the error I get:
> Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project airavata: Failed to deploy artifacts: Could not transfer artifact org.apache.airavata:airavata:pom:0.1-incubating 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/airavata/airavata/0.1-incubating/airavata-0.1-incubating.pom. Return code is: 400
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira