cancel
Showing results for 
Search instead for 
Did you mean: 

Maven Install Authentication Error

ronmwhite
New Contributor II

Hello. Trying to do some development and cant seem to get out of the gates. I have tried this on multiple networks so it does not appear to be network related.

When run “mvn clean install” in my newly created workspace, after successfully running “mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=http://maven.clouddev.snaplogic.com:8080/nexus/content/repositories/master

I get the following error.

Failed to read artifact descriptor for com.snaplogic:jutils:jar:4.22: Could not transfer artifact com.snaplogic:jutils:pom:4.22 from/to github (https://maven.pkg.github.com/SnapLogic/Tectonic😞 Authentication failed for https://maven.pkg.github.com/SnapLogic/Tectonic/com/snaplogic/jutils/4.22/jutils-4.22.pom 401 Unauthorized

Thoughts?

19 REPLIES 19

robin
Former Employee

Hi @ronmwhite, yes we are aware of this and are preparing a fix. Unfortunately GitHub public packages still require authentication to download artifacts. We’ll have an update out soon with a corrective action.

ptaylor
Employee
Employee

Hi @ronmwhite. When did you create your new project using the archetype? The 4.22 version of the archetype was just deployed yesterday. Do you recall whether you selected the 4.22 version of the archetype? Did you change anything else in the pom.xml that was created by the archetype?

If you used the 4.22 version of the archetype, and didn’t modify anything of significance in the pom.xml, please capture and share the exact command that you’re using to build and the output of that build.

ronmwhite
New Contributor II

Yes, I used the archetype and version 4.22 at that. Sorry, I already shared the commands in my original post - not sure what your looking for @ptaylor .

Note I am using the latest download of Maven and running directly from the terminal on my Mac. Per @robin this is a know issue but if you have a workaround please do share.

I think Robin was unaware that I had already updated and deployed the 4.22 Maven archetype.

I meant the command you used to build the project, not the command you used to clone the archetype. Was it just a ‘mvn clean install’ or similar? What I’m more interested in is the full output of that build. Can you please try ‘mvn clean install | tee build.out’ and then post build.out here?

You might first try temporarily using a clean local maven repo cache by doing this:

cd ~/.m2/
mv repository repository.save
mkdir repository

Then try your build.