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
It looks like the pom.xml and license files were removed at some point during the last few commits/releases.
Any chance these could be added back? The pom.xml file specifically is an impediment to getting started since it contains the dependencies needed to compile/run the SDK. The project readme even mentions Maven, so it is confusing for the project to not have a pom.
As a temporary workaround, I plan on checking out the pom.xml for the most-recent commit that included it in the project.
The text was updated successfully, but these errors were encountered:
It might also be useful to add a section to the README to get the SDK as a maven JAR. I just found it at maven central (after looking at the pom file to get the artifact id.)
HI Kyle,
That is the intended usage, for the SDK to added through Maven. We will
update the README to specify more clearly how to add the SDK to your
project through Maven.
Thanks,
Russell
On Fri, Jan 27, 2017 at 12:20 PM, Kyle ***@***.***> wrote:
It might also be useful to add a section to the README to get the SDK as a
maven JAR. I just found it at maven central (after looking at the pom file
to get the artifact id.)
com.heartlandpaymentsystems secure-submit v2.0.11
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEwP9SBvz53lzM2hw-a61cOZN1UCQZUlks5rWidYgaJpZM4Lv-bl>
.
It looks like the pom.xml and license files were removed at some point during the last few commits/releases.
Any chance these could be added back? The pom.xml file specifically is an impediment to getting started since it contains the dependencies needed to compile/run the SDK. The project readme even mentions Maven, so it is confusing for the project to not have a pom.
As a temporary workaround, I plan on checking out the pom.xml for the most-recent commit that included it in the project.
The text was updated successfully, but these errors were encountered: