I worked around it by running mvn eclipse:eclipse and then manually updating. If I ran mvn eclipse:eclipse and then imported into STS, then everything worked as expected, except of course I'd have to re-run this every time I updated the pom, which was undesirable. If I ran mvn install from the command line the project built successfully. However, when I imported the project using import -> Maven -> existing Maven project, the project did not import correctly import and I could not add the maven managed dependencies library to the build path. I was importing an existing Maven project which ran fine from the command line. I have the same issue using SpringSource Tool Suite. If you have m2e installed and the project already is a maven project but the maven dependencies are still missing, the easiest way that worked for me was Sample: mvn -Declipse.workspace=/home/ft/workspaces/wksp1/ eclipse:add-maven-repo However, if you haven't done any of this before you may need to do one other, one time only step.Ĭlose eclipse, then run the following command from the shell: mvn -Declipse.workspace= eclipse:add-maven-repo This will add all the dependencies you have in your pom.xml into eclipse. From the command line type: mvn eclipse:eclipse
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |