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
Hi guys,
We use google code wicked-charts-wicket7 for long time.
Now we want to upgrade to latest, so found new version in adesso wicked-charts-wicket8
But I couldn't use this as maven dependency, it is not found there.
I tried adding jcenter repository in maven setting.xml, it didn't work
Finally I was trying to download jar file for this dependency from https://oss.jfrog.org/artifactory/jcenter/. It asks credentials
I tried with default credentials admin/password, it didn't work.
Could you help us to sort out the problem?
Yes, it is available in jCenter
but wicked-charts-wicket8 is not resolved in maven project even after configuring the repository in maven setting.xml
I couldn't even download it manually.
Please correct me If I did any mistake.
Yes, you are correct and jCenter asks for credentials. This apparently has to do with the shutdown of jCenter. According to jfrog however, the repository should be available as read-only indefinetly, so I don't know exactly what credentials it needs either. Until the library is migrated to maven central, the only way to download it is through the GitHub releases, which is quite inconvenient. I will attempt to find out if jCenter can still be used.
Hi guys,
We use google code wicked-charts-wicket7 for long time.
Now we want to upgrade to latest, so found new version in adesso wicked-charts-wicket8
But I couldn't use this as maven dependency, it is not found there.
I tried adding jcenter repository in maven setting.xml, it didn't work
Finally I was trying to download jar file for this dependency from https://oss.jfrog.org/artifactory/jcenter/. It asks credentials
I tried with default credentials admin/password, it didn't work.
Could you help us to sort out the problem?
Development environment:
Java
Maven
Spring
Wicket
Highcharts
The text was updated successfully, but these errors were encountered: