My friend and I were searching for already built-in features in Eclipse or plugins that allow you to develop code in a group, or to be more specific, in a pair.
I found only a single plugin that provides such features, however it is quite hard to install.
Are there any simple solutions for Eclipse, or should I use a different editor?
You could use Git/GitHub or a similar form of version control. I am pretty sure Eclipse has built in support for Git.
I am new to sakai, i want to add my own tool in sakai source code like announcement,syllabus...etc That tool having some my own functionality for this what i have to do, how can i develop my own tool in sakai.
Thanks.
Use one of the archetypes to get you started, then customise it. When you are comfortable you can change the UI layer to be whatever you like.
https://confluence.sakaiproject.org/display/BOOT/Developer+Tools
If you are looking for a solid "base" tool shell to begin with tool development my recommendation would be to start here: "Sakai Wicket Maven Archetype". There are a few other very good archetypes available but are often outdated and may cause you some problems based on my experience. This has been the one I've had the most success with.
This uses Wicket but does not mean you have to use Wicket to develop further with it. Make sure to pull the 1.2 version as last check the binaries for the others were not available yet so replace -DarchetypeVersion=1.4.1 with -DarchetypeVersion=1.2 It will compile and deploy successfully as a tool "as-is" that you can modify as needed. It also allows you to code in Java to directly access the sakai API and pull from its database or even add your own tables. I've successfully used it with NetBeans 8.0.1 and MySQL 5.6 under Windows 7 with Maven 3.2.3 and Sakai 10.1.
The code is well-documented and is no-frills but with enough varied functional use examples to allow you to do "almost" anything you want. The wicket manual is 600+ pages but in my experience you should be able to accomplish a lot just by looking at the code in the archetype.
Quite a while ago I used to use eclipse (or actually Aptana) for making websites. I never really got how it worked. After my laptop crashed I decided to install netbeans hoping it would be less complex, however it is still overwhelming. I know that working with a good IDE can help out a lot, but I just find it very complex (steep learning curve).
Does anybody know a few good tutorials to help me get started with this?
BTW I will be using it mostly for building websites (php, html, css) occasionally in a more abstract way (drupal) or using a framework (Zend). However I have done some Java programming and would like to start building some apps for android or maybe even learn c# or c++ for windows 8.
I would also like to start using subversion and if possible an integrated ftp client.
Help to get me started would really be appreciated.
Wow, thats really about 5 different questions. Firstly the benefit of using an IDE (for web development) is generally for refactoring tools, a good text editor, built in web previews and a built in development server like apache or glassfish. For your purposes eclipse and netbeans will work equally well, but I suppose netbeans has a slightly less steep learning curve but both are fairly straight forward. I'm going to give you a list of links that I think will help you:
Netbeans - http://netbeans.org/kb/docs/php/quickstart.html
Android - http://developer.android.com/training/index.html
Windows bassed svn client - http://tortoisesvn.net/
Free SVN repository hosting - https://www.assembla.com/home
Good FTP client - http://filezilla-project.org/
I don't think there are any combined svn and ftp clients, and it doesn't really make sense to have one either. A quick note on android development that may steer your choice of IDE, Android development is generally done within eclipse using the ADT plugin. Just a few thoughts...
I am a long time intellij user.
The company where I work is likely to introduce Rational Team Concert to our department shortly. I went to the RTC demo and it looks like a reasonable product, built around Eclipse, but I would rather not give up using IntelliJ.
Does anyone have experience of using non-eclipse IDEs with RTC?
This is going to be hard - you could configure IntelliJ to call the RTC scm commands, but this is not going to be that easy. I have heard of a company planning to build an integration, but not seen this myself (they might have finished this already). Company is called CM-Logic and is UK-based.
I use both of them together. You can't use IDEA to checking or deliver code, but you can certainly edit code in IDEA and then use the RTC tools to checkin.
One warning: I'm on Ubuntu 64-bit, and everything is fine. I have a co-worker using IDEA & RTC on Windows 7 and he has to close IDEA every time he wants to check-in because IDEA has file locks that RTC balks at.
I have no knowledge of the CM Logic's JazzConnect-IDEA product. There doesn't seem to be any way to download a demo of it either.
Rational Team Concert's integration page says "Jazz Connect for IntelliJ IDEA enables developers using JetBrains to leverage the power of Rational Team Concert for source control, work item management, and collaboration services."
Also have a look at this page for other integrations of RTC.
I would say that it could, it looks like IntelliJ offers an version control integration point as does the Jazz SCM component, but I am not familiar enough with IntelliJ to say for sure(looks like ClearCase is already on the list so they are adding support for vendors), I would think that without a full fledged integration where your Work Items are integrated into your development RTC starts to loose it's flair but may be not for your management :)
It seems that the answer is no.
Coexistence could cover many aspects; source code repository, Task lists, builds etc. But the first step would be integrating with source code repository and RTC uses something called Jazz.
There seems to be no available plugin nor plans for such.
Update on this: A new feature for Intellij is in the works, and planned or release this year. Here is the internal RFE. The links tab has a video recording of RTC integration with IDEA.
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=358932&tab=com.ibm.team.workitem.tab.links (Jazz ID authentication required)
I was always wondering why it is a big deal having version control support inside an IDE.
I always preferred to use a command-line/standalone version of the version control of choice and never found IDE integration helpful.
I know it can be helpful sometimes, for example to automatically keep track of renames, but I was bitten by version control plugins a couple of times (especially the ClearCase Eclipse plugin) that I'm now finding it counter productive compared to the command-line version, where I have better control.
What is your opinion?
Integrated Source Control also helps to only keep the important files under Source control. For example, when I add a new File in Visual Studio, the Plugin (visualSVN) will allow me to add it easily without me having to remember to go outside of my IDE and run the command to add it to the repository. On the other hand, it will automatically ignore temporary files, like the obj/ and bin/ Folders.
Essentially: Integrated Version Control that actually works is a great way to keep the repository clean and complete.
I like how some IDE's implement this. Ankh-SVN for Visual Studio is not that great and is a bit buggy, however Subeclipse I find to work exceedingly well when I'm using Eclipse.
I think it really depends on the IDE you're using and the quality of that plug-in. It's going to work well for some setups and terrible for others.
That's why I like Subversion with Tortoise SVN so much. I can choose to use the IDE integration when and where it makes sense, otherwise, just like you said, I can simply use the command line or in my case, the windows explorer based client!
Integration of the IDE with version control and, in particular, software change management (SCM) helps bringing together the philosophies of the IDE and the source control system.
One example is temporary files and binaries, that should not be checked-in and, e.g. in Visual Studio, end up within the source directory if you're not carefully creating new project and solution templates with a non-default directory configuration.
Another could be tracking of work items and complex bug fixes.
Also it saves some ceremony and context-switching when editing files.
Advanced integrations may also allow to push the change management system's concept of "configuration" ("branch", "tag", "view") into the IDE.
ClearCase integration, however, is clearly not "advanced".
A lot of it is simply the preference and comfort level of the user. Some folks are comfortable with the command line. Some prefer a GUI.
I wouldn't make generalized assumptions that all version control within the IDE is bad or buggy based on experiences with a particular plugin which had issues.
Why even have an IDE? Why not just do everything with a command line? ;)
The answer is that having it integrated with the IDE is "better".
My #1 reason:
You can visually see if a file is checked out or not, and if you need to edit a file, you can take the action right there where you are working.
There are more, but that is the big one.
It's depend on your IDE and the way you work with VCS.
Me and my team using VSS plugin-ins inside Delphi IDE, it gives a lot of flexibable feature when working together for example, All our forms are check-in when you start to write a letter or move components it asked if you want to check-out the code file or form.
also when some one change any code in other forms, it pop up and telling you it's already update by someone else and asking you to update current files in your H.D.
and you just get everything while you are in the IDE, you don't need to move to other external file, or command prompt to do a simple task.
I find most people who like to deal with command prompt working mostly in code without GUI IDE or may I be wrong.
Nearly all of my subversion needs can be handled by the IDE interface. It's a lot faster to do 2 quick clicks than pop up a command line, cd to the right place, issue the command, etc.
Command line has it's place, but with the current crop of IDEs, that place continues to shrink.
I have battle scars from using a buggy implementation of an IDE/VCS integration. In all honesty, if it was not buggy it would have been great. As long as there are great tools like TortoiseSVN, I don't see a need for IDE/VCS integration. I'd rather have more tools that do their job well than a few buggy tools.
Version control support in an IDE generally gives you a better view. The IDE actually knows what type of file you are looking at when doing a diff, which means it can do context highlighting and help you do merges more effectively.
I also think it saves setup time. In stead of installing all kinds of tools, a developer can download the IDE, do a checkout an be on it's way. If every developer on a project uses the same IDE, they can help eachother.
"Counterproductive" is a large word. If you have serious CVS/SVN problems maybe once a month, it's still way to few to have complicated clients installed on all your dev machines.
I have both systems where there is an integrated IDE (Microsoft FrontPage against an IIS Development Web site with Visual Source Safe on all of the web content) and where there is not (java command-line development, Visual Studio Express Editions). An intermediate case that I use is jEdit 4.x with VSS integration via plug-in.
I think the integrated case is valuable for the reason it always is -- you don't have to leave your application to interact with source-control functions and you don't have to worry about remembering to add new files and to check out files before editing them. The ability to have a smooth work process and to minimize the risk of oversights is powerful, as far as I am concerned. Even when the IDE-plugin integration is less than perfect (the jEdit 4.x case), I still prefer it over not having it.
I also agree that having explorer integration on Windows, the case for Tortoise SVN, is also a great capability, even when IDE integration is available. This allows convenient operation without having to launch the IDE while also being able to launch from the explorer window into the IDE (depending on file type) or editor or make or whatever while operating in Windows Explorer.
And yes, the command-line interfaces remain valuable, especially for scripting of recuring-operation patterns.
I operate in many contexts. Having low barriers and fluidity of operation in all of them is to be prized.
I'm not sure I understand the question. IDEs by definition are integrated, meaning that they're supposed to help you avoid the need to get out of the environment for anything project-related. Version control obviously fits the bill.
If you're looking for more practical reasons, one is that IDEs can offer you awareness by the nature of their graphical presentation. Eclipse, for example, will present files and directories that have changed. With additional plugins or suites, you can ever get real-time awareness as soon as another user is editing the same file, helping you predict a merge conflict before it occurs. I'm not familiar with a commandline based mechanism.
I use intellij integrated with cvs on a regular basis and by far the best feature of the integration of version control inside the IDE is line-by-line indications of what is added, edited, or deleted along with easy access (mouse hover/tool tip) to the pre-edit changes.
This is all within the source code in a non-obtrusive way.
For the nuts and bolts of version control (checkin/checkout/update/etc) I sometimes use the IDE and sometimes use the command line.
The number 1 reason for an SCM integrated with the IDE is that it makes it more effortless to use it and eliminates the need to REMEMBER to check things out. Through experience I have seen that steps that developers construe as extraneous, which often encompases anything other than writing code, don't get done. Making them do extra steps increases the odds that developers won't bother with it and will work around the source control system