You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Vladimir Sitnikov <si...@gmail.com> on 2020/04/02 09:32:02 UTC
Release 5.3
Hi,
It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
How about we release JMeter 5.3?
Vladimir
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
PR has been merged but version is not released yet.
See my answers inline below.
Regards
On Fri, Apr 3, 2020 at 10:57 AM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> >3) What about upgrade to groovy ? Do we skip it for this release ?
>
> Let's update to Groovy 3.
>
> >2) I upgraded some dependencies, but github is facing an incident so we
> >didn't get the mail
>
> Thanks.
>
> I suggest we stop adding lines like "Updated equalsverifier to 3.1.9 (from
> 3.1.12)" to changes.xml.
>
> The reasoning is as follows:
> 1) There are build-only dependencies, and there are runtime dependencies.
> For instance, JMeter binary artifacts do not include equalsverifier jar.
> What does "updated equalsverifier" tell the end-users?
>
I agree
> 2) It is hard to predict which transitive versions will be updated
>
> That is why I think we should update version diff just before the release.
>
It can help to do it before.
You might have a bug triggered with some updates of libs like HTTPClient,
Jodd, JSOUP...
>
> I'm not sure if we should add test-only dependencies update to changes.xml
> If we add them, the changes should probably go into a dedicated section
> (e.g. build/test changes).
>
I agree
>
> Vladimir
>
But we should clearly state all updates to non test libraries we do. As
client of other libraries I am very frustrated by limited release notes.
Regarding Auto Correlation feature, an alternative would be to manage 2
versions:
- 5.3 without it because it touches some core classes so it can impact
other features.
- 6.0-alpha or beta
HttpClient does this, I don't know if it's sucessful.
As a potential user, If I need auto correlation I would take the risk to
use alpha for example.
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 09.05.20 um 18:25 schrieb Milamber:
>
> I can do the release. When you prefer ?
I committed the fix for 64267, so I think we are ready to go. Feel free
to prepare a release candidate.
Thanks for your work
Felix
>
> On 5/8/20 7:41 PM, Philippe Mouawad wrote:
>> Hello,
>> I approved PR also.
>>
>> Any volunteer for Release ?
>>
>> Regards
>>
>> On Fri, May 8, 2020 at 5:25 PM Felix Schumacher <
>> felix.schumacher@internetallee.de> wrote:
>>
>>> Am 05.05.20 um 21:22 schrieb Philippe Mouawad:
>>>> Hello,
>>>> Good catch, yes it is required.
>>>>
>>>> Shall we release or do this before ?
>>> I have created a PR (that Vladimir has already looked into :)) that we
>>> could merge. I hesitated a bit, as one dependency (spock) is a
>>> milestone
>>> release. But Vladimir seems to be OK with it, as
>>>
>>> * Spock will most probably not change that much before a release
>>>
>>> * we use Spock at a level, that it is very unlikely, that a change
>>> would affect our code
>>>
>>> I agree with those statements.
>>>
>>> What do you (or anyone else) think?
>>>
>>> Felix
>>>
>>>> Thanks
>>>> Regards
>>>>
>>>> On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
>>>> felix.schumacher@internetallee.de> wrote:
>>>>
>>>>> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
>>>>>>> Let's update to Groovy 3.
>>>>>> I see that we currently use groovy-all dependency.
>>>>>> Unfortunately, it is unpredictable, as it adds new transitive
>>>>> dependencies
>>>>>> as Groovy evolves.
>>>>>>
>>>>>> I guess we need to specify which dependencies we include explicitly.
>>>>>> How about groovy,
>>>>>> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
>>>>>> groovy-sql
>>> ?
>>>>> What about groovy-jsr223?
>>>>>
>>>>> Felix
>>>>>
>>>>>> Here's dependency tree for groovy-all 2.4.18
>>>>>> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive
>>>>>> dependencies)
>>>>>>
>>>>>> groovy 3.0.2 (2.5.10 is pretty much the same)
>>>>>>
>>>>>> org.codehaus.groovy:groovy-all -> 3.0.2
>>>>>> +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-ant:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- org.apache.ant:ant:1.10.7
>>>>>> | | \--- org.apache.ant:ant-launcher:1.10.7
>>>>>> | +--- org.apache.ant:ant-junit:1.10.7
>>>>>> | | \--- org.apache.ant:ant:1.10.7 (*)
>>>>>> | +--- org.apache.ant:ant-launcher:1.10.7
>>>>>> | +--- org.apache.ant:ant-antlr:1.10.7
>>>>>> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- com.github.javaparser:javaparser-core:3.15.13
>>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2
>>>>>> | | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
>>>>>> | | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | \--- com.thoughtworks.qdox:qdox:1.12.1
>>>>>> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | \--- info.picocli:picocli:4.1.4
>>>>>> +--- org.codehaus.groovy:groovy-console:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>>> | \--- org.codehaus.groovy:groovy-swing:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-datetime:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
>>>>>> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
>>>>>> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
>>>>>> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>>> | \--- jline:jline:2.14.6
>>>>>> +--- org.codehaus.groovy:groovy-jmx:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-json:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-macro:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-nio:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-servlet:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>>> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>>> +--- org.codehaus.groovy:groovy-sql:3.0.2
>>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>>> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
>>>>>> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>>> +--- org.codehaus.groovy:groovy-test:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | \--- junit:junit:4.13
>>>>>> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
>>>>>> | \--- org.hamcrest:hamcrest:2.2
>>>>>> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | +--- org.junit.platform:junit-platform-launcher:1.6.0
>>>>>> | | +--- org.junit:junit-bom:5.6.0
>>>>>> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
>>>>>> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
>>>>>> | | | +---
>>>>>> org.junit.platform:junit-platform-engine:1.6.0 (c)
>>>>>> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0
>>> (c)
>>>>>> | | | \---
>>>>>> org.junit.platform:junit-platform-commons:1.6.0 (c)
>>>>>> | | \--- org.junit.platform:junit-platform-engine:1.6.0
>>>>>> | | +--- org.junit:junit-bom:5.6.0 (*)
>>>>>> | | +--- org.opentest4j:opentest4j:1.2.0
>>>>>> | | \--- org.junit.platform:junit-platform-commons:1.6.0
>>>>>> | | \--- org.junit:junit-bom:5.6.0 (*)
>>>>>> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
>>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>>> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
>>>>>> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
>>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>>> | +--- org.opentest4j:opentest4j:1.2.0
>>>>>> | \---
>>>>>> org.junit.platform:junit-platform-commons:1.6.0 (*)
>>>>>> +--- org.codehaus.groovy:groovy-testng:3.0.2
>>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>>> | \--- org.testng:testng:6.14.3
>>>>>> | \--- com.beust:jcommander:1.72
>>>>>> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>>>
>>>>>>
>>>>>> Vladimir
>>>>>>
>>
>
>
Re: Release 5.3
Posted by Milamber <mi...@apache.org>.
I can do the release. When you prefer ?
On 5/8/20 7:41 PM, Philippe Mouawad wrote:
> Hello,
> I approved PR also.
>
> Any volunteer for Release ?
>
> Regards
>
> On Fri, May 8, 2020 at 5:25 PM Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Am 05.05.20 um 21:22 schrieb Philippe Mouawad:
>>> Hello,
>>> Good catch, yes it is required.
>>>
>>> Shall we release or do this before ?
>> I have created a PR (that Vladimir has already looked into :)) that we
>> could merge. I hesitated a bit, as one dependency (spock) is a milestone
>> release. But Vladimir seems to be OK with it, as
>>
>> * Spock will most probably not change that much before a release
>>
>> * we use Spock at a level, that it is very unlikely, that a change
>> would affect our code
>>
>> I agree with those statements.
>>
>> What do you (or anyone else) think?
>>
>> Felix
>>
>>> Thanks
>>> Regards
>>>
>>> On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
>>> felix.schumacher@internetallee.de> wrote:
>>>
>>>> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
>>>>>> Let's update to Groovy 3.
>>>>> I see that we currently use groovy-all dependency.
>>>>> Unfortunately, it is unpredictable, as it adds new transitive
>>>> dependencies
>>>>> as Groovy evolves.
>>>>>
>>>>> I guess we need to specify which dependencies we include explicitly.
>>>>> How about groovy,
>>>>> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql
>> ?
>>>> What about groovy-jsr223?
>>>>
>>>> Felix
>>>>
>>>>> Here's dependency tree for groovy-all 2.4.18
>>>>> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
>>>>>
>>>>> groovy 3.0.2 (2.5.10 is pretty much the same)
>>>>>
>>>>> org.codehaus.groovy:groovy-all -> 3.0.2
>>>>> +--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-ant:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.apache.ant:ant:1.10.7
>>>>> | | \--- org.apache.ant:ant-launcher:1.10.7
>>>>> | +--- org.apache.ant:ant-junit:1.10.7
>>>>> | | \--- org.apache.ant:ant:1.10.7 (*)
>>>>> | +--- org.apache.ant:ant-launcher:1.10.7
>>>>> | +--- org.apache.ant:ant-antlr:1.10.7
>>>>> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- com.github.javaparser:javaparser-core:3.15.13
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2
>>>>> | | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
>>>>> | | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- com.thoughtworks.qdox:qdox:1.12.1
>>>>> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- info.picocli:picocli:4.1.4
>>>>> +--- org.codehaus.groovy:groovy-console:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | \--- org.codehaus.groovy:groovy-swing:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-datetime:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>> | \--- jline:jline:2.14.6
>>>>> +--- org.codehaus.groovy:groovy-jmx:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-json:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-macro:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-nio:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-servlet:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-sql:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-test:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- junit:junit:4.13
>>>>> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
>>>>> | \--- org.hamcrest:hamcrest:2.2
>>>>> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.junit.platform:junit-platform-launcher:1.6.0
>>>>> | | +--- org.junit:junit-bom:5.6.0
>>>>> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
>>>>> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
>>>>> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
>>>>> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0
>> (c)
>>>>> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
>>>>> | | \--- org.junit.platform:junit-platform-engine:1.6.0
>>>>> | | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | | +--- org.opentest4j:opentest4j:1.2.0
>>>>> | | \--- org.junit.platform:junit-platform-commons:1.6.0
>>>>> | | \--- org.junit:junit-bom:5.6.0 (*)
>>>>> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
>>>>> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | +--- org.opentest4j:opentest4j:1.2.0
>>>>> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
>>>>> +--- org.codehaus.groovy:groovy-testng:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- org.testng:testng:6.14.3
>>>>> | \--- com.beust:jcommander:1.72
>>>>> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>>
>>>>>
>>>>> Vladimir
>>>>>
>
Re: Release 5.3
Posted by Felix Schumacher <fe...@internetallee.de>.
I will commit the PR.
On the other hand, I think we should take a deeper look at bug 64267,
even if we didn't get any earlier bug report on this.
Felix
Am 08.05.20 um 21:41 schrieb Philippe Mouawad:
> Hello,
> I approved PR also.
>
> Any volunteer for Release ?
>
> Regards
>
> On Fri, May 8, 2020 at 5:25 PM Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Am 05.05.20 um 21:22 schrieb Philippe Mouawad:
>>> Hello,
>>> Good catch, yes it is required.
>>>
>>> Shall we release or do this before ?
>> I have created a PR (that Vladimir has already looked into :)) that we
>> could merge. I hesitated a bit, as one dependency (spock) is a milestone
>> release. But Vladimir seems to be OK with it, as
>>
>> * Spock will most probably not change that much before a release
>>
>> * we use Spock at a level, that it is very unlikely, that a change
>> would affect our code
>>
>> I agree with those statements.
>>
>> What do you (or anyone else) think?
>>
>> Felix
>>
>>> Thanks
>>> Regards
>>>
>>> On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
>>> felix.schumacher@internetallee.de> wrote:
>>>
>>>> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
>>>>>> Let's update to Groovy 3.
>>>>> I see that we currently use groovy-all dependency.
>>>>> Unfortunately, it is unpredictable, as it adds new transitive
>>>> dependencies
>>>>> as Groovy evolves.
>>>>>
>>>>> I guess we need to specify which dependencies we include explicitly.
>>>>> How about groovy,
>>>>> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql
>> ?
>>>> What about groovy-jsr223?
>>>>
>>>> Felix
>>>>
>>>>> Here's dependency tree for groovy-all 2.4.18
>>>>> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
>>>>>
>>>>> groovy 3.0.2 (2.5.10 is pretty much the same)
>>>>>
>>>>> org.codehaus.groovy:groovy-all -> 3.0.2
>>>>> +--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-ant:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.apache.ant:ant:1.10.7
>>>>> | | \--- org.apache.ant:ant-launcher:1.10.7
>>>>> | +--- org.apache.ant:ant-junit:1.10.7
>>>>> | | \--- org.apache.ant:ant:1.10.7 (*)
>>>>> | +--- org.apache.ant:ant-launcher:1.10.7
>>>>> | +--- org.apache.ant:ant-antlr:1.10.7
>>>>> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- com.github.javaparser:javaparser-core:3.15.13
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2
>>>>> | | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
>>>>> | | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- com.thoughtworks.qdox:qdox:1.12.1
>>>>> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- info.picocli:picocli:4.1.4
>>>>> +--- org.codehaus.groovy:groovy-console:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | \--- org.codehaus.groovy:groovy-swing:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-datetime:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
>>>>> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>> | \--- jline:jline:2.14.6
>>>>> +--- org.codehaus.groovy:groovy-jmx:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-json:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-macro:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-nio:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-servlet:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-sql:3.0.2
>>>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>>>> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>>>> +--- org.codehaus.groovy:groovy-test:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- junit:junit:4.13
>>>>> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
>>>>> | \--- org.hamcrest:hamcrest:2.2
>>>>> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | +--- org.junit.platform:junit-platform-launcher:1.6.0
>>>>> | | +--- org.junit:junit-bom:5.6.0
>>>>> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
>>>>> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
>>>>> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
>>>>> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0
>> (c)
>>>>> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
>>>>> | | \--- org.junit.platform:junit-platform-engine:1.6.0
>>>>> | | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | | +--- org.opentest4j:opentest4j:1.2.0
>>>>> | | \--- org.junit.platform:junit-platform-commons:1.6.0
>>>>> | | \--- org.junit:junit-bom:5.6.0 (*)
>>>>> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
>>>>> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
>>>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>>>> | +--- org.opentest4j:opentest4j:1.2.0
>>>>> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
>>>>> +--- org.codehaus.groovy:groovy-testng:3.0.2
>>>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>>>> | \--- org.testng:testng:6.14.3
>>>>> | \--- com.beust:jcommander:1.72
>>>>> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>>>
>>>>>
>>>>> Vladimir
>>>>>
>
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I approved PR also.
Any volunteer for Release ?
Regards
On Fri, May 8, 2020 at 5:25 PM Felix Schumacher <
felix.schumacher@internetallee.de> wrote:
>
> Am 05.05.20 um 21:22 schrieb Philippe Mouawad:
> > Hello,
> > Good catch, yes it is required.
> >
> > Shall we release or do this before ?
>
> I have created a PR (that Vladimir has already looked into :)) that we
> could merge. I hesitated a bit, as one dependency (spock) is a milestone
> release. But Vladimir seems to be OK with it, as
>
> * Spock will most probably not change that much before a release
>
> * we use Spock at a level, that it is very unlikely, that a change
> would affect our code
>
> I agree with those statements.
>
> What do you (or anyone else) think?
>
> Felix
>
> > Thanks
> > Regards
> >
> > On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
> > felix.schumacher@internetallee.de> wrote:
> >
> >> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
> >>>> Let's update to Groovy 3.
> >>> I see that we currently use groovy-all dependency.
> >>> Unfortunately, it is unpredictable, as it adds new transitive
> >> dependencies
> >>> as Groovy evolves.
> >>>
> >>> I guess we need to specify which dependencies we include explicitly.
> >>> How about groovy,
> >>> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql
> ?
> >> What about groovy-jsr223?
> >>
> >> Felix
> >>
> >>> Here's dependency tree for groovy-all 2.4.18
> >>> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
> >>>
> >>> groovy 3.0.2 (2.5.10 is pretty much the same)
> >>>
> >>> org.codehaus.groovy:groovy-all -> 3.0.2
> >>> +--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-ant:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- org.apache.ant:ant:1.10.7
> >>> | | \--- org.apache.ant:ant-launcher:1.10.7
> >>> | +--- org.apache.ant:ant-junit:1.10.7
> >>> | | \--- org.apache.ant:ant:1.10.7 (*)
> >>> | +--- org.apache.ant:ant-launcher:1.10.7
> >>> | +--- org.apache.ant:ant-antlr:1.10.7
> >>> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- com.github.javaparser:javaparser-core:3.15.13
> >>> | +--- org.codehaus.groovy:groovy-templates:3.0.2
> >>> | | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
> >>> | | \--- org.codehaus.groovy:groovy:3.0.2
> >>> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
> >>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | \--- com.thoughtworks.qdox:qdox:1.12.1
> >>> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | \--- info.picocli:picocli:4.1.4
> >>> +--- org.codehaus.groovy:groovy-console:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> >>> | \--- org.codehaus.groovy:groovy-swing:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-datetime:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
> >>> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
> >>> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
> >>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
> >>> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> >>> | \--- jline:jline:2.14.6
> >>> +--- org.codehaus.groovy:groovy-jmx:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-json:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-macro:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-nio:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-servlet:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> >>> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> >>> +--- org.codehaus.groovy:groovy-sql:3.0.2
> >>> | \--- org.codehaus.groovy:groovy:3.0.2
> >>> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
> >>> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> >>> +--- org.codehaus.groovy:groovy-test:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | \--- junit:junit:4.13
> >>> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
> >>> | \--- org.hamcrest:hamcrest:2.2
> >>> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | +--- org.junit.platform:junit-platform-launcher:1.6.0
> >>> | | +--- org.junit:junit-bom:5.6.0
> >>> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
> >>> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
> >>> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
> >>> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0
> (c)
> >>> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
> >>> | | \--- org.junit.platform:junit-platform-engine:1.6.0
> >>> | | +--- org.junit:junit-bom:5.6.0 (*)
> >>> | | +--- org.opentest4j:opentest4j:1.2.0
> >>> | | \--- org.junit.platform:junit-platform-commons:1.6.0
> >>> | | \--- org.junit:junit-bom:5.6.0 (*)
> >>> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
> >>> | +--- org.junit:junit-bom:5.6.0 (*)
> >>> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
> >>> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
> >>> | +--- org.junit:junit-bom:5.6.0 (*)
> >>> | +--- org.opentest4j:opentest4j:1.2.0
> >>> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
> >>> +--- org.codehaus.groovy:groovy-testng:3.0.2
> >>> | +--- org.codehaus.groovy:groovy:3.0.2
> >>> | \--- org.testng:testng:6.14.3
> >>> | \--- com.beust:jcommander:1.72
> >>> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> >>>
> >>>
> >>> Vladimir
> >>>
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 05.05.20 um 21:22 schrieb Philippe Mouawad:
> Hello,
> Good catch, yes it is required.
>
> Shall we release or do this before ?
I have created a PR (that Vladimir has already looked into :)) that we
could merge. I hesitated a bit, as one dependency (spock) is a milestone
release. But Vladimir seems to be OK with it, as
* Spock will most probably not change that much before a release
* we use Spock at a level, that it is very unlikely, that a change
would affect our code
I agree with those statements.
What do you (or anyone else) think?
Felix
> Thanks
> Regards
>
> On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
>>>> Let's update to Groovy 3.
>>> I see that we currently use groovy-all dependency.
>>> Unfortunately, it is unpredictable, as it adds new transitive
>> dependencies
>>> as Groovy evolves.
>>>
>>> I guess we need to specify which dependencies we include explicitly.
>>> How about groovy,
>>> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql ?
>> What about groovy-jsr223?
>>
>> Felix
>>
>>> Here's dependency tree for groovy-all 2.4.18
>>> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
>>>
>>> groovy 3.0.2 (2.5.10 is pretty much the same)
>>>
>>> org.codehaus.groovy:groovy-all -> 3.0.2
>>> +--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-ant:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- org.apache.ant:ant:1.10.7
>>> | | \--- org.apache.ant:ant-launcher:1.10.7
>>> | +--- org.apache.ant:ant-junit:1.10.7
>>> | | \--- org.apache.ant:ant:1.10.7 (*)
>>> | +--- org.apache.ant:ant-launcher:1.10.7
>>> | +--- org.apache.ant:ant-antlr:1.10.7
>>> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- com.github.javaparser:javaparser-core:3.15.13
>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2
>>> | | +--- org.codehaus.groovy:groovy:3.0.2
>>> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
>>> | | \--- org.codehaus.groovy:groovy:3.0.2
>>> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | \--- com.thoughtworks.qdox:qdox:1.12.1
>>> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | \--- info.picocli:picocli:4.1.4
>>> +--- org.codehaus.groovy:groovy-console:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>> | \--- org.codehaus.groovy:groovy-swing:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-datetime:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
>>> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
>>> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
>>> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>> | \--- jline:jline:2.14.6
>>> +--- org.codehaus.groovy:groovy-jmx:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-json:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-macro:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-nio:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-servlet:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>> +--- org.codehaus.groovy:groovy-sql:3.0.2
>>> | \--- org.codehaus.groovy:groovy:3.0.2
>>> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
>>> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
>>> +--- org.codehaus.groovy:groovy-test:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | \--- junit:junit:4.13
>>> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
>>> | \--- org.hamcrest:hamcrest:2.2
>>> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | +--- org.junit.platform:junit-platform-launcher:1.6.0
>>> | | +--- org.junit:junit-bom:5.6.0
>>> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
>>> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
>>> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
>>> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0 (c)
>>> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
>>> | | \--- org.junit.platform:junit-platform-engine:1.6.0
>>> | | +--- org.junit:junit-bom:5.6.0 (*)
>>> | | +--- org.opentest4j:opentest4j:1.2.0
>>> | | \--- org.junit.platform:junit-platform-commons:1.6.0
>>> | | \--- org.junit:junit-bom:5.6.0 (*)
>>> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
>>> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
>>> | +--- org.junit:junit-bom:5.6.0 (*)
>>> | +--- org.opentest4j:opentest4j:1.2.0
>>> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
>>> +--- org.codehaus.groovy:groovy-testng:3.0.2
>>> | +--- org.codehaus.groovy:groovy:3.0.2
>>> | \--- org.testng:testng:6.14.3
>>> | \--- com.beust:jcommander:1.72
>>> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>>>
>>>
>>> Vladimir
>>>
>
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
Good catch, yes it is required.
Shall we release or do this before ?
Thanks
Regards
On Sun, May 3, 2020 at 2:20 PM Felix Schumacher <
felix.schumacher@internetallee.de> wrote:
>
> Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
> >> Let's update to Groovy 3.
> > I see that we currently use groovy-all dependency.
> > Unfortunately, it is unpredictable, as it adds new transitive
> dependencies
> > as Groovy evolves.
> >
> > I guess we need to specify which dependencies we include explicitly.
> > How about groovy,
> > groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql ?
>
> What about groovy-jsr223?
>
> Felix
>
> >
> > Here's dependency tree for groovy-all 2.4.18
> > org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
> >
> > groovy 3.0.2 (2.5.10 is pretty much the same)
> >
> > org.codehaus.groovy:groovy-all -> 3.0.2
> > +--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-ant:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- org.apache.ant:ant:1.10.7
> > | | \--- org.apache.ant:ant-launcher:1.10.7
> > | +--- org.apache.ant:ant-junit:1.10.7
> > | | \--- org.apache.ant:ant:1.10.7 (*)
> > | +--- org.apache.ant:ant-launcher:1.10.7
> > | +--- org.apache.ant:ant-antlr:1.10.7
> > | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- com.github.javaparser:javaparser-core:3.15.13
> > | +--- org.codehaus.groovy:groovy-templates:3.0.2
> > | | +--- org.codehaus.groovy:groovy:3.0.2
> > | | \--- org.codehaus.groovy:groovy-xml:3.0.2
> > | | \--- org.codehaus.groovy:groovy:3.0.2
> > | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
> > | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | \--- com.thoughtworks.qdox:qdox:1.12.1
> > +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | \--- info.picocli:picocli:4.1.4
> > +--- org.codehaus.groovy:groovy-console:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> > | \--- org.codehaus.groovy:groovy-swing:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-datetime:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
> > +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
> > +--- org.codehaus.groovy:groovy-groovysh:3.0.2
> > | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
> > | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> > | \--- jline:jline:2.14.6
> > +--- org.codehaus.groovy:groovy-jmx:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-json:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-jsr223:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-macro:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-nio:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-servlet:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> > | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> > +--- org.codehaus.groovy:groovy-sql:3.0.2
> > | \--- org.codehaus.groovy:groovy:3.0.2
> > +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
> > +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> > +--- org.codehaus.groovy:groovy-test:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | \--- junit:junit:4.13
> > | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
> > | \--- org.hamcrest:hamcrest:2.2
> > +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | +--- org.junit.platform:junit-platform-launcher:1.6.0
> > | | +--- org.junit:junit-bom:5.6.0
> > | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
> > | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
> > | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
> > | | | +--- org.junit.platform:junit-platform-launcher:1.6.0 (c)
> > | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
> > | | \--- org.junit.platform:junit-platform-engine:1.6.0
> > | | +--- org.junit:junit-bom:5.6.0 (*)
> > | | +--- org.opentest4j:opentest4j:1.2.0
> > | | \--- org.junit.platform:junit-platform-commons:1.6.0
> > | | \--- org.junit:junit-bom:5.6.0 (*)
> > | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
> > | +--- org.junit:junit-bom:5.6.0 (*)
> > | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
> > | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
> > | +--- org.junit:junit-bom:5.6.0 (*)
> > | +--- org.opentest4j:opentest4j:1.2.0
> > | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
> > +--- org.codehaus.groovy:groovy-testng:3.0.2
> > | +--- org.codehaus.groovy:groovy:3.0.2
> > | \--- org.testng:testng:6.14.3
> > | \--- com.beust:jcommander:1.72
> > \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> >
> >
> > Vladimir
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 07.04.20 um 13:18 schrieb Vladimir Sitnikov:
>> Let's update to Groovy 3.
> I see that we currently use groovy-all dependency.
> Unfortunately, it is unpredictable, as it adds new transitive dependencies
> as Groovy evolves.
>
> I guess we need to specify which dependencies we include explicitly.
> How about groovy,
> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql ?
What about groovy-jsr223?
Felix
>
> Here's dependency tree for groovy-all 2.4.18
> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
>
> groovy 3.0.2 (2.5.10 is pretty much the same)
>
> org.codehaus.groovy:groovy-all -> 3.0.2
> +--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-ant:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.apache.ant:ant:1.10.7
> | | \--- org.apache.ant:ant-launcher:1.10.7
> | +--- org.apache.ant:ant-junit:1.10.7
> | | \--- org.apache.ant:ant:1.10.7 (*)
> | +--- org.apache.ant:ant-launcher:1.10.7
> | +--- org.apache.ant:ant-antlr:1.10.7
> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- com.github.javaparser:javaparser-core:3.15.13
> | +--- org.codehaus.groovy:groovy-templates:3.0.2
> | | +--- org.codehaus.groovy:groovy:3.0.2
> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
> | | \--- org.codehaus.groovy:groovy:3.0.2
> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- com.thoughtworks.qdox:qdox:1.12.1
> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- info.picocli:picocli:4.1.4
> +--- org.codehaus.groovy:groovy-console:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | \--- org.codehaus.groovy:groovy-swing:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-datetime:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> | \--- jline:jline:2.14.6
> +--- org.codehaus.groovy:groovy-jmx:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-json:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-macro:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-nio:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-servlet:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-sql:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-test:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- junit:junit:4.13
> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
> | \--- org.hamcrest:hamcrest:2.2
> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.junit.platform:junit-platform-launcher:1.6.0
> | | +--- org.junit:junit-bom:5.6.0
> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0 (c)
> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
> | | \--- org.junit.platform:junit-platform-engine:1.6.0
> | | +--- org.junit:junit-bom:5.6.0 (*)
> | | +--- org.opentest4j:opentest4j:1.2.0
> | | \--- org.junit.platform:junit-platform-commons:1.6.0
> | | \--- org.junit:junit-bom:5.6.0 (*)
> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
> | +--- org.junit:junit-bom:5.6.0 (*)
> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
> | +--- org.junit:junit-bom:5.6.0 (*)
> | +--- org.opentest4j:opentest4j:1.2.0
> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
> +--- org.codehaus.groovy:groovy-testng:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- org.testng:testng:6.14.3
> | \--- com.beust:jcommander:1.72
> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>
>
> Vladimir
>
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
Just a little update to say, the last issue seems to be also fixed by 2.1.1
Regards
On Saturday, May 2, 2020, Philippe Mouawad <ph...@gmail.com>
wrote:
> Hello all,
> I hope you're fine.
>
> I upgraded to 2.1.1 of Darklaf (Thanks Jannis for reactivity) and it fixed
> 2 issues seen:
>
> - NPE when saving file (https://github.com/weisJ/darklaf/issues/157)
> - https://github.com/weisJ/darklaf/issues/155
>
>
> But I am still facing this one, do you also confirm this problem when
> testing nightly ?
>
> - https://github.com/weisJ/darklaf/issues/156
>
> It depends on version of Java I use.
> Do you also reproduce it under same conditions ?
> Should we release with current state ?
>
> Thanks
> Regards
>
> On Thu, Apr 30, 2020 at 11:00 PM Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Thanks Jannis
>> Upgraded to 2.1.0, issue is fixed.
>> But I see 2 new blocking issues:
>> https://github.com/weisJ/darklaf/issues/156 (not sure it's a new one)
>> https://github.com/weisJ/darklaf/issues/155 (it's a new one for sure)
>>
>> Regards
>>
>> On Wed, Apr 29, 2020 at 5:49 PM <we...@arcor.de> wrote:
>>
>>> Hello,
>>>
>>> the issue is already fixed in the current upstream version of Darklaf.
>>> I’ll probably release the next version tomorrow or on Friday. The setting
>>> to render/edit booleans as checkboxes can also be disabled manually using
>>> the “darklaf.tableBooleanRenderer=false” and
>>> “darklaf.treeBooleanRenderer=false”.
>>>
>>> Best regards
>>> Jannis
>>> On 29. Apr 2020, 14:34 +0200, Philippe Mouawad <
>>> philippe.mouawad@gmail.com>, wrote:
>>> > Hello,
>>> > Another issue related to DarkLaf I think.
>>> > Checkboxes "encode?" is not checkable in HTTP Request
>>> > That's a blocker one
>>> >
>>> > Regards
>>> >
>>> > On Sun, Apr 26, 2020 at 6:26 PM Philippe Mouawad <
>>> philippe.mouawad@gmail.com>
>>> > wrote:
>>> >
>>> > > Hello,
>>> > > Regression seen here:
>>> > > https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
>>> > >
>>> > > Regards
>>> > >
>>> > > On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <
>>> > > philippe.mouawad@gmail.com> wrote:
>>> > >
>>> > > > Hello,
>>> > > > The two issues are now fixed.
>>> > > > I guess we can start a release.
>>> > > >
>>> > > > Regards
>>> > > >
>>> > > > On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
>>> > > > philippe.mouawad@gmail.com> wrote:
>>> > > >
>>> > > > > Hello,
>>> > > > > 2 other issues:
>>> > > > >
>>> > > > > - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
>>> > > > > - https://github.com/weisJ/darklaf/issues/135
>>> > > > >
>>> > > > > Regards
>>> > > > >
>>> > > > >
>>> > > > > On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
>>> > > > > philippe.mouawad@gmail.com> wrote:
>>> > > > >
>>> > > > > > Hello,
>>> > > > > > I have found a blocker issue with release.
>>> > > > > > See:
>>> > > > > > https://github.com/weisJ/darklaf/issues/133
>>> > > > > >
>>> > > > > > Regards
>>> > > > > >
>>> > > > > > On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <
>>> > > > > > ra0077@gmail.com> wrote:
>>> > > > > >
>>> > > > > > > Hi
>>> > > > > > >
>>> > > > > > > i have tested JMeter-Plugins in the latest nightly build of
>>> JMeter in
>>> > > > > > > Linux
>>> > > > > > > Ubuntu and it's ok (no more errors)
>>> > > > > > >
>>> > > > > > > Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
>>> > > > > > > philippe.mouawad@gmail.com>
>>> > > > > > > a écrit :
>>> > > > > > >
>>> > > > > > > > Hello,
>>> > > > > > > > JMeter-Plugins has been released. Can somebody else test
>>> if it's ok ?
>>> > > > > > > >
>>> > > > > > > > Thanks
>>> > > > > > > >
>>> > > > > > > > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>>> > > > > > > > philippe.mouawad@gmail.com>
>>> > > > > > > > wrote:
>>> > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>>> > > > > > > > > sitnikov.vladimir@gmail.com> wrote:
>>> > > > > > > > >
>>> > > > > > > > > > Philippe>I would add those 2:
>>> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-templates :
>>> > > > > > > > > > Philippe>
>>> > > > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > >
>>> > > > > > > https://docs.groovy-lang.org/docs/next/html/documentation/
>>> template-engines.html
>>> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>>> > > > > > > > > >
>>> > > > > > > > > > The libraries were on my list as well:
>>> > > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > indeed, not explicit enough for me :-)
>>> > > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > > > > Vladimir> How about groovy,
>>> > > > > > > > > > Vladimir> groovy-datetime, groovy-jmx, groovy-json,
>>> > > > > > > groovy-templates,
>>> > > > > > > > > > groovy-sql ?
>>> > > > > > > > > >
>>> > > > > > > > > > Philippe>Don't we also need:
>>> > > > > > > > > > Philippe>- org.codehaus.groovy:groovy-astbuilder
>>> > > > > > > > > >
>>> > > > > > > > > > I think the ones who can understand astbuilder are
>>> smart enough
>>> > > > > > > to add
>>> > > > > > > > the
>>> > > > > > > > > > relevant jars themselves :)
>>> > > > > > > > > > Of course, we could consider bundling the dependency
>>> if there's a
>>> > > > > > > use
>>> > > > > > > > > > case,
>>> > > > > > > > > > however,
>>> > > > > > > > > > I do not think there's a common use-case for doing AST
>>> > > > > > > transformations
>>> > > > > > > > > > inside JSR223 samplers.
>>> > > > > > > > > >
>>> > > > > > > > > > Vladimir
>>> > > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > --
>>> > > > > > > > > Cordialement.
>>> > > > > > > > > Philippe Mouawad.
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > > > > --
>>> > > > > > > > Cordialement.
>>> > > > > > > > Philippe Mouawad.
>>> > > > > > > >
>>> > > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > --
>>> > > > > > Cordialement.
>>> > > > > > Philippe Mouawad.
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > > > --
>>> > > > > Cordialement.
>>> > > > > Philippe Mouawad.
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > >
>>> > > > --
>>> > > > Cordialement.
>>> > > > Philippe Mouawad.
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> > > --
>>> > > Cordialement.
>>> > > Philippe Mouawad.
>>> > >
>>> > >
>>> > >
>>> >
>>> > --
>>> > Cordialement.
>>> > Philippe Mouawad.
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello all,
I hope you're fine.
I upgraded to 2.1.1 of Darklaf (Thanks Jannis for reactivity) and it fixed
2 issues seen:
- NPE when saving file (https://github.com/weisJ/darklaf/issues/157)
- https://github.com/weisJ/darklaf/issues/155
But I am still facing this one, do you also confirm this problem when
testing nightly ?
- https://github.com/weisJ/darklaf/issues/156
It depends on version of Java I use.
Do you also reproduce it under same conditions ?
Should we release with current state ?
Thanks
Regards
On Thu, Apr 30, 2020 at 11:00 PM Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Thanks Jannis
> Upgraded to 2.1.0, issue is fixed.
> But I see 2 new blocking issues:
> https://github.com/weisJ/darklaf/issues/156 (not sure it's a new one)
> https://github.com/weisJ/darklaf/issues/155 (it's a new one for sure)
>
> Regards
>
> On Wed, Apr 29, 2020 at 5:49 PM <we...@arcor.de> wrote:
>
>> Hello,
>>
>> the issue is already fixed in the current upstream version of Darklaf.
>> I’ll probably release the next version tomorrow or on Friday. The setting
>> to render/edit booleans as checkboxes can also be disabled manually using
>> the “darklaf.tableBooleanRenderer=false” and
>> “darklaf.treeBooleanRenderer=false”.
>>
>> Best regards
>> Jannis
>> On 29. Apr 2020, 14:34 +0200, Philippe Mouawad <
>> philippe.mouawad@gmail.com>, wrote:
>> > Hello,
>> > Another issue related to DarkLaf I think.
>> > Checkboxes "encode?" is not checkable in HTTP Request
>> > That's a blocker one
>> >
>> > Regards
>> >
>> > On Sun, Apr 26, 2020 at 6:26 PM Philippe Mouawad <
>> philippe.mouawad@gmail.com>
>> > wrote:
>> >
>> > > Hello,
>> > > Regression seen here:
>> > > https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
>> > >
>> > > Regards
>> > >
>> > > On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <
>> > > philippe.mouawad@gmail.com> wrote:
>> > >
>> > > > Hello,
>> > > > The two issues are now fixed.
>> > > > I guess we can start a release.
>> > > >
>> > > > Regards
>> > > >
>> > > > On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
>> > > > philippe.mouawad@gmail.com> wrote:
>> > > >
>> > > > > Hello,
>> > > > > 2 other issues:
>> > > > >
>> > > > > - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
>> > > > > - https://github.com/weisJ/darklaf/issues/135
>> > > > >
>> > > > > Regards
>> > > > >
>> > > > >
>> > > > > On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
>> > > > > philippe.mouawad@gmail.com> wrote:
>> > > > >
>> > > > > > Hello,
>> > > > > > I have found a blocker issue with release.
>> > > > > > See:
>> > > > > > https://github.com/weisJ/darklaf/issues/133
>> > > > > >
>> > > > > > Regards
>> > > > > >
>> > > > > > On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <
>> > > > > > ra0077@gmail.com> wrote:
>> > > > > >
>> > > > > > > Hi
>> > > > > > >
>> > > > > > > i have tested JMeter-Plugins in the latest nightly build of
>> JMeter in
>> > > > > > > Linux
>> > > > > > > Ubuntu and it's ok (no more errors)
>> > > > > > >
>> > > > > > > Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
>> > > > > > > philippe.mouawad@gmail.com>
>> > > > > > > a écrit :
>> > > > > > >
>> > > > > > > > Hello,
>> > > > > > > > JMeter-Plugins has been released. Can somebody else test if
>> it's ok ?
>> > > > > > > >
>> > > > > > > > Thanks
>> > > > > > > >
>> > > > > > > > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>> > > > > > > > philippe.mouawad@gmail.com>
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>> > > > > > > > > sitnikov.vladimir@gmail.com> wrote:
>> > > > > > > > >
>> > > > > > > > > > Philippe>I would add those 2:
>> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-templates :
>> > > > > > > > > > Philippe>
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>> > > > > > > > > >
>> > > > > > > > > > The libraries were on my list as well:
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > indeed, not explicit enough for me :-)
>> > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > Vladimir> How about groovy,
>> > > > > > > > > > Vladimir> groovy-datetime, groovy-jmx, groovy-json,
>> > > > > > > groovy-templates,
>> > > > > > > > > > groovy-sql ?
>> > > > > > > > > >
>> > > > > > > > > > Philippe>Don't we also need:
>> > > > > > > > > > Philippe>- org.codehaus.groovy:groovy-astbuilder
>> > > > > > > > > >
>> > > > > > > > > > I think the ones who can understand astbuilder are
>> smart enough
>> > > > > > > to add
>> > > > > > > > the
>> > > > > > > > > > relevant jars themselves :)
>> > > > > > > > > > Of course, we could consider bundling the dependency if
>> there's a
>> > > > > > > use
>> > > > > > > > > > case,
>> > > > > > > > > > however,
>> > > > > > > > > > I do not think there's a common use-case for doing AST
>> > > > > > > transformations
>> > > > > > > > > > inside JSR223 samplers.
>> > > > > > > > > >
>> > > > > > > > > > Vladimir
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > --
>> > > > > > > > > Cordialement.
>> > > > > > > > > Philippe Mouawad.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Cordialement.
>> > > > > > > > Philippe Mouawad.
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Cordialement.
>> > > > > > Philippe Mouawad.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > > --
>> > > > > Cordialement.
>> > > > > Philippe Mouawad.
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Cordialement.
>> > > > Philippe Mouawad.
>> > > >
>> > > >
>> > > >
>> > >
>> > > --
>> > > Cordialement.
>> > > Philippe Mouawad.
>> > >
>> > >
>> > >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Thanks Jannis
Upgraded to 2.1.0, issue is fixed.
But I see 2 new blocking issues:
https://github.com/weisJ/darklaf/issues/156 (not sure it's a new one)
https://github.com/weisJ/darklaf/issues/155 (it's a new one for sure)
Regards
On Wed, Apr 29, 2020 at 5:49 PM <we...@arcor.de> wrote:
> Hello,
>
> the issue is already fixed in the current upstream version of Darklaf.
> I’ll probably release the next version tomorrow or on Friday. The setting
> to render/edit booleans as checkboxes can also be disabled manually using
> the “darklaf.tableBooleanRenderer=false” and
> “darklaf.treeBooleanRenderer=false”.
>
> Best regards
> Jannis
> On 29. Apr 2020, 14:34 +0200, Philippe Mouawad <ph...@gmail.com>,
> wrote:
> > Hello,
> > Another issue related to DarkLaf I think.
> > Checkboxes "encode?" is not checkable in HTTP Request
> > That's a blocker one
> >
> > Regards
> >
> > On Sun, Apr 26, 2020 at 6:26 PM Philippe Mouawad <
> philippe.mouawad@gmail.com>
> > wrote:
> >
> > > Hello,
> > > Regression seen here:
> > > https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
> > >
> > > Regards
> > >
> > > On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <
> > > philippe.mouawad@gmail.com> wrote:
> > >
> > > > Hello,
> > > > The two issues are now fixed.
> > > > I guess we can start a release.
> > > >
> > > > Regards
> > > >
> > > > On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
> > > > philippe.mouawad@gmail.com> wrote:
> > > >
> > > > > Hello,
> > > > > 2 other issues:
> > > > >
> > > > > - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
> > > > > - https://github.com/weisJ/darklaf/issues/135
> > > > >
> > > > > Regards
> > > > >
> > > > >
> > > > > On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
> > > > > philippe.mouawad@gmail.com> wrote:
> > > > >
> > > > > > Hello,
> > > > > > I have found a blocker issue with release.
> > > > > > See:
> > > > > > https://github.com/weisJ/darklaf/issues/133
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <
> > > > > > ra0077@gmail.com> wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > i have tested JMeter-Plugins in the latest nightly build of
> JMeter in
> > > > > > > Linux
> > > > > > > Ubuntu and it's ok (no more errors)
> > > > > > >
> > > > > > > Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
> > > > > > > philippe.mouawad@gmail.com>
> > > > > > > a écrit :
> > > > > > >
> > > > > > > > Hello,
> > > > > > > > JMeter-Plugins has been released. Can somebody else test if
> it's ok ?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
> > > > > > > > philippe.mouawad@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
> > > > > > > > > sitnikov.vladimir@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > > Philippe>I would add those 2:
> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-templates :
> > > > > > > > > > Philippe>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > >
> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
> > > > > > > > > > Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
> > > > > > > > > >
> > > > > > > > > > The libraries were on my list as well:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > indeed, not explicit enough for me :-)
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Vladimir> How about groovy,
> > > > > > > > > > Vladimir> groovy-datetime, groovy-jmx, groovy-json,
> > > > > > > groovy-templates,
> > > > > > > > > > groovy-sql ?
> > > > > > > > > >
> > > > > > > > > > Philippe>Don't we also need:
> > > > > > > > > > Philippe>- org.codehaus.groovy:groovy-astbuilder
> > > > > > > > > >
> > > > > > > > > > I think the ones who can understand astbuilder are smart
> enough
> > > > > > > to add
> > > > > > > > the
> > > > > > > > > > relevant jars themselves :)
> > > > > > > > > > Of course, we could consider bundling the dependency if
> there's a
> > > > > > > use
> > > > > > > > > > case,
> > > > > > > > > > however,
> > > > > > > > > > I do not think there's a common use-case for doing AST
> > > > > > > transformations
> > > > > > > > > > inside JSR223 samplers.
> > > > > > > > > >
> > > > > > > > > > Vladimir
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Cordialement.
> > > > > > > > > Philippe Mouawad.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Cordialement.
> > > > > > > > Philippe Mouawad.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Cordialement.
> > > > > > Philippe Mouawad.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Cordialement.
> > > > > Philippe Mouawad.
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Cordialement.
> > > > Philippe Mouawad.
> > > >
> > > >
> > > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > >
> > >
> > >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by we...@arcor.de.
Hello,
the issue is already fixed in the current upstream version of Darklaf. I’ll probably release the next version tomorrow or on Friday. The setting to render/edit booleans as checkboxes can also be disabled manually using the “darklaf.tableBooleanRenderer=false” and “darklaf.treeBooleanRenderer=false”.
Best regards
Jannis
On 29. Apr 2020, 14:34 +0200, Philippe Mouawad <ph...@gmail.com>, wrote:
> Hello,
> Another issue related to DarkLaf I think.
> Checkboxes "encode?" is not checkable in HTTP Request
> That's a blocker one
>
> Regards
>
> On Sun, Apr 26, 2020 at 6:26 PM Philippe Mouawad <ph...@gmail.com>
> wrote:
>
> > Hello,
> > Regression seen here:
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
> >
> > Regards
> >
> > On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <
> > philippe.mouawad@gmail.com> wrote:
> >
> > > Hello,
> > > The two issues are now fixed.
> > > I guess we can start a release.
> > >
> > > Regards
> > >
> > > On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
> > > philippe.mouawad@gmail.com> wrote:
> > >
> > > > Hello,
> > > > 2 other issues:
> > > >
> > > > - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
> > > > - https://github.com/weisJ/darklaf/issues/135
> > > >
> > > > Regards
> > > >
> > > >
> > > > On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
> > > > philippe.mouawad@gmail.com> wrote:
> > > >
> > > > > Hello,
> > > > > I have found a blocker issue with release.
> > > > > See:
> > > > > https://github.com/weisJ/darklaf/issues/133
> > > > >
> > > > > Regards
> > > > >
> > > > > On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <
> > > > > ra0077@gmail.com> wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > i have tested JMeter-Plugins in the latest nightly build of JMeter in
> > > > > > Linux
> > > > > > Ubuntu and it's ok (no more errors)
> > > > > >
> > > > > > Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
> > > > > > philippe.mouawad@gmail.com>
> > > > > > a écrit :
> > > > > >
> > > > > > > Hello,
> > > > > > > JMeter-Plugins has been released. Can somebody else test if it's ok ?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
> > > > > > > philippe.mouawad@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
> > > > > > > > sitnikov.vladimir@gmail.com> wrote:
> > > > > > > >
> > > > > > > > > Philippe>I would add those 2:
> > > > > > > > > Philippe> - org.codehaus.groovy:groovy-templates :
> > > > > > > > > Philippe>
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
> > > > > > > > > Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
> > > > > > > > >
> > > > > > > > > The libraries were on my list as well:
> > > > > > > > >
> > > > > > > >
> > > > > > > > indeed, not explicit enough for me :-)
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Vladimir> How about groovy,
> > > > > > > > > Vladimir> groovy-datetime, groovy-jmx, groovy-json,
> > > > > > groovy-templates,
> > > > > > > > > groovy-sql ?
> > > > > > > > >
> > > > > > > > > Philippe>Don't we also need:
> > > > > > > > > Philippe>- org.codehaus.groovy:groovy-astbuilder
> > > > > > > > >
> > > > > > > > > I think the ones who can understand astbuilder are smart enough
> > > > > > to add
> > > > > > > the
> > > > > > > > > relevant jars themselves :)
> > > > > > > > > Of course, we could consider bundling the dependency if there's a
> > > > > > use
> > > > > > > > > case,
> > > > > > > > > however,
> > > > > > > > > I do not think there's a common use-case for doing AST
> > > > > > transformations
> > > > > > > > > inside JSR223 samplers.
> > > > > > > > >
> > > > > > > > > Vladimir
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Cordialement.
> > > > > > > > Philippe Mouawad.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Cordialement.
> > > > > > > Philippe Mouawad.
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Cordialement.
> > > > > Philippe Mouawad.
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Cordialement.
> > > > Philippe Mouawad.
> > > >
> > > >
> > > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > >
> > >
> > >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
> >
> >
>
> --
> Cordialement.
> Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
Another issue related to DarkLaf I think.
Checkboxes "encode?" is not checkable in HTTP Request
That's a blocker one
Regards
On Sun, Apr 26, 2020 at 6:26 PM Philippe Mouawad <ph...@gmail.com>
wrote:
> Hello,
> Regression seen here:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
>
> Regards
>
> On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> The two issues are now fixed.
>> I guess we can start a release.
>>
>> Regards
>>
>> On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Hello,
>>> 2 other issues:
>>>
>>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
>>> - https://github.com/weisJ/darklaf/issues/135
>>>
>>> Regards
>>>
>>>
>>> On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
>>> philippe.mouawad@gmail.com> wrote:
>>>
>>>> Hello,
>>>> I have found a blocker issue with release.
>>>> See:
>>>> https://github.com/weisJ/darklaf/issues/133
>>>>
>>>> Regards
>>>>
>>>> On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <
>>>> ra0077@gmail.com> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> i have tested JMeter-Plugins in the latest nightly build of JMeter in
>>>>> Linux
>>>>> Ubuntu and it's ok (no more errors)
>>>>>
>>>>> Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
>>>>> philippe.mouawad@gmail.com>
>>>>> a écrit :
>>>>>
>>>>> > Hello,
>>>>> > JMeter-Plugins has been released. Can somebody else test if it's ok ?
>>>>> >
>>>>> > Thanks
>>>>> >
>>>>> > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>>>>> > philippe.mouawad@gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> > >
>>>>> > >
>>>>> > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>>>>> > > sitnikov.vladimir@gmail.com> wrote:
>>>>> > >
>>>>> > >> Philippe>I would add those 2:
>>>>> > >> Philippe> - org.codehaus.groovy:groovy-templates :
>>>>> > >> Philippe>
>>>>> > >>
>>>>> > >>
>>>>> >
>>>>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>>>>> > >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>>>>> > >>
>>>>> > >> The libraries were on my list as well:
>>>>> > >>
>>>>> > >
>>>>> > > indeed, not explicit enough for me :-)
>>>>> > >
>>>>> > >>
>>>>> > >> Vladimir> How about groovy,
>>>>> > >> Vladimir> groovy-datetime, groovy-jmx, groovy-json,
>>>>> groovy-templates,
>>>>> > >> groovy-sql ?
>>>>> > >>
>>>>> > >> Philippe>Don't we also need:
>>>>> > >> Philippe>- org.codehaus.groovy:groovy-astbuilder
>>>>> > >>
>>>>> > >> I think the ones who can understand astbuilder are smart enough
>>>>> to add
>>>>> > the
>>>>> > >> relevant jars themselves :)
>>>>> > >> Of course, we could consider bundling the dependency if there's a
>>>>> use
>>>>> > >> case,
>>>>> > >> however,
>>>>> > >> I do not think there's a common use-case for doing AST
>>>>> transformations
>>>>> > >> inside JSR223 samplers.
>>>>> > >>
>>>>> > >> Vladimir
>>>>> > >>
>>>>> > >
>>>>> > >
>>>>> > > --
>>>>> > > Cordialement.
>>>>> > > Philippe Mouawad.
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> >
>>>>> > --
>>>>> > Cordialement.
>>>>> > Philippe Mouawad.
>>>>> >
>>>>>
>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>>
>>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
Regression seen here:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64382
Regards
On Sat, Apr 25, 2020 at 3:09 PM Philippe Mouawad <ph...@gmail.com>
wrote:
> Hello,
> The two issues are now fixed.
> I guess we can start a release.
>
> Regards
>
> On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> 2 other issues:
>>
>> - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
>> - https://github.com/weisJ/darklaf/issues/135
>>
>> Regards
>>
>>
>> On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Hello,
>>> I have found a blocker issue with release.
>>> See:
>>> https://github.com/weisJ/darklaf/issues/133
>>>
>>> Regards
>>>
>>> On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <ra...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> i have tested JMeter-Plugins in the latest nightly build of JMeter in
>>>> Linux
>>>> Ubuntu and it's ok (no more errors)
>>>>
>>>> Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
>>>> philippe.mouawad@gmail.com>
>>>> a écrit :
>>>>
>>>> > Hello,
>>>> > JMeter-Plugins has been released. Can somebody else test if it's ok ?
>>>> >
>>>> > Thanks
>>>> >
>>>> > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>>>> > philippe.mouawad@gmail.com>
>>>> > wrote:
>>>> >
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>>>> > > sitnikov.vladimir@gmail.com> wrote:
>>>> > >
>>>> > >> Philippe>I would add those 2:
>>>> > >> Philippe> - org.codehaus.groovy:groovy-templates :
>>>> > >> Philippe>
>>>> > >>
>>>> > >>
>>>> >
>>>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>>>> > >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>>>> > >>
>>>> > >> The libraries were on my list as well:
>>>> > >>
>>>> > >
>>>> > > indeed, not explicit enough for me :-)
>>>> > >
>>>> > >>
>>>> > >> Vladimir> How about groovy,
>>>> > >> Vladimir> groovy-datetime, groovy-jmx, groovy-json,
>>>> groovy-templates,
>>>> > >> groovy-sql ?
>>>> > >>
>>>> > >> Philippe>Don't we also need:
>>>> > >> Philippe>- org.codehaus.groovy:groovy-astbuilder
>>>> > >>
>>>> > >> I think the ones who can understand astbuilder are smart enough to
>>>> add
>>>> > the
>>>> > >> relevant jars themselves :)
>>>> > >> Of course, we could consider bundling the dependency if there's a
>>>> use
>>>> > >> case,
>>>> > >> however,
>>>> > >> I do not think there's a common use-case for doing AST
>>>> transformations
>>>> > >> inside JSR223 samplers.
>>>> > >>
>>>> > >> Vladimir
>>>> > >>
>>>> > >
>>>> > >
>>>> > > --
>>>> > > Cordialement.
>>>> > > Philippe Mouawad.
>>>> > >
>>>> > >
>>>> > >
>>>> >
>>>> > --
>>>> > Cordialement.
>>>> > Philippe Mouawad.
>>>> >
>>>>
>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
The two issues are now fixed.
I guess we can start a release.
Regards
On Sat, Apr 11, 2020 at 12:14 PM Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Hello,
> 2 other issues:
>
> - https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
> - https://github.com/weisJ/darklaf/issues/135
>
> Regards
>
>
> On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> I have found a blocker issue with release.
>> See:
>> https://github.com/weisJ/darklaf/issues/133
>>
>> Regards
>>
>> On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <ra...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> i have tested JMeter-Plugins in the latest nightly build of JMeter in
>>> Linux
>>> Ubuntu and it's ok (no more errors)
>>>
>>> Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <
>>> philippe.mouawad@gmail.com>
>>> a écrit :
>>>
>>> > Hello,
>>> > JMeter-Plugins has been released. Can somebody else test if it's ok ?
>>> >
>>> > Thanks
>>> >
>>> > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>>> > philippe.mouawad@gmail.com>
>>> > wrote:
>>> >
>>> > >
>>> > >
>>> > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>>> > > sitnikov.vladimir@gmail.com> wrote:
>>> > >
>>> > >> Philippe>I would add those 2:
>>> > >> Philippe> - org.codehaus.groovy:groovy-templates :
>>> > >> Philippe>
>>> > >>
>>> > >>
>>> >
>>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>>> > >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>>> > >>
>>> > >> The libraries were on my list as well:
>>> > >>
>>> > >
>>> > > indeed, not explicit enough for me :-)
>>> > >
>>> > >>
>>> > >> Vladimir> How about groovy,
>>> > >> Vladimir> groovy-datetime, groovy-jmx, groovy-json,
>>> groovy-templates,
>>> > >> groovy-sql ?
>>> > >>
>>> > >> Philippe>Don't we also need:
>>> > >> Philippe>- org.codehaus.groovy:groovy-astbuilder
>>> > >>
>>> > >> I think the ones who can understand astbuilder are smart enough to
>>> add
>>> > the
>>> > >> relevant jars themselves :)
>>> > >> Of course, we could consider bundling the dependency if there's a
>>> use
>>> > >> case,
>>> > >> however,
>>> > >> I do not think there's a common use-case for doing AST
>>> transformations
>>> > >> inside JSR223 samplers.
>>> > >>
>>> > >> Vladimir
>>> > >>
>>> > >
>>> > >
>>> > > --
>>> > > Cordialement.
>>> > > Philippe Mouawad.
>>> > >
>>> > >
>>> > >
>>> >
>>> > --
>>> > Cordialement.
>>> > Philippe Mouawad.
>>> >
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
2 other issues:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=64340
- https://github.com/weisJ/darklaf/issues/135
Regards
On Thu, Apr 9, 2020 at 3:31 PM Philippe Mouawad <ph...@gmail.com>
wrote:
> Hello,
> I have found a blocker issue with release.
> See:
> https://github.com/weisJ/darklaf/issues/133
>
> Regards
>
> On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <ra...@gmail.com>
> wrote:
>
>> Hi
>>
>> i have tested JMeter-Plugins in the latest nightly build of JMeter in
>> Linux
>> Ubuntu and it's ok (no more errors)
>>
>> Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <philippe.mouawad@gmail.com
>> >
>> a écrit :
>>
>> > Hello,
>> > JMeter-Plugins has been released. Can somebody else test if it's ok ?
>> >
>> > Thanks
>> >
>> > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
>> > philippe.mouawad@gmail.com>
>> > wrote:
>> >
>> > >
>> > >
>> > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
>> > > sitnikov.vladimir@gmail.com> wrote:
>> > >
>> > >> Philippe>I would add those 2:
>> > >> Philippe> - org.codehaus.groovy:groovy-templates :
>> > >> Philippe>
>> > >>
>> > >>
>> >
>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>> > >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>> > >>
>> > >> The libraries were on my list as well:
>> > >>
>> > >
>> > > indeed, not explicit enough for me :-)
>> > >
>> > >>
>> > >> Vladimir> How about groovy,
>> > >> Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
>> > >> groovy-sql ?
>> > >>
>> > >> Philippe>Don't we also need:
>> > >> Philippe>- org.codehaus.groovy:groovy-astbuilder
>> > >>
>> > >> I think the ones who can understand astbuilder are smart enough to
>> add
>> > the
>> > >> relevant jars themselves :)
>> > >> Of course, we could consider bundling the dependency if there's a use
>> > >> case,
>> > >> however,
>> > >> I do not think there's a common use-case for doing AST
>> transformations
>> > >> inside JSR223 samplers.
>> > >>
>> > >> Vladimir
>> > >>
>> > >
>> > >
>> > > --
>> > > Cordialement.
>> > > Philippe Mouawad.
>> > >
>> > >
>> > >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>> >
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I have found a blocker issue with release.
See:
https://github.com/weisJ/darklaf/issues/133
Regards
On Wed, Apr 8, 2020 at 7:25 PM Antonio Gomes Rodrigues <ra...@gmail.com>
wrote:
> Hi
>
> i have tested JMeter-Plugins in the latest nightly build of JMeter in Linux
> Ubuntu and it's ok (no more errors)
>
> Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <ph...@gmail.com>
> a écrit :
>
> > Hello,
> > JMeter-Plugins has been released. Can somebody else test if it's ok ?
> >
> > Thanks
> >
> > On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
> > philippe.mouawad@gmail.com>
> > wrote:
> >
> > >
> > >
> > > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
> > > sitnikov.vladimir@gmail.com> wrote:
> > >
> > >> Philippe>I would add those 2:
> > >> Philippe> - org.codehaus.groovy:groovy-templates :
> > >> Philippe>
> > >>
> > >>
> >
> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
> > >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
> > >>
> > >> The libraries were on my list as well:
> > >>
> > >
> > > indeed, not explicit enough for me :-)
> > >
> > >>
> > >> Vladimir> How about groovy,
> > >> Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
> > >> groovy-sql ?
> > >>
> > >> Philippe>Don't we also need:
> > >> Philippe>- org.codehaus.groovy:groovy-astbuilder
> > >>
> > >> I think the ones who can understand astbuilder are smart enough to add
> > the
> > >> relevant jars themselves :)
> > >> Of course, we could consider bundling the dependency if there's a use
> > >> case,
> > >> however,
> > >> I do not think there's a common use-case for doing AST transformations
> > >> inside JSR223 samplers.
> > >>
> > >> Vladimir
> > >>
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > >
> > >
> > >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi
i have tested JMeter-Plugins in the latest nightly build of JMeter in Linux
Ubuntu and it's ok (no more errors)
Le mer. 8 avr. 2020 à 17:17, Philippe Mouawad <ph...@gmail.com>
a écrit :
> Hello,
> JMeter-Plugins has been released. Can somebody else test if it's ok ?
>
> Thanks
>
> On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <
> philippe.mouawad@gmail.com>
> wrote:
>
> >
> >
> > On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
> > sitnikov.vladimir@gmail.com> wrote:
> >
> >> Philippe>I would add those 2:
> >> Philippe> - org.codehaus.groovy:groovy-templates :
> >> Philippe>
> >>
> >>
> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
> >> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
> >>
> >> The libraries were on my list as well:
> >>
> >
> > indeed, not explicit enough for me :-)
> >
> >>
> >> Vladimir> How about groovy,
> >> Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
> >> groovy-sql ?
> >>
> >> Philippe>Don't we also need:
> >> Philippe>- org.codehaus.groovy:groovy-astbuilder
> >>
> >> I think the ones who can understand astbuilder are smart enough to add
> the
> >> relevant jars themselves :)
> >> Of course, we could consider bundling the dependency if there's a use
> >> case,
> >> however,
> >> I do not think there's a common use-case for doing AST transformations
> >> inside JSR223 samplers.
> >>
> >> Vladimir
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> >
> >
> >
>
> --
> Cordialement.
> Philippe Mouawad.
>
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
JMeter-Plugins has been released. Can somebody else test if it's ok ?
Thanks
On Tue, Apr 7, 2020 at 8:46 PM Philippe Mouawad <ph...@gmail.com>
wrote:
>
>
> On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
>> Philippe>I would add those 2:
>> Philippe> - org.codehaus.groovy:groovy-templates :
>> Philippe>
>>
>> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
>> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>>
>> The libraries were on my list as well:
>>
>
> indeed, not explicit enough for me :-)
>
>>
>> Vladimir> How about groovy,
>> Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
>> groovy-sql ?
>>
>> Philippe>Don't we also need:
>> Philippe>- org.codehaus.groovy:groovy-astbuilder
>>
>> I think the ones who can understand astbuilder are smart enough to add the
>> relevant jars themselves :)
>> Of course, we could consider bundling the dependency if there's a use
>> case,
>> however,
>> I do not think there's a common use-case for doing AST transformations
>> inside JSR223 samplers.
>>
>> Vladimir
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
On Tue, Apr 7, 2020 at 8:37 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> Philippe>I would add those 2:
> Philippe> - org.codehaus.groovy:groovy-templates :
> Philippe>
>
> https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
> Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
>
> The libraries were on my list as well:
>
indeed, not explicit enough for me :-)
>
> Vladimir> How about groovy,
> Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
> groovy-sql ?
>
> Philippe>Don't we also need:
> Philippe>- org.codehaus.groovy:groovy-astbuilder
>
> I think the ones who can understand astbuilder are smart enough to add the
> relevant jars themselves :)
> Of course, we could consider bundling the dependency if there's a use case,
> however,
> I do not think there's a common use-case for doing AST transformations
> inside JSR223 samplers.
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
Philippe>I would add those 2:
Philippe> - org.codehaus.groovy:groovy-templates :
Philippe>
https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
Philippe> - org.codehaus.groovy:groovy-xml : XmlSlurper
The libraries were on my list as well:
Vladimir> How about groovy,
Vladimir> groovy-datetime, groovy-jmx, groovy-json, groovy-templates,
groovy-sql ?
Philippe>Don't we also need:
Philippe>- org.codehaus.groovy:groovy-astbuilder
I think the ones who can understand astbuilder are smart enough to add the
relevant jars themselves :)
Of course, we could consider bundling the dependency if there's a use case,
however,
I do not think there's a common use-case for doing AST transformations
inside JSR223 samplers.
Vladimir
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Thanks for analysis.
I would add those 2:
- org.codehaus.groovy:groovy-templates :
https://docs.groovy-lang.org/docs/next/html/documentation/template-engines.html
- org.codehaus.groovy:groovy-xml : XmlSlurper
I'm sure I've used them in tests I built.
Don't we also need:
- org.codehaus.groovy:groovy-astbuilder
Regards
On Tue, Apr 7, 2020 at 1:18 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> >Let's update to Groovy 3.
>
> I see that we currently use groovy-all dependency.
> Unfortunately, it is unpredictable, as it adds new transitive dependencies
> as Groovy evolves.
>
> I guess we need to specify which dependencies we include explicitly.
> How about groovy,
> groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql ?
>
> Here's dependency tree for groovy-all 2.4.18
> org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
>
> groovy 3.0.2 (2.5.10 is pretty much the same)
>
> org.codehaus.groovy:groovy-all -> 3.0.2
> +--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-ant:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.apache.ant:ant:1.10.7
> | | \--- org.apache.ant:ant-launcher:1.10.7
> | +--- org.apache.ant:ant-junit:1.10.7
> | | \--- org.apache.ant:ant:1.10.7 (*)
> | +--- org.apache.ant:ant-launcher:1.10.7
> | +--- org.apache.ant:ant-antlr:1.10.7
> | \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- com.github.javaparser:javaparser-core:3.15.13
> | +--- org.codehaus.groovy:groovy-templates:3.0.2
> | | +--- org.codehaus.groovy:groovy:3.0.2
> | | \--- org.codehaus.groovy:groovy-xml:3.0.2
> | | \--- org.codehaus.groovy:groovy:3.0.2
> | \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- com.thoughtworks.qdox:qdox:1.12.1
> +--- org.codehaus.groovy:groovy-astbuilder:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- info.picocli:picocli:4.1.4
> +--- org.codehaus.groovy:groovy-console:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | \--- org.codehaus.groovy:groovy-swing:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-datetime:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-groovysh:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
> | +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> | \--- jline:jline:2.14.6
> +--- org.codehaus.groovy:groovy-jmx:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-json:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-jsr223:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-macro:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-nio:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-servlet:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> | \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-sql:3.0.2
> | \--- org.codehaus.groovy:groovy:3.0.2
> +--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
> +--- org.codehaus.groovy:groovy-test:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- junit:junit:4.13
> | \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
> | \--- org.hamcrest:hamcrest:2.2
> +--- org.codehaus.groovy:groovy-test-junit5:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | +--- org.junit.platform:junit-platform-launcher:1.6.0
> | | +--- org.junit:junit-bom:5.6.0
> | | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
> | | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
> | | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
> | | | +--- org.junit.platform:junit-platform-launcher:1.6.0 (c)
> | | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
> | | \--- org.junit.platform:junit-platform-engine:1.6.0
> | | +--- org.junit:junit-bom:5.6.0 (*)
> | | +--- org.opentest4j:opentest4j:1.2.0
> | | \--- org.junit.platform:junit-platform-commons:1.6.0
> | | \--- org.junit:junit-bom:5.6.0 (*)
> | \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
> | +--- org.junit:junit-bom:5.6.0 (*)
> | +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
> | \--- org.junit.jupiter:junit-jupiter-api:5.6.0
> | +--- org.junit:junit-bom:5.6.0 (*)
> | +--- org.opentest4j:opentest4j:1.2.0
> | \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
> +--- org.codehaus.groovy:groovy-testng:3.0.2
> | +--- org.codehaus.groovy:groovy:3.0.2
> | \--- org.testng:testng:6.14.3
> | \--- com.beust:jcommander:1.72
> \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
>
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
>Let's update to Groovy 3.
I see that we currently use groovy-all dependency.
Unfortunately, it is unpredictable, as it adds new transitive dependencies
as Groovy evolves.
I guess we need to specify which dependencies we include explicitly.
How about groovy,
groovy-datetime, groovy-jmx, groovy-json, groovy-templates, groovy-sql ?
Here's dependency tree for groovy-all 2.4.18
org.codehaus.groovy:groovy-all -> 2.4.18 (no transitive dependencies)
groovy 3.0.2 (2.5.10 is pretty much the same)
org.codehaus.groovy:groovy-all -> 3.0.2
+--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-ant:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- org.apache.ant:ant:1.10.7
| | \--- org.apache.ant:ant-launcher:1.10.7
| +--- org.apache.ant:ant-junit:1.10.7
| | \--- org.apache.ant:ant:1.10.7 (*)
| +--- org.apache.ant:ant-launcher:1.10.7
| +--- org.apache.ant:ant-antlr:1.10.7
| \--- org.codehaus.groovy:groovy-groovydoc:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- com.github.javaparser:javaparser-core:3.15.13
| +--- org.codehaus.groovy:groovy-templates:3.0.2
| | +--- org.codehaus.groovy:groovy:3.0.2
| | \--- org.codehaus.groovy:groovy-xml:3.0.2
| | \--- org.codehaus.groovy:groovy:3.0.2
| \--- org.codehaus.groovy:groovy-docgenerator:3.0.2
| +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
| +--- org.codehaus.groovy:groovy:3.0.2
| \--- com.thoughtworks.qdox:qdox:1.12.1
+--- org.codehaus.groovy:groovy-astbuilder:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-cli-picocli:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| \--- info.picocli:picocli:4.1.4
+--- org.codehaus.groovy:groovy-console:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
| \--- org.codehaus.groovy:groovy-swing:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-datetime:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-docgenerator:3.0.2 (*)
+--- org.codehaus.groovy:groovy-groovydoc:3.0.2 (*)
+--- org.codehaus.groovy:groovy-groovysh:3.0.2
| +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- org.codehaus.groovy:groovy-console:3.0.2 (*)
| +--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
| \--- jline:jline:2.14.6
+--- org.codehaus.groovy:groovy-jmx:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-json:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-jsr223:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-macro:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-nio:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-servlet:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
| \--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
+--- org.codehaus.groovy:groovy-sql:3.0.2
| \--- org.codehaus.groovy:groovy:3.0.2
+--- org.codehaus.groovy:groovy-swing:3.0.2 (*)
+--- org.codehaus.groovy:groovy-templates:3.0.2 (*)
+--- org.codehaus.groovy:groovy-test:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| \--- junit:junit:4.13
| \--- org.hamcrest:hamcrest-core:1.3 -> 2.2
| \--- org.hamcrest:hamcrest:2.2
+--- org.codehaus.groovy:groovy-test-junit5:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| +--- org.junit.platform:junit-platform-launcher:1.6.0
| | +--- org.junit:junit-bom:5.6.0
| | | +--- org.junit.jupiter:junit-jupiter-api:5.6.0 (c)
| | | +--- org.junit.jupiter:junit-jupiter-engine:5.6.0 (c)
| | | +--- org.junit.platform:junit-platform-engine:1.6.0 (c)
| | | +--- org.junit.platform:junit-platform-launcher:1.6.0 (c)
| | | \--- org.junit.platform:junit-platform-commons:1.6.0 (c)
| | \--- org.junit.platform:junit-platform-engine:1.6.0
| | +--- org.junit:junit-bom:5.6.0 (*)
| | +--- org.opentest4j:opentest4j:1.2.0
| | \--- org.junit.platform:junit-platform-commons:1.6.0
| | \--- org.junit:junit-bom:5.6.0 (*)
| \--- org.junit.jupiter:junit-jupiter-engine:5.6.0
| +--- org.junit:junit-bom:5.6.0 (*)
| +--- org.junit.platform:junit-platform-engine:1.6.0 (*)
| \--- org.junit.jupiter:junit-jupiter-api:5.6.0
| +--- org.junit:junit-bom:5.6.0 (*)
| +--- org.opentest4j:opentest4j:1.2.0
| \--- org.junit.platform:junit-platform-commons:1.6.0 (*)
+--- org.codehaus.groovy:groovy-testng:3.0.2
| +--- org.codehaus.groovy:groovy:3.0.2
| \--- org.testng:testng:6.14.3
| \--- com.beust:jcommander:1.72
\--- org.codehaus.groovy:groovy-xml:3.0.2 (*)
Vladimir
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
>3) What about upgrade to groovy ? Do we skip it for this release ?
Let's update to Groovy 3.
>2) I upgraded some dependencies, but github is facing an incident so we
>didn't get the mail
Thanks.
I suggest we stop adding lines like "Updated equalsverifier to 3.1.9 (from
3.1.12)" to changes.xml.
The reasoning is as follows:
1) There are build-only dependencies, and there are runtime dependencies.
For instance, JMeter binary artifacts do not include equalsverifier jar.
What does "updated equalsverifier" tell the end-users?
2) It is hard to predict which transitive versions will be updated
That is why I think we should update version diff just before the release.
I'm not sure if we should add test-only dependencies update to changes.xml
If we add them, the changes should probably go into a dedicated section
(e.g. build/test changes).
Vladimir
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello ,
1) I submitted a PR for JMP
2) I upgraded some dependencies, but github is facing an incident so we
didn't get the mail
3) What about upgrade to groovy ? Do we skip it for this release ?
Thanks
On Thu, Apr 2, 2020 at 6:55 PM Felix Schumacher <
felix.schumacher@internetallee.de> wrote:
>
> Am 02.04.20 um 11:32 schrieb Vladimir Sitnikov:
> > Hi,
> >
> > It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
> >
> > How about we release JMeter 5.3?
>
> Apart from the objection from Philippe, I am fine with a release.
>
> Felix
>
> >
> > Vladimir
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 02.04.20 um 11:32 schrieb Vladimir Sitnikov:
> Hi,
>
> It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
>
> How about we release JMeter 5.3?
Apart from the objection from Philippe, I am fine with a release.
Felix
>
> Vladimir
>
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
>I didn't have opportunity to review it more deeply or test it on real life
>case.
Same for me :-(
>Should we request users to test it and give feedback ?
>I have seen 2 or 3 very interested.
My understanding is we have a chicken and egg problem here.
JMeter releases are very rare, so features wait in the queue for
extremely long amount of time.
That demotivates both end-users and developers.
At the same time, we don't release because, well, some of the features are
in progress.
Now we are at a point when Java releases are more frequent than JMeter
releases :-/
We should be able to release once every two or three months, then the
features are released when they are ready.
We should avoid delaying the release because a feature is still pending.
Vladimir
RE: Release 5.3
Posted by "IMOTO TAKASHI (井元 崇之)" <t-...@nec.com>.
To: Philippe-san and alexander-san.
Thank you for considering it.
> So an alternative is to merge it, mark it as alpha and release.
Yes. I agree to merge it as alpha release.
And thank you for test it.
And would you tell me process and remain task for release it ?
Thanks.
-----Original Message-----
From: Alexander Podelko <ap...@yahoo.com.INVALID>
Sent: Saturday, April 4, 2020 5:42 AM
To: dev@jmeter.apache.org
Subject: Re: Release 5.3
Yes, I am.
On Friday, April 3, 2020, 4:25:45 PM EDT, Philippe Mouawad <p....@ubik-ingenierie.com> wrote:
Kon'nichiwa IMOTO-san,
Thank you for your big contribution !
I see now that it does not alter any core class, so it is mergeable without impacts.
So an alternative is to merge it, mark it as alpha and release.
We would need volunteers to use it, @Alexander Podelko <ap...@yahoo.com> , would you be ready to test nightly build ?
Regards
Philippe M.
On Fri, Apr 3, 2020 at 9:55 PM IMOTO TAKASHI(井元 崇之) <t-...@nec.com> wrote:
> To: Alexander-san and Philippe-san.
>
> Thank you for considering merge our auto-correlation feature.
>
> To release and merged feature, we want to contribute.
> As you said, we have some remain task.
> So we have updated code and response comments.
>
> > There are pending remarks done on PR that have not been taken into
> account yet.
> > I didn't have opportunity to review it more deeply or test it on
> > real
> life case.
> We have fixed with community's review comments.
>
> > Yes, my concern is that it gets rather stale and doesn't get
> synchronized with JMeter code.
> > If there is other way to revive the project and improve it further
> before merging later - it definitely may be an option.
> We merged latest code.
>
> > Should we request users to test it and give feedback ?
> I'm waiting your test and feedback, so at release process, there are
> some issue we want to follow it.
>
> So can you consider merge this feature. If so we want to support it.
>
> Thanks.
>
> -----Original Message-----
> From: Alexander Podelko <ap...@yahoo.com.INVALID>
> Sent: Friday, April 3, 2020 12:52 AM
> To: ApacheJMeter dev list <de...@jmeter.apache.org>
> Subject: Re: Release 5.3
>
> My user view after trying it once:
> -Some correlation help functionality is needed-That functionality is
>complex and will never be perfect -That project definitely provides
>some correlation help -My understanding is that there is no other
>competing projects
>
> [I saw some other projects/proposals mentioned, but it appears that
> they are rather in the conception phase]
>
> -That functionality as implemented is pretty isolated and shouldn't
> interfere with other parts
>
> So my thought was that it may be merged so people start using it /
> keep it in sync.
>
> Yes, my concern is that it gets rather stale and doesn't get
> synchronized with JMeter code.
> If there is other way to revive the project and improve it further
> before merging later - it definitely may be an option.
>
> Thanks,Alex
>
> On Thursday, April 2, 2020, 11:28:06 AM EDT, Philippe Mouawad <
>philippe.mouawad@gmail.com> wrote:
>
> Hello,
> I don't think it is.
> There are pending remarks done on PR that have not been taken into
>account yet.
> I didn't have opportunity to review it more deeply or test it on real
>life case.
>
> Should we request users to test it and give feedback ?
>
> I have seen 2 or 3 very interested.
>
> Regards
>
> On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
> > Alexander> What about auto-correlation
> > https://github.com/apache/jmeter/pull/499 ?
> >
> > Do you think it is ready for merge as is?
> >
> > Vladimir
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
Re: Release 5.3
Posted by Alexander Podelko <ap...@yahoo.com.INVALID>.
Yes, I am.
On Friday, April 3, 2020, 4:25:45 PM EDT, Philippe Mouawad <p....@ubik-ingenierie.com> wrote:
Kon'nichiwa IMOTO-san,
Thank you for your big contribution !
I see now that it does not alter any core class, so it is mergeable without
impacts.
So an alternative is to merge it, mark it as alpha and release.
We would need volunteers to use it, @Alexander Podelko <ap...@yahoo.com>
, would you be ready to test nightly build ?
Regards
Philippe M.
On Fri, Apr 3, 2020 at 9:55 PM IMOTO TAKASHI(井元 崇之) <t-...@nec.com> wrote:
> To: Alexander-san and Philippe-san.
>
> Thank you for considering merge our auto-correlation feature.
>
> To release and merged feature, we want to contribute.
> As you said, we have some remain task.
> So we have updated code and response comments.
>
> > There are pending remarks done on PR that have not been taken into
> account yet.
> > I didn't have opportunity to review it more deeply or test it on real
> life case.
> We have fixed with community's review comments.
>
> > Yes, my concern is that it gets rather stale and doesn't get
> synchronized with JMeter code.
> > If there is other way to revive the project and improve it further
> before merging later - it definitely may be an option.
> We merged latest code.
>
> > Should we request users to test it and give feedback ?
> I'm waiting your test and feedback, so at release process, there are some
> issue we want to follow it.
>
> So can you consider merge this feature. If so we want to support it.
>
> Thanks.
>
> -----Original Message-----
> From: Alexander Podelko <ap...@yahoo.com.INVALID>
> Sent: Friday, April 3, 2020 12:52 AM
> To: ApacheJMeter dev list <de...@jmeter.apache.org>
> Subject: Re: Release 5.3
>
> My user view after trying it once:
> -Some correlation help functionality is needed-That functionality is
> complex and will never be perfect
> -That project definitely provides some correlation help
> -My understanding is that there is no other competing projects
>
> [I saw some other projects/proposals mentioned, but it appears that they
> are rather in the conception phase]
>
> -That functionality as implemented is pretty isolated and shouldn't
> interfere with other parts
>
> So my thought was that it may be merged so people start using it / keep it
> in sync.
>
> Yes, my concern is that it gets rather stale and doesn't get synchronized
> with JMeter code.
> If there is other way to revive the project and improve it further before
> merging later - it definitely may be an option.
>
> Thanks,Alex
>
> On Thursday, April 2, 2020, 11:28:06 AM EDT, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
> Hello,
> I don't think it is.
> There are pending remarks done on PR that have not been taken into account
> yet.
> I didn't have opportunity to review it more deeply or test it on real life
> case.
>
> Should we request users to test it and give feedback ?
>
> I have seen 2 or 3 very interested.
>
> Regards
>
> On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
> > Alexander> What about auto-correlation
> > https://github.com/apache/jmeter/pull/499 ?
> >
> > Do you think it is ready for merge as is?
> >
> > Vladimir
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
Re: Release 5.3
Posted by Philippe Mouawad <p....@ubik-ingenierie.com>.
Kon'nichiwa IMOTO-san,
Thank you for your big contribution !
I see now that it does not alter any core class, so it is mergeable without
impacts.
So an alternative is to merge it, mark it as alpha and release.
We would need volunteers to use it, @Alexander Podelko <ap...@yahoo.com>
, would you be ready to test nightly build ?
Regards
Philippe M.
On Fri, Apr 3, 2020 at 9:55 PM IMOTO TAKASHI(井元 崇之) <t-...@nec.com> wrote:
> To: Alexander-san and Philippe-san.
>
> Thank you for considering merge our auto-correlation feature.
>
> To release and merged feature, we want to contribute.
> As you said, we have some remain task.
> So we have updated code and response comments.
>
> > There are pending remarks done on PR that have not been taken into
> account yet.
> > I didn't have opportunity to review it more deeply or test it on real
> life case.
> We have fixed with community's review comments.
>
> > Yes, my concern is that it gets rather stale and doesn't get
> synchronized with JMeter code.
> > If there is other way to revive the project and improve it further
> before merging later - it definitely may be an option.
> We merged latest code.
>
> > Should we request users to test it and give feedback ?
> I'm waiting your test and feedback, so at release process, there are some
> issue we want to follow it.
>
> So can you consider merge this feature. If so we want to support it.
>
> Thanks.
>
> -----Original Message-----
> From: Alexander Podelko <ap...@yahoo.com.INVALID>
> Sent: Friday, April 3, 2020 12:52 AM
> To: ApacheJMeter dev list <de...@jmeter.apache.org>
> Subject: Re: Release 5.3
>
> My user view after trying it once:
> -Some correlation help functionality is needed-That functionality is
> complex and will never be perfect
> -That project definitely provides some correlation help
> -My understanding is that there is no other competing projects
>
> [I saw some other projects/proposals mentioned, but it appears that they
> are rather in the conception phase]
>
> -That functionality as implemented is pretty isolated and shouldn't
> interfere with other parts
>
> So my thought was that it may be merged so people start using it / keep it
> in sync.
>
> Yes, my concern is that it gets rather stale and doesn't get synchronized
> with JMeter code.
> If there is other way to revive the project and improve it further before
> merging later - it definitely may be an option.
>
> Thanks,Alex
>
> On Thursday, April 2, 2020, 11:28:06 AM EDT, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
> Hello,
> I don't think it is.
> There are pending remarks done on PR that have not been taken into account
> yet.
> I didn't have opportunity to review it more deeply or test it on real life
> case.
>
> Should we request users to test it and give feedback ?
>
> I have seen 2 or 3 very interested.
>
> Regards
>
> On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
> > Alexander> What about auto-correlation
> > https://github.com/apache/jmeter/pull/499 ?
> >
> > Do you think it is ready for merge as is?
> >
> > Vladimir
> >
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
RE: Release 5.3
Posted by "IMOTO TAKASHI (井元 崇之)" <t-...@nec.com>.
To: Alexander-san and Philippe-san.
Thank you for considering merge our auto-correlation feature.
To release and merged feature, we want to contribute.
As you said, we have some remain task.
So we have updated code and response comments.
> There are pending remarks done on PR that have not been taken into account yet.
> I didn't have opportunity to review it more deeply or test it on real life case.
We have fixed with community's review comments.
> Yes, my concern is that it gets rather stale and doesn't get synchronized with JMeter code.
> If there is other way to revive the project and improve it further before merging later - it definitely may be an option.
We merged latest code.
> Should we request users to test it and give feedback ?
I'm waiting your test and feedback, so at release process, there are some issue we want to follow it.
So can you consider merge this feature. If so we want to support it.
Thanks.
-----Original Message-----
From: Alexander Podelko <ap...@yahoo.com.INVALID>
Sent: Friday, April 3, 2020 12:52 AM
To: ApacheJMeter dev list <de...@jmeter.apache.org>
Subject: Re: Release 5.3
My user view after trying it once:
-Some correlation help functionality is needed-That functionality is complex and will never be perfect
-That project definitely provides some correlation help
-My understanding is that there is no other competing projects
[I saw some other projects/proposals mentioned, but it appears that they are rather in the conception phase]
-That functionality as implemented is pretty isolated and shouldn't interfere with other parts
So my thought was that it may be merged so people start using it / keep it in sync.
Yes, my concern is that it gets rather stale and doesn't get synchronized with JMeter code.
If there is other way to revive the project and improve it further before merging later - it definitely may be an option.
Thanks,Alex
On Thursday, April 2, 2020, 11:28:06 AM EDT, Philippe Mouawad <ph...@gmail.com> wrote:
Hello,
I don't think it is.
There are pending remarks done on PR that have not been taken into account yet.
I didn't have opportunity to review it more deeply or test it on real life case.
Should we request users to test it and give feedback ?
I have seen 2 or 3 very interested.
Regards
On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov < sitnikov.vladimir@gmail.com> wrote:
> Alexander> What about auto-correlation
> https://github.com/apache/jmeter/pull/499 ?
>
> Do you think it is ready for merge as is?
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Alexander Podelko <ap...@yahoo.com.INVALID>.
My user view after trying it once:
-Some correlation help functionality is needed-That functionality is complex and will never be perfect
-That project definitely provides some correlation help-My understanding is that there is no other competing projects [I saw some other projects/proposals mentioned, but it appears that they are rather in the conception phase]-That functionality as implemented is pretty isolated and shouldn't interfere with other parts
So my thought was that it may be merged so people start using it / keep it in sync.
Yes, my concern is that it gets rather stale and doesn't get synchronized with JMeter code. If there is other way to revive the project and improve it further before merging later - it definitely may be an option.
Thanks,Alex
On Thursday, April 2, 2020, 11:28:06 AM EDT, Philippe Mouawad <ph...@gmail.com> wrote:
Hello,
I don't think it is.
There are pending remarks done on PR that have not been taken into account
yet.
I didn't have opportunity to review it more deeply or test it on real life
case.
Should we request users to test it and give feedback ?
I have seen 2 or 3 very interested.
Regards
On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> Alexander> What about auto-correlation
> https://github.com/apache/jmeter/pull/499 ?
>
> Do you think it is ready for merge as is?
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I don't think it is.
There are pending remarks done on PR that have not been taken into account
yet.
I didn't have opportunity to review it more deeply or test it on real life
case.
Should we request users to test it and give feedback ?
I have seen 2 or 3 very interested.
Regards
On Thu, Apr 2, 2020 at 5:24 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> Alexander> What about auto-correlation
> https://github.com/apache/jmeter/pull/499 ?
>
> Do you think it is ready for merge as is?
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
Alexander> What about auto-correlation
https://github.com/apache/jmeter/pull/499 ?
Do you think it is ready for merge as is?
Vladimir
Re: Release 5.3
Posted by Alexander Podelko <ap...@yahoo.com.INVALID>.
What about auto-correlation https://github.com/apache/jmeter/pull/499 ?
On Thursday, April 2, 2020, 5:55:11 AM EDT, Philippe Mouawad <ph...@gmail.com> wrote:
Hello
I didn't have time yet to contribute a fix to jmeter-plugins-manager
Regards
On Thu, Apr 2, 2020 at 11:48 AM Antonio Gomes Rodrigues <ra...@gmail.com>
wrote:
> Hi,
>
> +1 if the work about improve UX is done
>
>
> Le jeu. 2 avr. 2020 à 11:32, Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com>
> a écrit :
>
> > Hi,
> >
> > It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
> >
> > How about we release JMeter 5.3?
> >
> > Vladimir
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello
I didn't have time yet to contribute a fix to jmeter-plugins-manager
Regards
On Thu, Apr 2, 2020 at 11:48 AM Antonio Gomes Rodrigues <ra...@gmail.com>
wrote:
> Hi,
>
> +1 if the work about improve UX is done
>
>
> Le jeu. 2 avr. 2020 à 11:32, Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com>
> a écrit :
>
> > Hi,
> >
> > It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
> >
> > How about we release JMeter 5.3?
> >
> > Vladimir
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Release 5.3
Posted by Vladimir Sitnikov <si...@gmail.com>.
>if the work about improve UX is done
There's always room for UX, however, the further improvements might come
with upcoming versions.
For instance, upcoming Darklaf would have high contrast theme, and it would
support OS notifications for UI preferences (e.g. switch JMeter between
light-dark as OS theme changes)
Vladimir
Re: Release 5.3
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi,
+1 if the work about improve UX is done
Le jeu. 2 avr. 2020 à 11:32, Vladimir Sitnikov <si...@gmail.com>
a écrit :
> Hi,
>
> It's been a long since JMeter 5.2.1, so I guess 5.3 is long overdue.
>
> How about we release JMeter 5.3?
>
> Vladimir
>