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

Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/06/16 19:47:05 UTC

[jira] [Closed] (TINKERPOP-1260) Log for validate-distribution.sh

     [ https://issues.apache.org/jira/browse/TINKERPOP-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kuppitz closed TINKERPOP-1260.
-------------------------------------
       Resolution: Done
    Fix Version/s: 3.2.1

CTR'ed in https://github.com/apache/tinkerpop/commit/6edca75100f152b62a79cd1df8fbe20328d9f911 and https://github.com/apache/tinkerpop/commit/ce0dc48b5f46ce0fa7f106d4619070a339bb9964.

> Log for validate-distribution.sh
> --------------------------------
>
>                 Key: TINKERPOP-1260
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1260
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release
>    Affects Versions: 3.1.2-incubating
>            Reporter: stephen mallette
>            Assignee: Daniel Kuppitz
>            Priority: Minor
>             Fix For: 3.1.3, 3.2.1
>
>
> By the time we run `bin/validate-distribution.sh` there really shouldn't be errors, but errors seem to somehow happen anyway. Instead of writing the output to `/dev/null` it seems like it would be better to write to `/target/validate-distribution/mvn-clean-install.log` or something like that. 
> Perhaps on failure, it could just write the contents of that log back to the console so that you could just see the all the output without having to go find the file.



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