[jira] [Commented] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-13 Thread Guo Ruijing (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932962#comment-13932962
 ] 

Guo Ruijing commented on HBASE-10681:
-

JIRA is closed since Roman's solution is good

> Allow Hbase artifacts to deploy to remote repo other than apache
> 
>
> Key: HBASE-10681
> URL: https://issues.apache.org/jira/browse/HBASE-10681
> Project: HBase
>  Issue Type: Improvement
>  Components: build
>Reporter: Guo Ruijing
>
> pom.xml in hbase write as
>  
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
> We expect pom.xml in hbase like hadoop can be:
>  
>   
>   ${distMgmtStagingId}
>   ${distMgmtStagingName}
>   ${distMgmtStagingUrl}
> 
> 
>   ${distMgmtSnapshotsId}
>   ${distMgmtSnapshotsName}
>   ${distMgmtSnapshotsUrl}
> 
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
>   



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-12 Thread Roman Shaposhnik (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932192#comment-13932192
 ] 

Roman Shaposhnik commented on HBASE-10681:
--

[~rguo] here's what I'm thinking:
  # this is already implemented for snapshots in a parent Apache pom: just pass 
-DdistMgmtSnapshotsUrl=XXX to the build
  # you can always utilize 
-DaltDeploymentRepository/altReleaseDeploymentRepository/altSnapshotDeploymentRepository
 to redirect the deployment

The trouble that I see with your approach is that once you add the override for 
a non-snapshot repo to the HBase pom, I don't think there's any way to keep the 
one coming from the parent pom as the default.
  

> Allow Hbase artifacts to deploy to remote repo other than apache
> 
>
> Key: HBASE-10681
> URL: https://issues.apache.org/jira/browse/HBASE-10681
> Project: HBase
>  Issue Type: Improvement
>  Components: build
>Reporter: Guo Ruijing
>
> pom.xml in hbase write as
>  
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
> We expect pom.xml in hbase like hadoop can be:
>  
>   
>   ${distMgmtStagingId}
>   ${distMgmtStagingName}
>   ${distMgmtStagingUrl}
> 
> 
>   ${distMgmtSnapshotsId}
>   ${distMgmtSnapshotsName}
>   ${distMgmtSnapshotsUrl}
> 
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
>   



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-10681) Allow Hbase artifacts to deploy to remote repo other than apache

2014-03-05 Thread stack (JIRA) 

[ 
https://issues.apache.org/jira/browse/HBASE-10681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921594#comment-13921594
 ] 

stack commented on HBASE-10681:
---

[~rguo]  Sounds totally reasonable.  Mind making a patch for our top level pom 
and I'll apply it, np.

> Allow Hbase artifacts to deploy to remote repo other than apache
> 
>
> Key: HBASE-10681
> URL: https://issues.apache.org/jira/browse/HBASE-10681
> Project: HBase
>  Issue Type: Improvement
>  Components: build
>Reporter: Guo Ruijing
>
> pom.xml in hbase write as
>  
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
> We expect pom.xml in hbase like hadoop can be:
>  
>   
>   ${distMgmtStagingId}
>   ${distMgmtStagingName}
>   ${distMgmtStagingUrl}
> 
> 
>   ${distMgmtSnapshotsId}
>   ${distMgmtSnapshotsName}
>   ${distMgmtSnapshotsUrl}
> 
> 
>   hbase.apache.org
>   HBase Website at hbase.apache.org
>   
>   file:///tmp
> 
>   



--
This message was sent by Atlassian JIRA
(v6.2#6252)