You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for creating a great library. I've been comparing many others and yours offer the best fit to our needs.
The JAR file contains very old version of slf4j which creates a problem when importing to our project. I understand that the distributed JAR file might be an uber jar for CLI purposes.
Ideally there would be 2 JARs to distribute:
One uber JAR for CLI
One lib JAR which doesn't have any slf4j included, instead, has slf4j as dependency in pom.xml
The text was updated successfully, but these errors were encountered:
Hi Trung Nguyễn,
Thanks for the feedback. I am glad you have found the library to be useful for your needs.
You are certainly right. The JAR file available via GitHub is quite old in several regards and is need of updating. We have been adding new features and improvements to the full EDI framework (the free EDI-to-JSON tool at GitHub is a thin subset of that) and are recently in the process of providing certain functions, such as EDI-to-JSON with loop awareness for any X12 or EDIFACT document type, and JSON-to-EDI (referred to as the EDI-JSON Premium Edition at GitHub) runnable as a CLI tool with a renewable runtime license. And our intent is to continue to provide a free EDI-to-JSON tool, like the one currently at GitHub except updated along the lines you suggest; we don’t have a timeline for that but will look to expedite it based on your request.
Feel free to contact us directly at the email addresses above for more information.
Thanks,
Scott
On Apr 10, 2024, at 3:38 PM, ⚆ Trung Nguyen ***@***.***> wrote:
First of all, thanks for creating a great library. I've been comparing many others and yours offer the best fit to our needs.
The JAR file contains very old version of slf4j which creates a problem when importing to our project. I understand that the distributed JAR file might be an uber jar for CLI purposes.
Ideally there would be 2 JARs to distribute:
One uber JAR for CLI
One lib JAR which doesn't have any slf4j included, instead, has slf4j as dependency in pom.xml
—
Reply to this email directly, view it on GitHub <#19>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQDKPBPSPQBGO67MHECA4LY4WPNRAVCNFSM6AAAAABGBDOGWCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTMMZYHE2TIMQ>.
You are receiving this because you are subscribed to this thread.
First of all, thanks for creating a great library. I've been comparing many others and yours offer the best fit to our needs.
The JAR file contains very old version of slf4j which creates a problem when importing to our project. I understand that the distributed JAR file might be an uber jar for CLI purposes.
Ideally there would be 2 JARs to distribute:
pom.xml
The text was updated successfully, but these errors were encountered: