eclipse keep on updating and creating - eclipse

I am try to use maven in eclipse (luna,mars and neon),I configure maven settings.xml mirror with maven repository url.and then I configure eclipse about maven,such as settings file path ,local repo path ,unchecked auto build project and so on. but times I want to create maven-archetype-webapp project,it blocked at creating maven-archetype-webapp with 99% schedule more than 1 hour,then I use git bash archetype:generate command create a maven-archetype-wenapp project , and import to eclipse , when I update project (or use Alt+F5),it blocked at updating maven project . so how to create webapp archetype without block,or how to update without block?thanks!!!

Related

Maven Git project in Eclipse as Java project with content assist

I am having a Maven project in Git which I have checked out using EGit in Eclipse Kepler. Now this project is in my local system but not yet visible in Eclipse as a project. I want to achieve below things:
1) Import it in Eclipse as a Maven / Java project (I am not sure which one is appropriate but I want for example, to be able to reach to a method defined in second java file from my current java file and get the content assist facility of available methods / class)
2) I have run mvn clean install command outside of Eclipse and have got required dependency jar files at C:\Users\xxxx.m2\repository. Now in Eclipse I want to configure my project created in step (1) to be able to use those jar files and do not give compile time error for missing required class.
I tried several options of
Import > Maven > Existing Maven Projects
Import > Maven > Checkout Maven Projects from SCM
Import > Git > Projects from Git
but none of them is giving me above two exact functionality.
I am using Maven 3.1.1 and Eclipse Kepler.
Appreciate if someone can guide step by step approach.
I suppose you have already cloned the project using EGit.
After cloning, go to the Eclipse Git perspective:
click on the git+ icon/button Then select the 'Working directory'
Import as general project
This should import the project in Eclipse and work with EGit.
You should see the current branch next to the project name in the Eclipse Package explorer view.

Gradle (gradlew) does not build Eclipse path correctly trying to build spring social

I downloaded spring-social-facebook and spring-social-linked in and built the sources as per the README of the github repo for the projects
After I did ./gradlew eclipse and nce I have imported the project into Eclipse, the build path is not set up correctly.
I tried a few manual set up but did not go very far with that.
I am not a gradle user.
I found out that when you do File -> Import -> Existing projects into workspace in Eclipse, I was using the wrong directory to start from.
When you initially clone the git repository, you have a spring-social-linkedin directory created which is the one you then cd to to do the gradlew operations. And then you have a second one which is created : git/spring-social-linkedin/spring-social-linkedin.
This is this second one you need to select as the root directory to look at when you import the project into eclipse and everything will work fine.
Probably obvious for gradle knowledgeable people...

Importing projects into Eclipse

I have this simple question how to import whole project source into Ecplise so I can browse it easily? Specifically, I have downloaded Maven source code http://maven.apache.org/download.html and I just want to view it same as other projects in my Eclipse.
I've tried to import it with use of two possible options (as archive and as a project) without luck.
Thank you in advance!
Maven itself is a Mavenized multi-module project, Generally there are two ways to import a Mavenized project into a IDE like eclipse:
Pre-requirment:
Suppose you have installed Maven 3 and setup environment variable
properly.
if you use Eclipse, you also need add M2_REPO to you
Build Path -- Classpath Variable, check out here for how to
setup. this tells Eclipse where to find jar dependencies stored in
local maven repository.
Option 1 -- Import as Java Project:
Open a command prompt and go to the extracted source folder, run mvn eclipse:eclipse
and waiting for it finish, make sure it doesn't popup any message start with [ERROR], this
will download all required jar dependencies from internet to you
local maven repository and create .project and .classpath for Eclipse
to use when doing import.
In eclipse, go to File -- Import -- General -- Existing Project into
Workspace, select the extracted source folder as root directory. This
will import a group of projects into Eclipse as bunch of regular java
projects (i.e. project icon inside Package Explorer watermarked with a
capital J).
Option 2 -- Import as Maven Project:
Alternatively, if yo got m2e plugin installed in Eclipse, you can
directly import the extracted project folder, go to File -- Import --
Maven -- Existing Maven Projects, select the extracted source folder
as Root Directory. This will import a group of projects into Eclipse
as bunch of Maven projects (project icon inside Package Explorer
watermarked with a Capital M).
Hope this helps.
The maven repository versions are not uploaded in the exact format they are on disc (from where the the mvn deploy goal is run. I can think of 3 options assuming I understand your question correctly:
You can find the open source project if it exists and get all the
source and project from there.
On an existing project, you go the dependencies, right click on one
and select browse source. Not the same as having the show project
here you can build and run however.
You can download the sources from the maven repo and then
reconstruct the project. I'm not not sure how feasible this
actually is and I have never tried it. I would probably find other
ways before trying this.

m2eclipse/svn project with packaging of pom

I have a project with the following layout
taac
* taac-web
* taac-backend-api
* taac-scheduler
all of this is checked into an SVN repository. When creating a new project in eclipse (originally) I checked out the root taac directory, and it gave me the option to select each of the sub-projects to create new eclipse projects for. I had a problem with svn and had to remove the projects from eclipse, and now when trying to check them out, i no longer get this option. If I select just the sub-projects, then their pom's are invalid (due to not having the parent pom).... Does anyone know how to get that option to select each separate project out?
You can get entire project hierarchy into Eclipse using "File / Import... / Maven Projects" wizard or you can checkout as Maven projects from SVN (make sure you have Maven integration for Subclipse or Subversive installed).
You can also install parent's project pom into a local Maven repository, so Maven and Eclipse will be able to find it when building or working with individual projects.

m2eclipse not finding maven dependencies, artifacts not found

I'm using m2eclipse as my maven 2 plugin for eclipse. I'm brand new to maven, so my mistake might be simple, although searching has not yielded any solutions for me. I can run maven from the command line and it build successfully. However if I import as an existing maven project, or use mvn eclipse:eclipse and then import I get the artifacts not found in my POM file resulting in no maven dependencies being loaded at all.
What's odd is that I have 2 projects, both children to a parent pom packaged project. One child loads all my maven dependencies while the other cannot find any and says my pom file is missing artifacts. Again, I can install and package them all just fine from the command line.
I even tried loading my projects into netbeans which worked flawlessly, however I am required to use eclipse.
Any ideas on how to fix this?
Update
Directory structure, pom files layout:
--main
--pom.xml (is a pom package that is the parent to two other projects)
--ProjectA
--pom.xml
--ProjectB
--pom.xml
Main is the parent project of both ProjectA and ProjectB. ProjectB has ProjectA as a dependency. Apprently m2eclipse is not happy about that depedency. As soon as I remove the dependency of ProjectA from ProjectB's pom file all the maven dependencies are found by eclipse.
- com.company.myproj:app:6.6.0:jar Missing: ---------- 1) com.company.myproj:main:pom:${myproj.version} ---------- 1 required artifact is missing. for artifact: com.company.myproj:main:pom:$
{myproj.version} from the specified remote repositories: apache-incubating (http://people.apache.org/repo/m2-incubating-repository/, releases=true, snapshots=true), central (http://
repo1.maven.org/maven2, releases=true, snapshots=false)
However, I still need ProjectB to have that dependency for ProjectA. The error message seems to be m2eclipse looking for ProjectA in a remote repo. Project A should only be in .m2 directory, but I'm not sure how to tell m2eclipse to look there.
I think this may be just a m2eclipse specific issue because using mvn from the command line works fine and like I said previously, netbeans loads the projects and dependencies just fine.
I had this issue for dependencies that were created in other projects. Downloaded thirdparty dependencies showed up fine in the build path, but not a library that I had created.
SOLUTION: In the project that is not building correctly, right-click on the project and choose Properties, and then Maven. Uncheck the box labeled "Resolve dependencies from Workspace projects", hit Apply, and then OK. Right-click again on your project and do a Maven->Update Snapshots (or Update Dependencies) and your errors should go away when your project rebuilds (automatically if you have auto-build enabled).
It sounds like your m2eclipse install is using the embedded Maven, which has its own repository (located under user home) and settings.
If you open up the Maven preferences (Window->Preferences->Maven->Installations, you can add your Maven installation by selecting Add... then browsing to the M2_HOME directory.
(source: sonatype.com)
For more details see the m2eclipse book
For me maven was downloading the dependency but was unable to add it to the classpath. I saw my .classpath of the project,it didnt have any maven-related entry. When I added
<classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER"/>
the issue got resolved for me.
One of the reason I found was why it doesn't find a jar from repository might be because the .pom file for that particular jar might be missing or corrupt. Just correct it and try to load from local repository.
Okay I fixed this thing. Had to first convert the projects to Maven Projects, then remove them from the Eclipse workspace, and then re-import them.
I had problems with using m2eclipse (i.e. it did not appear to be installed at all) but I develop a project using IAM - maven plugin for eclipse supported by Eclipse Foundation (or hosted or something like that).
I had sometimes problems as sometimes some strange error appeared for project (it couldn't move something) but simple command (run from eclipse as task or from console) + refresh (F5) solved all problems:
mvn clean
However please note that I created project in eclipse. However I modified pom.xml by hand.
This could be a problem if you are using a custom 'Settings.xml', with a different <localRepository> configured in it.
Eclipse will be using the default installation of MAVEN, and will be using the default location for the User to look for the local Maven repository, which on Linux systems would be '/home/${USER}/.m2/'
Eclipse can be easily configured to use the customized 'Settings.xml', by doing the following:
Goto -> Window -> Preferences -> Select 'Maven' -> Select 'User Settings'
Under 'User Settings', select the custom 'Settings.xml' file, for 'User Settings' by clicking 'Browse' and selecting the customized 'Settings.xml'.
Click on 'Update Settings', if the 'Local Repository' Textbox does not show the custom location from the file above, just key in the location and click 'Reindex'.
Click 'OK'
After this, you could proceed to select your project from the 'Project Explorer', right click, Select 'Maven' > 'Update Project'. Make sure that your project is selected (ticked) in the Window, and click 'OK'.
This should help to resolve the issue, if using custom 'Settings.xml' for Maven.
Hope it helps.