Activity Not Available
I Use This!
Project Vulnerability Report

News

Analyzed about 1 month ago. based on code collected about 1 month ago.
Posted 2 days ago
What is a Linter?Linters are Code Quality Inspectors, which work by basically parsing your code. They check JavaScript code for common mistakes and discrepancies without running the application.You can plug linters into your code editor or copy and ... [More] paste your code into any standard online linting tool. Linting your code is a great thing to […] The post JavaScript Linters, even in your IDE! appeared first on Genuitec. [Less]
Posted 3 days ago
Every year it is amazing to see how fast the Eclipse DemoCamp in Munich sells out. To give everyone a fair chance to register, we have announced the time the registration opens in advance. This year, it took less than 24 hours, until the available ... [More] 110 seats were fully booked. However, even if you did not get a seat, we still encourage you to register for the waiting list. You can register here. There you’ll also find detailed information on the location, agenda, time and more. The democamp is in 4 weeks (June 20th 2016) and some of the 110 registrants will be forced to cancel. We remind all current registrants to double check their availability. We expect some people to unregister before the event. If and only if you are on the waiting list, you will be notified immediately, once a seat becomes available. We wish you good luck and we are looking forward to great demos and seeing you in June! A big thanks to our sponsors: BSI Business Systems Integration AG,  EclipseSource München GmbH, Eclipse Foundation, Capgemini Deutschland GmbH and Angelika for organization. Leave a Comment. Tagged with democamp, eclipse, democamp, eclipse [Less]
Posted 6 days ago by nore...@blogger.com (Fabio Zadrozny)
LiClipse 3.0.3 is now released... The main things on LiClipse itself is that the base platform was upgraded to Eclipse 4.6 RC1 and EGit was upgraded (it had a critical issue in the Git Staging View).Now, what I really wanted to talk about is that ... [More] with this release, the LiClipse editor component was open sourced!The editor component in this case is the component which allows LiClipse to support multiple languages out of the box (either through its own language or through the TextMate grammar).So, the features which are now available as Open Source (EPL) are:Syntax Highlighting (LiClipse, TextMate or SublimeText based).Code completion.Outline view and Quick Outline.Text-based mark occurrences.LiClipse Languages view:Enables exploring installed languages.LiClipse Partitions view:Enables inspecting the partitioning of the editor.Useful to debug how LiClipseText is parsing a language.Use LiClipseText as a base for other editors:Languages may be created and experimented with on-the-fly, without restarting Eclipse.The home page with more details on the project is: http://liclipse.com/text.So, what does this mean for LiClipse itself and its current users?First, LiClipse (the commercial counterpart) still exists and provides advanced features not in LiClipseText:Bundling of LiClipseText (along with PyDev, EGit, ColorTheme, AnyEdit and StartExplorer) as a standalone with native installers.Enhancements to the theming (allowing theming of the IDE along with the editor and a nice dark theme).Multiple cursors.Linting for JavaScript, XML and HTML editors.Code formatting for HTML, XML.Vertical Indent Guides.Improved text search capabilities (with Lucene index-based searching, support for external folders, open editors and additional filtering on results page).HTML preview for the RST, Markdown and HTML editors.Debugging of Django Templates in PyDev.Launching of files opened with LiClipseText.My hope is that users that can will still upgrade to it (to get the advanced features and to help in keeping the LiClipseText and PyDev development going on) or will donate to keep its development going forward...And the main benefit here (both for existing users or new users) is that the LiClipse editor (LiClipseText) being EPL makes it hackable by anyone ;) [Less]
Posted 6 days ago
The latest Eclipse Neon release is now available. Download and test drive it this weekend!
Posted 6 days ago
Mike Reyes, Mary Cole discuss the reasons for selecting Eclipse and RCP, how the move was made, challenges encountered during this move, and the benefits that have resulted from this change. By Mike Reyes, Mary Cole
Posted 6 days ago
Mike Reyes and Mary Cole discuss the reasons for selecting Eclipse and RCP, how the move was made, challenges encountered during this move, and the benefits that have resulted from this change. By Mike Reyes, Mary Cole
Posted 6 days ago
JSDT project has been officially rebooted! Read all about the new features and enhancements.
Posted 7 days ago
I would like to show you how to re-use the Eclipse editor area in an e4 application. Before, I had the problem that the editor disappeared after maximizing views or that Eclipse showed me messages like: !MESSAGE Exception while dispatching event ... [More] org.osgi.service.event.Event [topic=org/eclipse/e4/ui/model/application/ApplicationElement/tags/REMOVE] {ChangedElement=org.eclipse.e4.ui.model.application.ui.basic.impl.PartStackImpl@4981d95b (elementId: org.eclipse.chemclipse.ux.extension.msd.ui.partstack.main.2, tags: [active], contributorURI: platform:/plugin/org.eclipse.chemclipse.ux.extension.msd.ui) (widget: CTabFolder {}, renderer: org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer@7b2f8152, toBeRendered: true, onTop: false, visible: true, containerData: 10000, accessibilityPhrase: null), Widget=CTabFolder {}, AttName=tags, EventType=REMOVE, Position=1, OldValue=Maximized} to handler org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler@5f32ab17 !STACK 0 org.eclipse.e4.core.di.InjectionException: java.lang.ClassCastException: org.eclipse.e4.ui.model.application.ui.advanced.impl.AreaImpl cannot be cast to org.eclipse.e4.ui.model.application.ui.advanced.MPlaceholder at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68) at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:56) So, here’s the description how to use the editor correctly: A) Define an Area under “Shared Elements” in the Application.e4xmi: B) Insert a “Part Stack” called “org.eclipse.e4.primaryDataStack”: Add the tags: newtablook org.eclipse.e4.primaryDataStack EditorStack NoAutoCollapse C) Import the Area in the fragment.e4xmi: D) Reference the Area via a Placeholder called “org.eclipse.ui.editorss”: It’s important that the Placeholder gets the ID “org.eclipse.ui.editorss”. The Area must be referenced in other perspectives via the same placeholder ID “org.eclipse.ui.editorss”. E) The 3.x editor is used when elements are opened via the “Project Explorer”: F) The 4.x editor is used when elements are opened via 4.x editor parts: That’s it! [Less]
Posted 7 days ago by nore...@blogger.com (Konstantin Komissarchik)
Sapphire 9.0.5 and 8.2.5 releases are now available. Both include a fix for the validation messages appearing out of order in some cases and a fix for the diagram editor context menu not displaying if the editor has been scrolled. Sapphire 8.2.5 ... [More] is intended for adopters who are not yet able to require Java 8. Sapphire 9.0.5 will be part of the upcoming Neon release of Eclipse. [Less]
Posted 7 days ago
I’d taken a little break from testing Eclipse Platform on Java 9 Jigsaw builds. A few nights ago, I pulled down the latest builds of both and gave them a spin. I pulled down build 118 of the 64 bit Linux version of the Java 9 JDK. The last time I did ... [More] this, the Jigsaw builds were separate, but they’ve since replaced the Java 9 builds, so when you download Java 9 you now get Jigsaw. It’s currently delivered as a .tar.gz file, so I extracted it into a directory on my system. I then turned my attention to the Eclipse Installer which has a handy feature that hunts down JREs installed on your system and lets you pick the one that you want to use. It also has a handy feature that lets you manually add JREs to the list. The installer includes some logic to help the user avoid making a poor choice, and changes in the way that the JRE reports its version means that the installer doesn’t recognise this particular version of the JRE as a JRE and won’t let you select it (see Bug 493759). I decided to install the latest Neon M7 build anyway using a Java 8 JRE. I launched my newly-installed configuration. I added the Java 9 Support (Beta) feature from the Eclipse Marketplace. You can install it yourself by simply dragging and dropping the “Install” button below onto your Neon version of Eclipse Platform: The last time I tested this, I needed to have Eclipse JDT run on the Java 9 JRE to use the Java 9 support; but now, the Java 9 support seems to work just fine when running the Eclipse JDT on a Java 8 runtime. The JDT team has done some significant work, it seems, since I last looked. I added the Java 9 JRE to the Installed JREs page in the preferences and was able to create and run a Java 9 application. The bits that I tested all seem to work as expected; e.g. the Package Explorer lists modules. I only spent a few minutes poking around before moving on to the next task: I wanted to get the Eclipse Platform itself running on this Java 9 build. I tweaked the eclipse.ini file to point to the Java 9 JVM, by adding the path to the JVM at the top of the file: -vm /home/apps/jdk-9/bin I launched the Eclipse Platform and got as far as selecting the workspace before it died with a message to check the log. I opened Bug 493761. The JDT team engaged within hours. Tom Watson (from the Equinox project team) determined that a change in the boot classpath configuration is the cause and suggested as a workaround to add some additional configuration to the configuration file (after the -vmargs line) to ensure that the necessary modules are available. -addmods java.se.ee For more information, see JEP 261. With that modification, everything works as expected. The workaround is not optimal. For one, the Eclipse Platform fails to launch with this option when you launch under Java 8. The JDT team is looking for a better solution. Your help is appreciated. If you have the time, please test this yourself and report any new information that you discover. [Less]