[jira] [Commented] (HIVE-3714) Patch: Hive's ivy internal resolvers need to use sourceforge for sqlline

2013-01-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547897#comment-13547897
 ] 

Hudson commented on HIVE-3714:
--

Integrated in Hive-trunk-hadoop2 #54 (See 
[https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
HIVE-3714 : Patch: Hive's ivy internal resolvers need to use sourceforge 
for sqlline (Gopal V via Ashutosh Chauhan) (Revision 1419118)

 Result = ABORTED
hashutosh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1419118
Files : 
* /hive/trunk/ivy/ivysettings.xml


 Patch: Hive's ivy internal resolvers need to use sourceforge for sqlline
 

 Key: HIVE-3714
 URL: https://issues.apache.org/jira/browse/HIVE-3714
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.10.0
 Environment: Ubuntu 12.10 (x86_64)
Reporter: Gopal V
Assignee: Gopal V
Priority: Trivial
 Fix For: 0.11.0

 Attachments: hive-ivy.patch


 While building hive with an internal resolver, ivy fails to resolve sqlline, 
 which needs to be picked up from
 http://sourceforge.net/projects/sqlline/files/sqlline/1.0.2/sqlline-1_0_2.jar/download
 ant package -Dresolvers=internal
 fails with
 {code}
 [ivy:resolve]  datanucleus-repo: tried
 [ivy:resolve]   -- artifact sqlline#sqlline#1.0.2;1_0_2!sqlline.jar:
 [ivy:resolve]   
 http://www.datanucleus.org/downloads/maven2/sqlline/sqlline/1_0_2/sqlline-1_0_2.jar
 [ivy:resolve] ::
 [ivy:resolve] ::  UNRESOLVED DEPENDENCIES ::
 [ivy:resolve] ::
 [ivy:resolve] :: sqlline#sqlline#1.0.2;1_0_2: not found
 [ivy:resolve] ::
 {code}
 The attached patch adds sourceforge to the internal resolver list so that if 
 the default sqlline version ( a hadoop snapshot) is used, the build does not 
 fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3714) Patch: Hive's ivy internal resolvers need to use sourceforge for sqlline

2012-12-10 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527889#comment-13527889
 ] 

Hudson commented on HIVE-3714:
--

Integrated in Hive-trunk-h0.21 #1847 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1847/])
HIVE-3714 : Patch: Hive's ivy internal resolvers need to use sourceforge 
for sqlline (Gopal V via Ashutosh Chauhan) (Revision 1419118)

 Result = FAILURE
hashutosh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1419118
Files : 
* /hive/trunk/ivy/ivysettings.xml


 Patch: Hive's ivy internal resolvers need to use sourceforge for sqlline
 

 Key: HIVE-3714
 URL: https://issues.apache.org/jira/browse/HIVE-3714
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.10.0
 Environment: Ubuntu 12.10 (x86_64)
Reporter: Gopal V
Assignee: Gopal V
Priority: Trivial
 Fix For: 0.11

 Attachments: hive-ivy.patch


 While building hive with an internal resolver, ivy fails to resolve sqlline, 
 which needs to be picked up from
 http://sourceforge.net/projects/sqlline/files/sqlline/1.0.2/sqlline-1_0_2.jar/download
 ant package -Dresolvers=internal
 fails with
 {code}
 [ivy:resolve]  datanucleus-repo: tried
 [ivy:resolve]   -- artifact sqlline#sqlline#1.0.2;1_0_2!sqlline.jar:
 [ivy:resolve]   
 http://www.datanucleus.org/downloads/maven2/sqlline/sqlline/1_0_2/sqlline-1_0_2.jar
 [ivy:resolve] ::
 [ivy:resolve] ::  UNRESOLVED DEPENDENCIES ::
 [ivy:resolve] ::
 [ivy:resolve] :: sqlline#sqlline#1.0.2;1_0_2: not found
 [ivy:resolve] ::
 {code}
 The attached patch adds sourceforge to the internal resolver list so that if 
 the default sqlline version ( a hadoop snapshot) is used, the build does not 
 fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira