Publish to Central Repository

[tilln]

Hi @sgoeschl

Would you consider publishing to the Maven Central Repository?

I have been looking for a usable JTL parser i.e. XSLT replacement for a while and just come across this which seems to fill that gap exactly.

If the JMeter project does not want to adopt it then making it available as a Maven artifact may be the next best solution?

Thanks!

[sgoeschl]

Hi Till, I will have a look at it in a couple of weeks - for know I'm drowning in work due to ISO-8583 message processing :-)

[tilln]

Hi Siegfried,

I've been doing ISO-8583 for the last two years so I know how much fun you're having ;-)

[sgoeschl]

It would be more fun if I would have two years of experience under my belt :(

[tilln]

Well, happy to help. I've been getting my head around the jPOS framework if you happen to use that.
Though mainly for testing purposes (functional and performance).

[sgoeschl]

Release 1.0.5 so the latest and greatest stuff is on the "master" branch - please note that man class changed from org.apache.jmeter.extra.report.sla.Main to com.github.sgoeschl.jmeter.report.sla.Main

I prepared the Maven project for an upload to Maven Central but I need to read through current process - but still some progress :)

[sgoeschl]

@tilln Could you have a look at https://github.com/sgoeschl/jmeter-sla-report/tree/ISSUE-11

• That version would be published as 1.0.6
• Please note I changed Maven package id to com.github.sgoeschl.jmeter to be consistent with my other lonely artefact
• Could you give it test and report any issues? Should be fixed before publishing ...

[tilln]

@sgoeschl I'm going to need some more time to do this, as I've found a couple of oddities, e.g. around error samples, which I'll report as separate issues.

[sgoeschl]

@tilln Any findings on your side? The oddities might be implementation decisions from my side :)

[tilln]

Sorry about the long delay. I just remembered that there was some outstanding issue here :)

When trying to process a results file with nothing but errors you'd get an ArrayIndexOutOfBoundsException in writeKiloBytesReceivedDetailTable when trying to sort the rawData, apparently because the kiloBytesReceivedMonitorProvider never got any data.
I had tried to fix this by collecting bytesReceived on failures too, but that seems to have other side effects as it breaks some unit tests (the failure would be reported twice). I haven't yet looked into it further unfortunately.

[sgoeschl]

Guess I need to fix my code :)

…

On 22.09.2021, at 04:04, Till Neunast ***@***.***> wrote: Sorry about the long delay. I just remembered that there was some outstanding issue here :) When trying to process a results file with nothing but errors you'd get an ArrayIndexOutOfBoundsException in writeKiloBytesReceivedDetailTable when trying to sort the rawData, apparently because the kiloBytesReceivedMonitorProvider never got any data. I had tried to fix this by collecting bytesReceived on failures too, but that seems to have other side effects as it breaks some unit tests (the failure would be reported twice). I haven't yet looked into it further unfortunately. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABR6IDDQT2BARDMHAV3E4DUDE2RTANCNFSM4Z6OVE7Q>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.