[FIXED] Artifactory repo has bad path for artifact, any way to fix path request?

Issue

Recently my company blocked requests to outside repositories, and an artifact that is required by a component of my project is available only on one repo where it is incorrectly set up.

The path requested is:

/reponame/com/group/name/artifact-name/1.0.0.pom

But it is found in the company repository here:

/reponame/com.group.name/artifact-name/1.0.0.pom

Other outside repositories I have seen have it in the former path.

Is there a way to have my project request the latter path instead, some other way around? I don't have the artifact requirement in my project, it's a dependency of a dependency requirement I have.

I have tried to get help from the artifactory admins but they are completely slammed, stating I won't have a solution for a couple weeks (I need it faster than that).

Solution

It seems that the best path is for me to install my own maven repo on my laptop so I don't get stopped when my company's artifactory support is lacking.

Answered By - Jim Gough
Answer Checked By - Marilyn (JavaFixing Volunteer)