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
Currently, the authority lookup goes to Sympony/Oracle, and the java code in this project goes to a maven repo to get the Oracle specific artifact containing the java classes that allow the authority lookup. Said maven repo (with the Oracle artifact) requires an oracle username and password. We have been using individual developer usernames and passwords ... but this isn't going to be okay outside of a dev environment.
We also use individual developer username and password on travis, which also isn't okay.
Thoughts:
stop using maven repos and put all the needed jars in the project (still use maven to compile, but not to grab remote artifacts)
as above, but switch to gradle or ant
note that we can still do code coverage reports and use coveralls
get some sort of official group account for oracle repo
The text was updated successfully, but these errors were encountered:
Currently, the authority lookup goes to Sympony/Oracle, and the java code in this project goes to a maven repo to get the Oracle specific artifact containing the java classes that allow the authority lookup. Said maven repo (with the Oracle artifact) requires an oracle username and password. We have been using individual developer usernames and passwords ... but this isn't going to be okay outside of a dev environment.
We also use individual developer username and password on travis, which also isn't okay.
Thoughts:
The text was updated successfully, but these errors were encountered: