The eclipse of the Eclipse

11 06 2014

When you do something for passion or for money you goal to do this well. I trust you do. And I am sure you do when you contribute to Open Source software. You do it from passion, devote your time and use best skills to make your product better and give it to people, hoping they will use it and benefit from it.

Well, Eclipse contributors are also willing their product to succeed, to be the best tool for programmers, made by programmers. But will it defend itself? The Eclipse Foundation Executive Director, Mike Milinkovich was making a keynote speech at 33rd Degree – one of the best conferences in Poland, one of the best I’ve attended. He had a great chance to inspire 1200 Java developers and infect them with his vision and he missed it. After listening to this keynote my impression is that Mike Milinkovich, The Executive Director, does not have vision and Eclipse will oversleep the revolution taking place in software development.

“You don’t want to throw away all you have written for so many years”
Keynote started from outlining the Eclipse history. It is truly great what was achieved, but one should not rely on its history in IT. Software developers are dynamic and open for innovation, not caring about the history much.

History has shaped Eclipse to the IDE as it is now – great one in my opinion, the only IDE I use for Java. But others are not sleeping – IntelliJIdea to be precise. Well Eclipse, you need to compete. It is tough decision to completely change the track and direct to another goal. History (and huge codebase) should not stop you if you want to be the best. Too much too loose by constantly looking back.

One need to respond to the new reality and change the mindset regardless of the great history of the company. Kodak missed the revolution and now it is only a history.

“I have no some vision of the future”
Trusting your team is a good thing. Trusting the open source contributors is even better. Allowing them to decide where to pull the product makes sense. But will it work with just some vision? Having influence on such tool as Eclipse is a great responsibility and a great honour. Representing all the contributors obliges. Isn’t it ruining everything saying that there is no vision? I hope that it won’t ruin Eclipse, because of its contributors doing the great work. But is it enough?

Note: I mean the independent contributors – not the ones from big companies like IBM, contributing because their company makes money on it.

You need a vision. A brave one. To be the best. To improve. Don’t disappoint the people that are actually building the Eclipse. And its users

“How would you convince me to use Eclipse instead of my perfect IntelliJ?”
– the question from the audience raised. Brave question. And one of the best that could be asked after such presentation. And the answer was: “I would not. Just use the tool that best suits you”. Very good answer. You would not convince that person anyway. But you could convince other Eclipse users not to switch to IntelliJ.

Including me

I see no vision, no courage to respond to the market change, no will to be best, better than the competition. I don’t want to be a part of this, I am going to give a try to the IntelliJ.

I am disappointed with the keynote, I feel bad for all the contributors – that their work, passion and impressive skills are destroyed by lack of support from the Executive Director site. I trust that Mike Milinkovich and wants good, but it is not enough.

I am full of appreciation and respect for Eclipse. It is my favourite IDE, powerful, and making my work easier. I am where I am also thanks to it, but the history should not be the only factor defining the future. I don’t want to be a part of it.





Eclipse: Aspectj Maven plugin execution not covered by lifecycle

7 06 2014

aspectj-logoMaven and eclipse integration is not straightforward. There is one m2e eclipse plugin giving support for Maven itself and a lot of other Eclipse plugins to support Maven plugins used in pom.xml.

One of these plugins is the org.codehaus.mojo:aspectj-maven-plugin – the aspectJ Maven plugin. So when you use it in pom.xml and import into eclipse, you will get error:

Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.2:compile (execution: default, phase: process-sources), Maven Project Build Lifecycle Mapping Problem

To fix it

Install AspectJ Maven Eclipse plugin from Eclipse update site (Via eclipse Help -> Install new software…):

http://dist.springsource.org/release/AJDT/configurator/

Prerequisities

To install above maven plugin Eclipse needs to have AspectJ Development Tools Eclipse Plugin and AspectJ compiler installed. If you do not have it, you need to install as well. This is where you can find it (install via eclipse Help -> Install new software…):

http://download.eclipse.org/tools/ajdt/43/update/

Did I help you?
I manage this blog and share my knowledge for free, sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!





Learn eclipse shortcuts with MouseFeed

8 12 2012

Majority of Eclipse actions can be performed with keyboard shortcuts, without even touching a mouse. Using Shortcuts makes you work faster and more efficiently. But how to remember all shortcuts?

MouseFeed is quite useful plugin I use. It shows a small tooltip to the user after performing some action with mouse click. Tooltip shows the keyboard shortcut that can be used instead.

Watch out! As for now (2012-12-9) MouseFeed does not work with Eclipse Juno! In my case it blocked all menu buttons in Eclipse :P

To install MouseFeed go to Marketplace in eclipse:

Help -> Eclipse Marketplace

and find the plugin named MouseFeed.

You may also find interesting to define your own eclipse shortcuts. I described it here.

Did I help you?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!





Custom Eclipse shortcuts: Import / Export

24 11 2012

As working with eclipse is far easier while using shortcuts, here is the way to define your own custom keys and export them. This enables using them in every eclipse instance you use.

 

Define custom shortcut

Define new eclipse shortcut

1. Under Window -> Preference -> General -> Keys is window to set up shortcuts.

2. Find desired command and press desired keys combination in Binding text field. For instance I use Ctrl+R shortcut to clean project (command: Build Clean).

 

Export shortcut preferences

Export eclipse shortcuts

1. Go to File -> Export -> General section -> Preferences.

2. In the next screen choose Preferences (and anything else, you want to export)

3. save it to .epf file.

 

Import shortcuts from file

Import eclipse shortcuts

1. Go to File -> Import -> General section -> Preferences,

2. Choose previously saved .epf file

3. mark Preferences checkbox (and anything else, you want to import). That’s it.

4. Sometimes eclipse restart is required for changes to take an effect.

Did I help you?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!





Eclipse Ant problem after upgrade: Could not find main class for InternalAntRunner

27 10 2012

The error appears after calling ant build command with eclipse and it is known issue after eclipse upgrade.

How to repair

It is enough to ‘Restore Defaults‘ settings of ant Runtime in Eclipse Window -> preferences. As for now it is just a workaround (the eclipse issue is still opened for it):

Restore Ant Defaults

Ensure that you have proper Ant configuration in eclipse

Make sure that eclipse has ant plugin installed. If not – follow instructions at the bottom of this page: Troubleshooting Eclipse Installation.

Did I help you?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!





Eclipse: GC overhead limit exceeded

29 09 2012

When Eclipse stops responding and displays an error message:

An internal error occurred during: "Building workspace".
GC overhead limit exceeded

or any other related to memory limits, like:

PermGen space limit exceeded

It means that the oparation performed was memory-consuming (like building big workspace project) and Java was out of memory. It often happens on 64-bit machines.

Then you should increase the memory allocation for IDE. Do it by editing eclipse.ini file (find it in your eclipse folder). you can increase memory allocation by editing values in those two lines:

-Xms512m
-Xmx1024m

by increasing it for example to:

-Xms1024m
-Xmx2048m

Did I help you?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!





JBoss application server remote debugging from eclipse

21 07 2012

Eclipse and JBoss supports standard debug mechanism: JPDA. Here is how to connect both and debug web application developed in Eclipse, deployed on JBoss.

Debugging gives you possibility to stop your webapp execution at any point you want – just by setting breakpoints in eclipse, that works just like breakpoints in standalone apps – stops execution at specific line of code.

Setting it up takes few minutes. Here is how to do it:

1. Turn on debugging in JBoss

set JAVA_OPTS in your operating system. You can do it in two ways:

– uncomment line in JBoss run.bat file () – just find in this file line, where entry similar to this appears, and uncomment it, restart JBoss:

rem # Sample JPDA settings for remote socket debugging
set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"

(various JBoss versions can have this line located in various places. for example in JBoss 5.1.0 it is in run.conf.bat file somewhere near line 51).

– or you can execute command in command line:

set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"

restart JBoss if needed

2. Set up eclipse

Create new debug configuration according to settings below:

Create new ‘Remote Java Application‘ config, according to screenshot below:

3. That’s all

Then click ‘Apply’ and Debug to connect to JBoss instance.

If does not work – let me know I’ll try to help you. And if my article is not enough – try exploring this one – everything is very well described there.

Did I help you?
I manage this blog and share my knowledge for free sacrificing my time. If you appreciate it and find this information helpful, please consider making a donation in order to keep this page alive and improve quality

Donate Button with Credit Cards

Thank You!








%d bloggers like this: