|
2 | 2 | JasperStarter - Running JasperReports from command line
|
3 | 3 | ========================================================
|
4 | 4 |
|
| 5 | +Release notes - JasperStarter - Version 3.5.0 |
| 6 | +--------------------------------------------- |
| 7 | + |
| 8 | +** Bug |
| 9 | + * [JAS-134] - "InterruptedException" should not be ignored in App.java |
| 10 | + * [JAS-135] - comparisons between unrelated types in Config.java |
| 11 | + |
| 12 | +** New Feature |
| 13 | + * [JAS-131] - Jasperstarter does not provide a way to use the query string saved in the report itself |
| 14 | + |
| 15 | +** Task |
| 16 | + * [JAS-133] - Release Pipeline takes longer than before |
| 17 | + * [JAS-136] - Throwable.printStackTrace(...) should not be called in Report.java setLookAndFeel() |
| 18 | + * [JAS-137] - Do not use a bitwise operator with a Boolean-like operand in ParameterPanel.java |
| 19 | + * [JAS-138] - Do not use a bitwise operator with a Boolean-like operand in ParameterPrompt.java |
| 20 | + |
| 21 | + |
| 22 | +Release notes - JasperStarter - Version 3.4.1 |
| 23 | +--------------------------------------------- |
| 24 | + |
| 25 | +** Bug |
| 26 | + * [JAS-132] - Security alert on org.springframework:spring-core |
| 27 | + Updated springframework to 4.3.21 |
| 28 | + |
| 29 | + CVE-2016-5007 - moderate severity - Vulnerable versions: < 4.3.1 |
| 30 | + CVE-2018-1275 - high severity - Vulnerable versions: < 4.3.16 |
| 31 | + CVE-2018-1272 - moderate severity - Vulnerable versions: < 4.3.15 |
| 32 | + CVE-2018-1271 - moderate severity - Vulnerable versions: < 4.3.15 |
| 33 | + CVE-2018-1270 - high severity - Vulnerable versions: < 4.3.16 |
| 34 | + CVE-2018-1257 - moderate severity - Vulnerable versions: < 4.3.17 |
| 35 | + |
| 36 | + |
| 37 | +Release notes - JasperStarter - Version 3.4.0 |
| 38 | +--------------------------------------------- |
| 39 | + |
| 40 | + JasperStarter-3.2.0 silently dropped Java7 support by using the |
| 41 | + latest available JasperReports Library. |
| 42 | + JasperReports-6.4.0 is the last release which works with Java7 so |
| 43 | + JasperStarter-3.1.0 was the latest release supporting Java7. |
| 44 | + |
| 45 | + Now JasperStarter needs Java8 at a minimum and is manually tested |
| 46 | + with OpenJDK-8, OpenJDK-10, OpenJDK-11. Automatic testing is on the |
| 47 | + way (see JAS-128). |
| 48 | + There will be a special release supporting Java7. |
| 49 | + |
| 50 | + "Diskless" operation using stdin and stdout for input data and |
| 51 | + output is now complete. See ([JAS-97] and [JAS-89]). |
| 52 | + |
| 53 | + A public API allows direct integration with Python using jpy |
| 54 | + ([JAS-125]). |
| 55 | + |
| 56 | +Known bugs: |
| 57 | + * [JAS-120] - JasperReports-6.7.0 Version does not match with |
| 58 | + reported version from the jar file in |
| 59 | + This is an upstream error which causes JasperStarter to put out |
| 60 | + a wrong JasperReports version number of 6.6.0 instead of 6.7.0 |
| 61 | + if you call: jasperstarter -V |
| 62 | + |
| 63 | +** Bug |
| 64 | + * [JAS-111] - JRE 1.7 incompatibility - not fixed in the main |
| 65 | + release but clarified. |
| 66 | + * [JAS-122] - Runtime error if a chart with "chart customizers" is |
| 67 | + used |
| 68 | + * [JAS-126] - Jasperstarter does not usefully propagate |
| 69 | + compilation errors |
| 70 | + |
| 71 | +** New Feature |
| 72 | + * [JAS-97] - Use stdout for the resulting PDF (so we don't have to |
| 73 | + write to the hosting server's storage) |
| 74 | + * [JAS-125] - Make report fill accessible via API |
| 75 | + |
| 76 | +** Task |
| 77 | + * [JAS-127] - Enable dependency caching in build pipeline |
| 78 | + * [JAS-129] - Remove test dependency to font Arial |
| 79 | + * [JAS-130] - launch4j-maven-plugin:1.5.2 depends on 32bit |
| 80 | + libraries |
| 81 | + |
| 82 | + |
| 83 | +Release notes - JasperStarter - Version 3.3.0 |
| 84 | +--------------------------------------------- |
| 85 | + |
| 86 | +Known bugs: |
| 87 | + * [JAS-120] - JasperReports-6.7.0 Version does not match with reported version from the jar file in |
| 88 | + This is an upstream error which causes JasperStarter to put out |
| 89 | + a wrong JasperReports version number of 6.6.0 instead of 6.7.0 |
| 90 | + if you call: jasperstarter -V |
| 91 | + |
| 92 | +** Bug |
| 93 | + * [JAS-116] - SSL error |
| 94 | + * [JAS-121] - Container 'Build' exceeded memory limit. |
| 95 | + * [JAS-122] - Runtime error if a chart with "chart customizers" is used |
| 96 | + |
| 97 | +** New Feature |
| 98 | + * [JAS-113] - JSONQL data source support |
| 99 | + |
| 100 | +** Task |
| 101 | + * [JAS-102] - Pipeline: enable build artifact upload to download section |
| 102 | + * [JAS-119] - Include JasperReports-6.7.0 |
| 103 | + |
| 104 | +** Improvement |
| 105 | + * [JAS-89] - Accept stdin for datafile input |
| 106 | + |
| 107 | + |
5 | 108 | Release Notes - JasperStarter - Version 3.2.1
|
6 | 109 | ---------------------------------------------
|
7 | 110 |
|
|
0 commit comments