Forum Discussion
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.
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.
- ptaylor6 years agoEmployee
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 repositoryThen try your build.
- ronmwhite6 years agoNew Contributor II
I tried that yesterday (removing the repository) - trying again at this time. I will post the build.out.