Related
I am new to maven and am experiencing difficulties while trying to mavenise a Java project.
Setting:
IDE: Eclipse Oxygen.2 Release (4.7.2)
Java: 8
m2e: 1.8.2
What I did:
- copy-pasted the entire original java project and renamed it
- right-click in eclipse: Configure > Convert to Maven project
- in java build path, deletion of libraries import from original local lib repo. The build path shows the Maven Dependencies folder, with the only junit library.
- maven install => downloaded things in the user/.m2/repository/, but not all.
What does not work:
When I try to add a dependency right from a file:
,
nothing pops up in the artifact selection windows, even though there is a commons-logging/ folder in m2/repository
When I try to add the dependency manually in the pom.xml:
<dependency>
<groupId>org.kie.modules</groupId>
<artifactId>org-apache-commons-configuration-main</artifactId>
<version>6.5.0.Final</version>
<type>pom</type>
</dependency>
but the package resolution error still appears in the java file, and I get this warning after Maven install
`[WARNING] The POM for org.kie.modules:org-apache-commons-configuration-main:pom:6.5.0.Final is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details`
I did Maven Update project, eclipse project clean, nothing changes.
My goal for now is just that eclipse understands (at least for one library), that it has to take it from maven repository. I still have many other dependencies to solve (intra-project), but that will be the next step.
Thanks for your help.
The cause of the issue is stated in the warning message :
[WARNING] The POM for
org.kie.modules:org-apache-commons-configuration-main:pom:6.5.0.Final
is invalid, transitive dependencies (if any) will not be available,
enable debug logging for more details
It means that the pom.xml downloaded in your local maven repository exists but is not valid.
Delete the folder of the dependency downloaded in your local maven repository and try again.
If you still have the same problem, check that your central repository that provides the dependency provides also correctly the pom.xml for that.
You can do it by browsing the directory of the dependency from a web browser.
For example we can see that the maven central repository provides a valid pom :
http://central.maven.org/maven2/org/kie/modules/org-apache-commons-collections-main/6.5.0.Final/org-apache-commons-collections-main-6.5.0.Final.pom
I have created a JBoss Fuse Camel integration project and I can deploy it as a Profile on the Karaf Server using fabric8:deploy. The project is running fine so far.
Now I want to create a new Profile to do some other tasks. In oder to avoid double code, I wanted to create a Commons Project and add common code into this. But i cannot figure out how to add the dependency so that fabric8:deploy will still work and also deploy the commons library on BOTH profiles.
How should I add the commons project to both projects pom.xml?
I tried to add it as a normal dependency:
<dependency>
<groupId>com.my.project</groupId>
<artifactId>common-tools</artifactId>
<version>1.0.0</version>
</dependency>
but i'm getting this error when i want to deploy it via fabric8:deploy:
The POM for com.my.project:common-tools:jar:1.0.0 is missing, no dependency information available
and
Failed to execute goal on project inbound: Could not resolve dependencies for project com.my.project:inbound:bundle:1.0.1-SNAPSHOT: Failure to find com.my.project:common-tools:jar:1.0.0 in https://maven.repository.redhat.com/ga was cached in the local repository, resolution will not be reattempted until the update interval of red-hat-ga-repository has elapsed or updates are forced -> [Help 1]
The message indicates that your common-tools project could not be found in the maven repositories. Do you have it in your local maven repo? Have you done a:
mvn clean install
for the common-tools project?
My project which uses Dataflow compiles just fine using
mvn compile
However when I import my project into eclipse, eclipse is unable to build the project and gives the following error
The project was not built since its build path is incomplete.
Cannot find the class file for com.google.common.reflect.TypeToken.
Fix the build path then try building this project
Adding an explicit dependency on Guava to my pom file appears to have fixed the problem.
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>[18.0,)</version>
</dependency>
By running
mvn dependency:tree -Dverbose -Dincludes=com.google.guava
I learned that I had several dependencies that were pulling in Guava so by adding an explicit dependency I was able to force maven to pull in a newer version.
However, I don't know why running 'mvn compile' on the command line worked.
I am trying to set up a project using Maven (m2eclipse), but I get this error in Eclipse:
Description Resource Path Location Type
Could not calculate build plan: Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom:2.0.2 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-compiler-plugin:pom:2.0.2 from/to central (http://repo1.maven.org/maven2): No response received after 60000 ExampleProject Unknown Maven Problem
Any ideas?
It would be helpful if you could show me how to check if everything is configured fine...
Remove all your failed downloads:
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;
For windows:
cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i
Then rightclick on your project in eclipse and choose Maven->"Update Project ...", make sure "Update Dependencies" is checked in the resulting dialog and click OK.
This worked for me in Windows as well.
Locate the {user}/.m2/repository (Using Juno /Win7 here)
In the Search field in upper right of window, type ".lastupdated". Windows will look through all subfolders for these files in the directory. (I did not look through cache.)
Remove them by Right-click > Delete (I kept all of the lastupdated.properties).
Then go back into Eclipse, Right-click on the project and select Maven > Update Project. I selected to "Force Update of Snapshots/Releases". Click Ok and the dependencies finally resolved correctly.
In Eclipse:
Right click the project->Maven->Update Project->Check checkbox "Force Update of Snapshots/Releases". Click OK.
Thanks for the replies, but after some more searching I was able to fix the problem. It turned out that I had to remove one of the "*.lastUpdated" which was preventing one of my plugins (Maven Surefire Plugin) from updating. I did this manually, because a maven clean wasn't doing it apparently.
The problem was that the "*.lastUpdated" file for a plugin was blocking the maven check for updates and not allowing a necessary jar to get downloaded.
Try to execute
mvn -U clean
or Run > Maven Clean and Maven > Update snapshots from project context menu in eclipse
In my case. The issues is same reason. I see the problem is on proxy and firewall.
Here my solution
Fisrt ways: 1. install Proxy for Maven and Eclipse 2. Go to Locate the {user}/.m2/repository and Remove all the *.lastupdated files 3. Go back into Eclipse, Right-click on the project and select Maven > Update Project. > Select "Force Update of Snapshots/Releases".
If the project is still exist error. example: here is my issues after all above step
Failure to transfer org.apache.maven:maven-archiver:pom:2.5 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven:maven-archiver:pom:2.5 from/to central (https://repo.maven.apache.org/maven2): Connect timed out
I use this solution useful for me:
1. Find repository in https://mvnrepository.com/ 2. Copy dependency to my *.poml of project example
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.5</version>
</dependency>
3. Build project. the dependency missing will be downloaded to local repository.
4. Go back into Eclipse, Right-click on the project and select Maven > Update Project. > Select "Force Update of Snapshots/Releases". =>> Error is resolved 5. I remove dependencies at step 2 after finished and resolved.
Done
This worked for me in Windows:
Locate the {user}/.m2/repository
In the Search field in upper right of window, type ".lastupdated". Windows will look through all subfolders for these files in the directory.
Remove all the .lastupdated files.
Go back into Eclipse, Right-click on the project and select Maven > Update Project.
Select "Force Update of Snapshots/Releases".
Click Ok and the dependencies will finally resolve correctly.
It happened to me as Iam behind a firewall. The dependencies doesn't get downloaded sometimes when you are running in Eclipse IDE. Make sure you use mvn clean install -U to resolve the problem. You would see the dependencies download after this.
If you are behind a proxy, you have to update the settings.xml file (under the conf folder of your MAVEN_HOME, the file itself contains information about the proxy settings) and additionally you may need to update your Eclipse Network Settings (Window->Preferences...-> type Network Connections).
Try using -X or --debug in order to get the debug output, this could provide additional information about the problem.
I had similar issue in Eclipse 3.6 with m2eclipse.
Could not calculate build plan: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 from central (http://repo1.maven.org/maven2): ConnectException project1 Unknown Maven Problem
Deleting all maven*.lastUpdated files from my local reository (as Deepak Joy suggested) solved that problem.
I had a similar issue with only a few projects in my workspace. Other projects with nearly identical POMs didn't have an error at all. None of the other answers listed fixed my problem. I finally stumbled upon removing/re-applying the Maven nature for each project and the errors disappeared:
For each project that has a pom with the "resolution will not be reattempted..." error:
Right-click on the project in Eclipse and select Maven->Disable Maven Nature
Right-click on the project in Eclipse and select Configure->Convert to Maven Project
It Happened to me also you may have two solue=tion for this
If your project consist of some external or project specificdependency in it then you have to manually add it to your M2 repo folder which is located at C:\Users\Mohit.Singh.m2\repository folder and then you have to run
mvn eclipse:eclipse and then
mvn clean install from the project folder
if you do not have any wxternal or project sppecific dependency then you may import the project into eclipse as Existing maven project
then right click on project --> GO to maven --> Click on update project
a window will appear check the force snapshot download option and hit on OK
Give correct maven setting.xml path in eclipse.
Windows --> Preference --> Maven --> User Settings
Enter correct setting.xml path in user settings text box
just delete the archetype in maven local repository. As said above, it happens in case of failed archetype downloads.
For me I just added the bellow xml code in the POM.xml file. And after I dit **right click in the project -> Maven -> Update Project and I checked Force Update of Snapshots/Releases ** and every thing worked
<dependencies>
<!-- https://mvnrepository.com/artifact/javax.servlet/javax.servlet-api -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.1.0</version>
</dependency>
<!-- https://mvnrepository.com/artifact/javax.servlet.jsp/jsp-api -->
<dependency>
<groupId>javax.servlet.jsp</groupId>
<artifactId>jsp-api</artifactId>
<version>2.1</version>
</dependency>
<!-- https://mvnrepository.com/artifact/jstl/jstl -->
<dependency>
<groupId>jstl</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.5.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
settings.xml for proxy?
and in eclipse there are maven global\local profile, add the settings.xml
You could delete the .m2 folder itself and force MyEclipse to re-download all dependencies on startup. Go to Window > Preferences > MyEclipse > Maven4MyEclipse.
Above Error occured due to removing of 'maven-compiler-plugin 2.0.2'
from maven repository.
For me, Above error gets resolved when I downgrade 'maven-compiler-plugin' to version to either 2.0 or 2.0.1.
for mac
I removed all the old failed downloads of maven there were several versions of maven also on my mac
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} ; -print -exec rm {} ;
after that, I simply updated my eclipse by
help -> check for updates
and the problem resolved for me
the main reason for this problem is the failed old updates does not allow you to download archetype so if you try to build project in any archetype of maven it gets failed
create a file delete_lastUpdated_and_remote.sh(use \n):
#!/bin/bash
find $(cd $(dirname $0); pwd) -name "*.lastUpdated" -type f -print -exec rm -rf {} \;
find $(cd $(dirname $0); pwd) -name "_remote.repositories" -type f -print -exec rm -rf {} \;
Put it in the local Maven repo, such as %userprofile%\.m2\repository or ~/.m2/repository, and run it.
In windows, you should install Git to run sh file also.
I also use it in jenkins job.
I got this error for the plugin below:
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>2.5</version>
I modified tag version to:
<version>2.5.0</version>
Then open Context menu on your project in eclipse and choose Maven > "Update Project ...", make sure "Update Dependencies" is checked in the dialog box and hit "OK" button.
In my case, I got this error message in spring tool 4
ArtifactTransferException: org.codehaus.plexus:plexus-interpolation:jar:1.26 failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.plexus:plexus-interpolation:jar:1.26 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org java.lang.reflect.InvocationTargetException
Here is the solution
step 01 - first close the spring tool Application
step 02 - go to path C:\Users\User and Delete .m2 folder
step 03 - Now go to package Explore and select your project
step 04 - Now Right Click on your project and go to the Maven and click Update Project
How to uninstall Spring Tool 4
step 01 - click on Help and Go to the About Spring Tool Suite 4
step 02 - Now click on Installation Details
step 03 - inside of that you can see the all Installed Software, simply press Ctrl + A to select all and click Uninstall
The solution that work for me is the following:
Copy the dependency to pom.
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.5</version>
</dependency>
Click right on your project
Select Maven
Select Update project
Select Force Update of Snapshots/Releases
Remove all files inside repository.
Go to C:\Users\DELL.m2\repository, select all the files and delete it.
Then go to project, right click maven update project (Alt+F5). It will download all the dependent files inside repository.
Please Make sure that settings.XML file in the folder .m2 is valid first
Then after clean the repository using below command in cmd
cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i
I am trying to set up a project using Maven (m2eclipse), but I get this error in Eclipse:
Description Resource Path Location Type
Could not calculate build plan: Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom:2.0.2 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-compiler-plugin:pom:2.0.2 from/to central (http://repo1.maven.org/maven2): No response received after 60000 ExampleProject Unknown Maven Problem
Any ideas?
It would be helpful if you could show me how to check if everything is configured fine...
Remove all your failed downloads:
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;
For windows:
cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i
Then rightclick on your project in eclipse and choose Maven->"Update Project ...", make sure "Update Dependencies" is checked in the resulting dialog and click OK.
This worked for me in Windows as well.
Locate the {user}/.m2/repository (Using Juno /Win7 here)
In the Search field in upper right of window, type ".lastupdated". Windows will look through all subfolders for these files in the directory. (I did not look through cache.)
Remove them by Right-click > Delete (I kept all of the lastupdated.properties).
Then go back into Eclipse, Right-click on the project and select Maven > Update Project. I selected to "Force Update of Snapshots/Releases". Click Ok and the dependencies finally resolved correctly.
In Eclipse:
Right click the project->Maven->Update Project->Check checkbox "Force Update of Snapshots/Releases". Click OK.
Thanks for the replies, but after some more searching I was able to fix the problem. It turned out that I had to remove one of the "*.lastUpdated" which was preventing one of my plugins (Maven Surefire Plugin) from updating. I did this manually, because a maven clean wasn't doing it apparently.
The problem was that the "*.lastUpdated" file for a plugin was blocking the maven check for updates and not allowing a necessary jar to get downloaded.
Try to execute
mvn -U clean
or Run > Maven Clean and Maven > Update snapshots from project context menu in eclipse
In my case. The issues is same reason. I see the problem is on proxy and firewall.
Here my solution
Fisrt ways: 1. install Proxy for Maven and Eclipse 2. Go to Locate the {user}/.m2/repository and Remove all the *.lastupdated files 3. Go back into Eclipse, Right-click on the project and select Maven > Update Project. > Select "Force Update of Snapshots/Releases".
If the project is still exist error. example: here is my issues after all above step
Failure to transfer org.apache.maven:maven-archiver:pom:2.5 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven:maven-archiver:pom:2.5 from/to central (https://repo.maven.apache.org/maven2): Connect timed out
I use this solution useful for me:
1. Find repository in https://mvnrepository.com/ 2. Copy dependency to my *.poml of project example
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.5</version>
</dependency>
3. Build project. the dependency missing will be downloaded to local repository.
4. Go back into Eclipse, Right-click on the project and select Maven > Update Project. > Select "Force Update of Snapshots/Releases". =>> Error is resolved 5. I remove dependencies at step 2 after finished and resolved.
Done
This worked for me in Windows:
Locate the {user}/.m2/repository
In the Search field in upper right of window, type ".lastupdated". Windows will look through all subfolders for these files in the directory.
Remove all the .lastupdated files.
Go back into Eclipse, Right-click on the project and select Maven > Update Project.
Select "Force Update of Snapshots/Releases".
Click Ok and the dependencies will finally resolve correctly.
It happened to me as Iam behind a firewall. The dependencies doesn't get downloaded sometimes when you are running in Eclipse IDE. Make sure you use mvn clean install -U to resolve the problem. You would see the dependencies download after this.
If you are behind a proxy, you have to update the settings.xml file (under the conf folder of your MAVEN_HOME, the file itself contains information about the proxy settings) and additionally you may need to update your Eclipse Network Settings (Window->Preferences...-> type Network Connections).
Try using -X or --debug in order to get the debug output, this could provide additional information about the problem.
I had similar issue in Eclipse 3.6 with m2eclipse.
Could not calculate build plan: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 from central (http://repo1.maven.org/maven2): ConnectException project1 Unknown Maven Problem
Deleting all maven*.lastUpdated files from my local reository (as Deepak Joy suggested) solved that problem.
I had a similar issue with only a few projects in my workspace. Other projects with nearly identical POMs didn't have an error at all. None of the other answers listed fixed my problem. I finally stumbled upon removing/re-applying the Maven nature for each project and the errors disappeared:
For each project that has a pom with the "resolution will not be reattempted..." error:
Right-click on the project in Eclipse and select Maven->Disable Maven Nature
Right-click on the project in Eclipse and select Configure->Convert to Maven Project
It Happened to me also you may have two solue=tion for this
If your project consist of some external or project specificdependency in it then you have to manually add it to your M2 repo folder which is located at C:\Users\Mohit.Singh.m2\repository folder and then you have to run
mvn eclipse:eclipse and then
mvn clean install from the project folder
if you do not have any wxternal or project sppecific dependency then you may import the project into eclipse as Existing maven project
then right click on project --> GO to maven --> Click on update project
a window will appear check the force snapshot download option and hit on OK
Give correct maven setting.xml path in eclipse.
Windows --> Preference --> Maven --> User Settings
Enter correct setting.xml path in user settings text box
just delete the archetype in maven local repository. As said above, it happens in case of failed archetype downloads.
For me I just added the bellow xml code in the POM.xml file. And after I dit **right click in the project -> Maven -> Update Project and I checked Force Update of Snapshots/Releases ** and every thing worked
<dependencies>
<!-- https://mvnrepository.com/artifact/javax.servlet/javax.servlet-api -->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.1.0</version>
</dependency>
<!-- https://mvnrepository.com/artifact/javax.servlet.jsp/jsp-api -->
<dependency>
<groupId>javax.servlet.jsp</groupId>
<artifactId>jsp-api</artifactId>
<version>2.1</version>
</dependency>
<!-- https://mvnrepository.com/artifact/jstl/jstl -->
<dependency>
<groupId>jstl</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.5.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
settings.xml for proxy?
and in eclipse there are maven global\local profile, add the settings.xml
You could delete the .m2 folder itself and force MyEclipse to re-download all dependencies on startup. Go to Window > Preferences > MyEclipse > Maven4MyEclipse.
Above Error occured due to removing of 'maven-compiler-plugin 2.0.2'
from maven repository.
For me, Above error gets resolved when I downgrade 'maven-compiler-plugin' to version to either 2.0 or 2.0.1.
for mac
I removed all the old failed downloads of maven there were several versions of maven also on my mac
find ~/.m2 -name "*.lastUpdated" -exec grep -q "Could not transfer" {} ; -print -exec rm {} ;
after that, I simply updated my eclipse by
help -> check for updates
and the problem resolved for me
the main reason for this problem is the failed old updates does not allow you to download archetype so if you try to build project in any archetype of maven it gets failed
create a file delete_lastUpdated_and_remote.sh(use \n):
#!/bin/bash
find $(cd $(dirname $0); pwd) -name "*.lastUpdated" -type f -print -exec rm -rf {} \;
find $(cd $(dirname $0); pwd) -name "_remote.repositories" -type f -print -exec rm -rf {} \;
Put it in the local Maven repo, such as %userprofile%\.m2\repository or ~/.m2/repository, and run it.
In windows, you should install Git to run sh file also.
I also use it in jenkins job.
I got this error for the plugin below:
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>2.5</version>
I modified tag version to:
<version>2.5.0</version>
Then open Context menu on your project in eclipse and choose Maven > "Update Project ...", make sure "Update Dependencies" is checked in the dialog box and hit "OK" button.
In my case, I got this error message in spring tool 4
ArtifactTransferException: org.codehaus.plexus:plexus-interpolation:jar:1.26 failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.plexus:plexus-interpolation:jar:1.26 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org java.lang.reflect.InvocationTargetException
Here is the solution
step 01 - first close the spring tool Application
step 02 - go to path C:\Users\User and Delete .m2 folder
step 03 - Now go to package Explore and select your project
step 04 - Now Right Click on your project and go to the Maven and click Update Project
How to uninstall Spring Tool 4
step 01 - click on Help and Go to the About Spring Tool Suite 4
step 02 - Now click on Installation Details
step 03 - inside of that you can see the all Installed Software, simply press Ctrl + A to select all and click Uninstall
The solution that work for me is the following:
Copy the dependency to pom.
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.5</version>
</dependency>
Click right on your project
Select Maven
Select Update project
Select Force Update of Snapshots/Releases
Remove all files inside repository.
Go to C:\Users\DELL.m2\repository, select all the files and delete it.
Then go to project, right click maven update project (Alt+F5). It will download all the dependent files inside repository.
Please Make sure that settings.XML file in the folder .m2 is valid first
Then after clean the repository using below command in cmd
cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i