IntelliJ IDEA 10.5 development goes full-speed and here is another fresh EAP build for you to try.
Check out the list of changes in the release notes on the IntelliJ IDEA EAP page and download the new build.
Make sure you follow out blog or twitter and have not missed the recent postings about new things coming in IntelliJ IDEA 10.5.
We’re looking forward to your feedback!
The recent EAP of IntelliJ IDEA 10.5 introduces a new presentation of Android platform inside a project.
Previously, you could configure Android SDK inside Android facet settings, while JDK played the role of the main Project/Module SDK. IntelliJ IDEA 10.5 considers Android platform itself as a Project/Module SDK:
Thus, the standard JDK jars aren’t included to the classpath of your Android module. So, the IDE will not complete the java classes which are not supported by the Android platform anymore. Also, the usages of such classes will be correctly highlighted as errors: 
Note, that in addition to the Android SDK, you still need a Java SDK because IntelliJ IDEA uses it for compilation. You’ll be prompted for it while creating a new Android SDK.
It is important to mention that once you open an existing Android project in IntelliJ IDEA 10.5 it will be converted automatically, no manual configuration needed.
You are welcome to try it in the latest IntelliJ IDEA 10.5 EAP build and let us know what you think.
For quite a while IntelliJ IDEA can detect probable NPE’s in your code. But you have to annotate it with JetBrains’ @Nullable/@NotNull. In order to leave your code free from JetBrains’ annotations you could use external annotations, but they were not so convenient to use as they were not visible in the code. With libraries and SDK code, however, there is no other way except using the external annotations.
So, to make things better, 10.5 IntelliJ IDEA will be able to recognize the most common annotations, such as javax @Nullable/@Nonnull, FindBugs @Nullable/@NonNull, as well as your own annotations with the same semantics.
You just need to configure which annotations are allowed in you code and which should be used by quick fixes to annotate the code.
Try it in IntelliJ IDEA 10.5 EAP and let us know what you think.
IntelliJ IDEA 10 allows you to debug JavaScript code running it in Mozilla Firefox. In IntelliJ IDEA 10.5 can choose to debug JavaScript in Google Chrome as well.
Debugger for Chrome supports all features of JavaScript debugger for Firefox, you can set breakpoints, inspect local variables, evaluate expressions and so on:
If you use Chrome for web browsing and want to debug in it simultaneously you can configure IntelliJ IDEA to use a separate Chrome user profile in ‘IDE Settings | Browser | Chrome‘:
To configure the default debugging browser just edit the ‘JavaScript Debug’ configuration under ‘Defaults’ section.
Download IntelliJ IDEA 10.5 EAP, try the new JS debugger and let us know what you think.
Off-topic: debugging JS in FireFox 4 is supported since IntelliJ IDEA 10.0.3.
A while ago we announced the IntelliJ IDEA 10.5 update, focusing on Java 7 support. Now we invite you to start using Java 7 with your favorite IDE: IntelliJ IDEA 10.5 EAP build 106.273 is available for download from the EAP page.
We will continue showcasing user visible improvements of the upcoming release in our blog (like documentation view overhaul, lighter refactorings UI, etc.), so stay tuned.
As an x.5 version, IntelliJ IDEA 10.5 will be a free update for IntelliJ IDEA 10.
IntelliJ IDEA 10.5 is also going to be a massive bug fix release. We need your feedback — welcome to our EAP discussion forum and issue tracker.
P.S. Ah yes, the codename for this version is Xena.
As a logical next step after inplace introduce variable refactoring we did in IntelliJ IDEA 10, version 10.5 will offer inplace introduce parameter.
Here is a brief overview of what we’re working on.
Once called, it will gently ask you to choose a method you want to add parameter to
Note, that you can introduce parameter in hierarchy by selecting the “Use super method of” option.
Then you’ll get a familiar template-like editor with a possibility to change parameter type and name. The refactoring settings you’ve got used to have in the dialog, are now available during template editing. You can make the parameter final, and generate method delegate, to remove unused parameters and replace field usages with getters. When multiple occurrences found you will be able to replace all of them or decide to replace only one right in place. No need to rerun the refactoring to see the results — they are already in the editor.
All method usages are already processed once you finish typing.
Just make sure you have inplace refactoring enabled in ‘IDE Settings | Editor | Enable in place refactorings‘.
The feature will be available in IntelliJ IDEA 10.5 EAP.
Watch our progress on inplace refactorings and let us know what you think!
We are coming close to opening the Early Access for IntelliJ IDEA 10.5 which we have announced some time ago. So, we are starting a series of blog posts that will describe some additions we are introducing in this new release.
Here is a list of newly added features that simplify working with Javadocs even more. Note that all of them are available in both Ultimate and Community Editions:
/** * <ul> * <li>[caret] * [caret moves here on Enter] * </ul> */ class Test { }
Stay tuned for the news about IntelliJ IDEA 10.5 EAP availability!
We’ve just released a new EAP build of IntelliJ IDEA 10, which is the Release Candidate for the 10.0.3 bugfix update. You can download the new EAP build or check the release notes on the IntelliJ IDEA EAP page.
Latest update contains support for horizontal scrolling with mouse. It also includes important fixes for version control problems with Svn, Cvs and Perforce reported by our customers. The ActionScript editor now properly handles binaries produced by early version of Flash player 11. You can download the new EAP build or check the release notes on the IntelliJ IDEA EAP page.
W00t! The IntelliJ IDEA team just received an invitation from Google GWT team to participate in the Developer Sandbox at this year’s Google I/O conference.
We took part in I/O 2010 last year and have been looking forward to going there again. It’s that kind of event where if you’ve been there once, you don’t want to miss the next one. So, we heartily thank the GWT team for inviting us!
So, if you’re coming to I/O 2011 this May, you’ll have a chance to talk to IntelliJ IDEA developers responsible for integration with Google technologies including GWT, Android, Google App Engine and others. And we’ll have a chance to meet in person and share whatever.
Speaking of GWT, have you seen this recent screencast on GWT Event Bus Basics by Hamlet D’Arcy? It’s on JetBrains TV?
Develop with pleasure!
JetBrains IntelliJ IDEA Team
Tweets about IntelliJ IDEA
