infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (INFRA-2828) Extend staging profile for Struts
Date Mon, 28 Jun 2010 19:20:10 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883251#action_12883251
] 

Brian Fox edited comment on INFRA-2828 at 6/28/10 3:19 PM:
-----------------------------------------------------------

There are a few issues at play here. First is that I don't think it's normal to have a release
come from Apache and go to another namespace, ie com.opensymphony. Second is that in order
for Nexus to generate proper metadata, I'd have to pull the old releases into the repo from
com.opensymphony.xwork. 3rd, the Central rsync recognizes com.opensymphony to come from rsync:maven2.opensymphony.com
not from rsync:repository.apache.org. Obviously moving all of opensymphony isn't the intent,
but this creates a bunch of extra confusion. Since this is the first release from Apache,
shouldn't this be the trigger to rename the groupId? 

I can help you craft a relocation pom for the artifacts so that Maven can recognize that com.opensymphony:xwork:2.2.0
is now org.apache.struts.xwork:2.2.0 if you wish.

      was (Author: brianf):
    There are a few issues at play here. First is that I don't think it's normal to have a
release come from Apache and go to another namespace, ie com.opensymphony. Second is that
in order for Nexus to generate proper metadata, I'd have to pull the old releases into the
repo from com.opensymphony.xwork. 3rd, the Central rsync recognizes com.opensymphony to come
from rsync:maven2.opensymphony.com not from rsync:repository.apache.org. Obviously moving
all of opensymphony isn't the intent, but this creates a bunch of extra confusion. Since this
is the first release from Apache, shouldn't this be the trigger to rename the groupId? 

I can help you craft a relocation pom for the artifacts so that Maven can recognize that com.opensymphony:xwork:2.2.0
is not org.apache.struts.xwork:2.2.0 if you wish.
  
> Extend staging profile for Struts
> ---------------------------------
>
>                 Key: INFRA-2828
>                 URL: https://issues.apache.org/jira/browse/INFRA-2828
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Lukasz Lenart
>            Assignee: Brian Fox
>            Priority: Blocker
>
> I'm trying to make a new Struts 2 release but I'm getting below exception during uploading:
> Got exception during processing request "PUT http://repository.apache.org/service/local/staging/deploy/maven2/com/opensymphony/xwork-core/2.2.0/xwork-core-2.2.0.jar":
Cannot find a matching staging profile!
> XWork has been moved to ASF some time ago and now it's a part of Apache Struts 2 but
it still has its own package layer (com.opensymphony.xwork). It will be moved to org.apache
soon.
> Could you solve that problem ASAP? It's blocking release process.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message