I am proficient at coding, but always struggling to install stuff, such as maven, plugings etc.
As I am used to version control with DevOps and now want to use Eclipse for a Java project, I try to make DevOps communicate with Eclipse. I have just downloaded Eclipse on this pc.
Unfortunately, installing the plugin of 'Team Explorer Everywhere' won't work. Probably a stupid mistake from my side.
I have been following this guide and also tried this one.
After adding the location http://dl.microsoft.com/eclipse/tfs, I get the error that it 'Could not find http://dl.microsoft.com/eclipse/tfs' and the question whether I want to alter the location. I also tried without /tfs.
After some research I found out that I probably need to download something of the plugin first (and then do it manually instead), so I downloaded Source code.zip from here.
Unfortunately, this does not contain the required folders which are mentioned in this Stack Overflow question.
Anyone here who can help me out on this?
Related
I'm using Intellij IDEA/Android Studio.
I was asked not to make any commits unless my code doesn't trigger any warnings in Problems View of Eclipse IDE.
So, is there any quick way to port Eclipse's analysis configuration to IDEA?
Thanks.
There is not. There is the Eclipse Code Formatter third party plug-in for portng over code formatting definitions. Pehaps you can contact that developer and see if he would add problems/inspections definition syncing. Until then, I see two options for you...
Configure your IDEA inspections so they match the team's Eclipse settings. This of course would require some time to initially set up. But I think in the end, it's the best solution.
IDEA can export to files in eclipse format. As part of that it can keep its configuration linked to the eclipse files. This way you could pop over to eclipse to check for problems prior to committing.
I'd like to put the entire eclipse IDE (indigo) under version control (for us that would be SVN) to allow developers to checkout the entire IDE ready to go with minimum environment configuration. Did anybody try this? Would this cause problems with actually USING SVN in eclipse?
I could check it in and have users export it, but that would make it trickier to keep it updated.
I went with #BenjaminLinus approach, get an eclipse, add all the plugins, set up our app's environment specific stuff, zip it up and check it in.
You can... but why? It is just easier to have it in a shared drive for install. You don't need to track version of eclipse.
At work we use Adobe Coldfusion Builder and got no problem installing plugins like MercurialEclipse. But at home I would like to use Eclipse itself, but am running into many many problems. When I try to contact http://cbes.javaforge.com/update it just says "Unable to read repository at http://cbes.javaforge.com/update/content.jar. Installing updates result in an endless ...pending...
What is going wrong here? I thought it would be the firewall. Turned it off, no succes. Tried reading all the articles about this problem, could not find my solution there as well.
Hopefully someone can pinpoint me to the right direction.
Thanx!!
Maarten
Are you using a different version of Eclipse? Try opening the transfers tab before you update and seeing if it's blocking on something like downloading content.jar. If so, the problem is that the repository only supports classic update sites, while Eclipse is only using p2.
As to solving it... I noticed this wasn't working on very recent builds of Eclipse. According to docs, classic is still supposed to be supported. I don't know if this is a change in behavior or a bug. Workarounds would probably be using an older Eclipse, switching to classic updates in Preferences, General/Capabilities, or possibly placing the plugin's zip in the eclipse dropins folder (eclipse/dropins).
I haven't tried these, but the Preferences seems most likely.
I'm using Eclipse 3.7 build I20110526-1708.
Edited
Yeah, you can tell that it's a p2 problem: http://cbes.javaforge.com/update/content.jar is a 404, while http://cbes.javaforge.com/update/site.xml works fine. site.xml is the classic update mechanism.
According to the wiki:
However, users will rarely have a need for enabling Update Manager, because p2 is able to install from any update site that was designed for Update Manager.
I just tried this out myself, and can verify the Capabilites workaround works: After enabling it, go to Help>Software Updates>Find and Install. Click Search for new Features to install, and add your site as a remote site.
It should successfully find the provided features.
As listed on the wiki, this is a workaround, and shouldn't normally be used. I'm not sure why it's necessary; I couldn't find information about it myself.
As for the dropins dir, I made a mistake: it should be a jar file, not a zip. The plugin's jar, which can be found by looking through the site.xml file. This is probably a worse workaround than the first, though.
It may be proxy related issue. Go to network connections preference page and in active provider select manual. Then select HTTP, click on edit and then provide the necessary details. Do the same for HTTPS also in the preference page. Then close the preference page and try again. It should work.
I was intending to have a play with git, and was wondering if anyone had used the git plugin for eclipse
I see it's at version 0.3.1, and was wondering if anyone knew how stable it was / any gotchas?
Update:
If you are using a recent version of Eclipse, your Help menu has an 'Eclipse Marketplace...' link.
Enter 'git' in the Find field. This shows me EGit.
This is also very high in the Popular plugins list.
Click install. Much easier than having to add update site locations by hand.
Github blog spoke yesterday about Egit plugin:
http://freshmeat.net/projects/jgit/
I'm using if for day-to-day work and I find it stable. Lately the plugin has made good progress and has added:
merge support, including a in-Eclipse merge tool;
a basic synchronise view;
reading of .git/info/exclude and .gitignore files.
rebasing;
streamlined commands for pushing and pulling;
cherry-picking.
Be sure to skim the EGit User Guide for a good overview of the current functionality.
I find that I only need to drop to the comand line for interactive rebases.
As an official Eclipse project I am confident that EGit will receive all the main features of the command-line client.
EGit is still in eclipse incubation. You can install it using the Eclipse update manager.
Select Help -> Install New Software...
You probably do not have the JGit update URL in your list of sites so in the 'Work with:' field enter this url: http://www.jgit.org/updates
Click Add...
You should now see Eclipse Git Plugin - Integration Build (Incubation) listed as available software to install. Check it and click Next.
Click Next and agree to the license and it should be installed.
You can integrate Git-GUI with Eclipse as an alternative to EGit.
See this two part YouTube tutorial specific to Windows:
http://www.youtube.com/watch?v=DcM1xOiaidk
http://www.youtube.com/watch?v=1OrPJClD92s
It still seems barely usable, to tell the truth, especially in comparison to the CVS and SVN plugins. Is it really GIT so different that developer with four years of CVS and SVN plugin experience should be completely lost with completely different GUI, unheard commands, two or even single word error messages and "features" like overwriting the shared repository without warning? Do not use it, use command line interface. If you do not like command line interface, do not use GIT at all.
Meanwhile EclipseGit is an "Official Eclipse Technology Project" (09-05-07 GitWiki). I use the current version 0.5.0 (the Wiki is a step behind the development) from time to time, without any problems. Version comparison, commit, revert etc. is working well, although manual refresh's (F5) are necessary when using command line or other Git clients (usual and acceptable Eclipse behavior I think).
For a command line view from within eclipse, install the Aptana Eclipse Plugin, it provides you with a console. It's an incredible productivity boost if you do a lot of terminal commands.
I've set up EGit in Eclipse for a few of my projects and find that its a lot easier, faster to use a command line interface versus having to drill down menus and click around windows.
I would prefer something like a command line view within Eclipse to do all the Git duties.
egit has a serious bug when comparing a file in your working dir with an earlier - it flashes a blank tab. The bug has been around since 2010 and still has not been fixed.
This very basic feature which works very well in svn plugin is completely broken.
I've used it briefly, but it was still lacking support in several important areas (it wasn't doing renames/moves properly, or something). There also was no update site available for it.
I don't remember which version it was, but this was like 6 months ago. Hopefully it is better now.
You may be interested in these pointers: http://github.com/blog/232-github-and-eclipse
There is also gitclipse(based on JavaGit), but seems dead.
I'm serious. I installed the Blackberry web developer thing for eclipse (being stupid, and not seeing the 'web' part). Then, when I realized my mistake, I went and got the JDE for Eclipse. I went through the install process....open up Eclipse...and I'm lost. I don't know how to run code...or the simulator, or anything.
All the tutorials I'm finding are referencing an older "beta" version of the Eclipse plugin, which apparently had a "Blackberry" menu option. I'm not seeing that.
I found some sample code, which gives the helpful instructions:
"1. Extract HelloWorld_incomplete.zip
2. In the IDE, open the helloworld.jdw workspace
3. Open the helloworld.java source file.
"
...I've never seen a .jdw file before. If I try opening it in Eclipse, I get a not-very-useful text file. Since they say it's a workspace, I try the "Switch Workspace" option in Eclipse, which lets me pick a folder, rather than a file.
I'm pretty sure "Import Project" isn't right, either.
So, I figure I'll deal with that later, so I open up the source code (a standard .java file, with a main, etc). I try running it, but it asks for an Ant build file.
I can run standard Java files just fine (that is, I know Java is in my path).
I don't know if maybe I don't have the Blackberry part right...or if it's on the eclipse side where I'm failing.
Does anyone have any ideas?
-Jenny
Edit: Just to be sure, I tried downloading the plugin through eclipse with their provided link (http://www.blackberry.com/go/eclipseUpdate), but eclipse says that it got a .jar file when it was expecting a .zip file, and so it errored. Can you even unzip a jar file (like Eclipse is trying to do?)
It sounds like you have the wrong package.
I installed it yesterday from the "Download Now" button at http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp
and it had both the menu option and the Blackberry project type.
It should have an installer if you get the correct one. I would post a direct link, but RIM likes to ask for your info before allowing the download.
Try installing it to a different directory and using a new workspace. It could be that the old install is interfering somehow.
-Hope that helps
if you want to know step by step to install the jde plugin in eclipse you can visit http://learn.virtue-software.com/2011/05/quick-start-creating-blackberry-application-with-eclipse/