Tuesday, February 16, 2010

Eclipse Day Submissions

Thanks everyone for showing such enthusiasm for Eclipse Day. We already have received some nice proposals. And as requested by many we are relaxing the last date to submit the talk proposals till Feb 28, 2010.

You may find the submitted proposals here  http://bit.ly/EclipseDaySubmissions

Tuesday, February 9, 2010

Did you register for Eclipse Day India 2010?

Registrations opened today for Eclipse Day India 2010 and it has been a great response. Half the seats already booked on day one. Attendees from over 20 companies have already registered and the number will only go up further only so register quickly.

We will be publishing the agenda by mid-March. So if you are an Eclipse enthusiast then it will be a great opportunity to not only attend some really nice presentations but also network with the community. 

And if you are a company which consumes Eclipse, then what better occasion to show your support by becoming a joint sponsor. IBM Rational has already come forward to joint sponsor event.

We would love to hear from you if you have been doing some nice work with Eclipse and plug-ins. Do submit your thoughts at http://EclipseDay.in.

Wednesday, February 3, 2010

[New in 3.6 M5] Configurable problem severities for build.properties

User will now have a finer control over build.properties related problems. Till now there was one catch all preference setting.

In 3.6 several new validations have been added to ensure build.properties reflects the project build path and environment settings. These can be turned on-off using the new additional preferences which looks like this

source. and output. preferences will control the problem reporting for all the source and output entries. A previous post discusses the validation rules in detail.

bin.includes and src.includes related preferences will handle the problem reporting for the corresponding entries. They are typically checked for files and folders existence. src.includes is also validated for presence of source folders. These entries were discussed in this post.
Java compliance properties preference refers to the problems reported for javacSource, javacTarget and jre.compilation.profile entries. The validations rules have been discussed earlier in another post.

The last one remains as catch all for remaining entries.

See Also
Eclipse 3.6 M5 - New and Noteworthy