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

Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/10/14 02:47:05 UTC

[jira] [Updated] (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:all-tabpanel ]

Colin Patrick McCabe updated HTRACE-252:
----------------------------------------
    Affects Version/s: 4.0
     Target Version/s: 4.0.1
             Priority: Minor  (was: Major)
        Fix Version/s:     (was: 4.1)
                       4.0.1
          Component/s: build

> 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
>          Components: build
>    Affects Versions: 4.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>             Fix For: 4.0.1
>
>         Attachments: 252.patch
>
>
> 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)