Productized v1.2.5 (#55)

* Update version number * Updated ReadMe.md
gfoidl · Jun 13, 2019 · b6e3cc5 · b6e3cc5
1 parent 5f763ab
commit b6e3cc5
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 5 deletions.
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -3,8 +3,8 @@
     <PropertyGroup>
         <VersionMajor Condition="'$(VersionMajor)' == ''">1</VersionMajor>
         <VersionMinor Condition="'$(VersionMinor)' == ''">2</VersionMinor>
-        <VersionPatch Condition="'$(VersionPatch)' == ''">4</VersionPatch>
-        <BuildNumber Condition="'$(BuildNumber)' == ''">77</BuildNumber>
+        <VersionPatch Condition="'$(VersionPatch)' == ''">5</VersionPatch>
+        <BuildNumber Condition="'$(BuildNumber)' == ''">82</BuildNumber>
         <VersionSuffix Condition="'$(Configuration)' == 'Debug' and '$(VersionSuffix)' == ''">dev</VersionSuffix>
         <Authors>gfoidl</Authors>
         <Company>Foidl Günther</Company>

diff --git a/ReadMe.md b/ReadMe.md
@@ -5,13 +5,12 @@
 # trx2junit (.NET Core global tool)
 
 Helper for converting trx-Testresults (`dotnet test --logger "trx"`) to a JUnit-based XML file.  
-The JUnit-output will be in the same directory than the trx-file.
 
 Can be used for CI-scenarios, like [CircleCi](https://circleci.com/) or [GitLab](https://docs.gitlab.com/ee/ci/junit_test_reports.html), where as test results JUnit is expected.
 
 ## Usage
 
-When installed as [.NET Core 2.1 Global Tools](https://natemcmaster.com/blog/2018/05/12/dotnet-global-tools/):  
+When installed as [.NET Core Global Tool](https://natemcmaster.com/blog/2018/05/12/dotnet-global-tools/):   
 `trx2junit {trxFile}` where _trxFile_ is the path to the trx-file.
 
 You can pass more than one trx file, each will create it's own junit xml file.
@@ -30,6 +29,7 @@ Converting 1 trx file(s) to JUnit-xml...
 Converting 'example.trx' to 'example.xml'
 done in 0.1234567 seconds. bye.
 ```
+If the shell won't handle wildcard expansion, `trx2junit` handles the expansion of files in the same directory.
 
 A different location for the JUnit-output can be specified:
 
@@ -51,7 +51,12 @@ For CI-scenarios execute before usage:
 ```sh
 export PATH="$PATH:/root/.dotnet/tools"
 ```
+Check also the documentation of your CI-system on how to persist the `PATH` between steps, etc.
+E.g. in CircleCI you need to run
+```sh
+echo 'export PATH="$PATH:/root/.dotnet/tools"' >> "$BASH_ENV"
+```
 
 ### Prequisites
 
-[.NET Core 2.1 SDK](https://aka.ms/DotNetCore21)
+[.NET Core SDK](https://dotnet.microsoft.com/download) 2.1 onwards.