You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@htrace.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/09/17 00:06:45 UTC

[jira] [Commented] (HTRACE-252) Up our apache pom to latest -- was v12, latest is v17

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

Hudson commented on HTRACE-252:
-------------------------------

FAILURE: Integrated in HTrace-Master #106 (See [https://builds.apache.org/job/HTrace-Master/106/])
HTRACE-252 Up our apache pom to latest -- was v12, latest is v17 (stack: rev 6d569bed2d9aee52198b9cba3f06a7ab8fb84915)
* pom.xml


> Up our apache pom to latest -- was v12, latest is v17
> -----------------------------------------------------
>
>                 Key: HTRACE-252
>                 URL: https://issues.apache.org/jira/browse/HTRACE-252
>             Project: HTrace
>          Issue Type: Improvement
>            Reporter: stack
>
> Trying this to see if it will get me over the perms problem building inside docker container:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.4:process (default) on project htrace: Error finding remote resources manifests: /home/jenkins/jenkins-slave/workspace/HTrace-Master/target/maven-shared-archive-resources/META-INF/NOTICE (Permission denied) -> [Help 1]
> We are puling these dependencies from our parent pom. The new parent pom uses a later version of maven-remote-resources-plugin, v1.5. Lets see if it is smarter about perms... else will have to try and override the perms it sets on the downloaded resources.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)