-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to pull "qaf-support" through maven dependency #4
Comments
you should be able to resolve 2.1.11. Are you inside VPN? |
Hi,
Yes, I’m connected to My organization VPN.
I did tried 2.1.11, but let me try again. Thanks much for your response!
Thanks,
…On Fri, Dec 15, 2017 at 12:58 AM cjayswal ***@***.***> wrote:
you should be able to resolve 2.1.11
<https://qmetry.github.io/qaf/dist/com/qmetry/qaf-support/2.1.11/>. Are
you inside VPN?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ag9XqKvIGmxTQZ42wRvozAqvWEnUz_99ks5tAgqLgaJpZM4RC7ej>
.
|
i try to pull 2.1.11 version, it didn't work either.. Can you please help me to solve this? |
can you provide error message? |
eclipse.buildId=4.6.2.M20161124-1400 org.eclipse.m2e.logback.appender |
It looks like warning and you can ignore it. It may be because of in your company local repository it's not upload with dependency information. You should be able to run with warning. If you are not able to run then you should provide above location to your system admin to mirror |
Its actually an error which prevents the maven to build the project... So I have commented the dependency in pom and downloaded the qaf-support-2.1.11.jar and added to build path... |
You should be able to resolve 2.1.12 as it is deployed in maven central. |
Hi,
I'm unable to get the "qaf-support" jars through maven dependency.
Tried multiple versions 2.1.11, 2.1.8. Any help to resolve this issue is much appreciated..
The text was updated successfully, but these errors were encountered: