From a8577c5cd3021b66ca0f0ba955f3fc73da4c4d6c Mon Sep 17 00:00:00 2001
From: Mario <mario@die-davids.de>
Date: Tue, 19 Dec 2017 20:20:58 +0100
Subject: [PATCH] released version 0.4.1

---
 CHANGELOG.md | 5 +++++
 README.md    | 2 ++
 build.gradle | 2 +-
 3 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a646532..6bd378d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+## [0.4.1] - 2017-12-19
+
+### Added
+- possibility to convert JPQL to SQL in the JPQL console
+
 ## [0.4.0] - 2017-11-29
 
 ### Added
diff --git a/README.md b/README.md
index 22597f0..3493800 100644
--- a/README.md
+++ b/README.md
@@ -117,6 +117,8 @@ Results of a JPQL / SQL statement are displayed in a table in the result tab. Th
 
 The JPQL / SQL console supports comments in the form of `-- single line comment` and `/* multi line comments */`.
 
+In the JPQL console you additionally have the possibility to convert your written JPQL into an equivivalent SQL query. 
+This can be handy sometimes when working with the default mechanism of CUBA to load in data via SQL files e.g. 
 
 ### Security of the SQL-Console
 By default, only SELECT stements are allowed to execute through the SQL-Console. 
diff --git a/build.gradle b/build.gradle
index fd0e8b4..7472904 100644
--- a/build.gradle
+++ b/build.gradle
@@ -40,7 +40,7 @@ def bintrayRepositoryUrl = "https://api.bintray.com/maven/mariodavid/cuba-compon
 cuba {
     artifact {
         group = 'de.diedavids.cuba.runtimediagnose'
-        version = '0.4.0'
+        version = '0.4.1'
         isSnapshot = false
     }
     tomcat {