Activity Not Available
I Use This!

News

Analyzed about 1 month ago. based on code collected about 1 month ago.
Posted 2 days ago
As I got several requests how to show an “Out-of-office” in Gerrit and Bugzilla, I documented this in the Eclipse Platform Contribution tutorial. Have fun.
Posted 2 days ago
We are rolling out the new Eclipse Contributor Agreement (ECA).
Posted 2 days ago
A lot of Vert.x conferences are planned this fall around the world, here is a quick recap of these events: JavaZone Let’s build a scalable async Vert.x app in < 60 min - Paulo Lopes (Wednesday, 18:20 - 19:20) Geecon Reactive in Sopot Reactive ... [More] back-pressure with Vert.x - Julien Viet (9th of September, 11:45 - 12:30) JavaOne Reactive Microservices with Vert.x - Burr Sutter (Thursday, Sep 22, 4:00 p.m. - 5:00 p.m.) Reactive Distributed Applications with Vert.x - Clement Escoffier (Wednesday, Sep 21, 8:30 a.m. - 9:30 a.m.) Vert.x: From Zero to (Micro-) Hero (Hands-on Lab) - Clement Escoffier (Thursday, Sep 22, 12:00 p.m. - 2:00 p.m.) Go Reactive with Vert.x in Oracle Application Container Cloud - Edson Yanaga (Monday, Sep 19, 5:30 p.m. - 6:30 p.m.) Reactive Summit Reactive Polyglot Microservices with OpenShift and Vert.x - Clement Escoffier (Tuesday, October 4, 11:20am - 12:10pm) Devoxx BE Better performance with HTTP/2 - Julien Viet Reactive Microservices with Vert.x - Edison Yanaga and Burr Sutter If you are going at one of these conferences, don’t miss the opportunity to learn more about Vert.x! [Less]
Posted 3 days ago by nore...@blogger.com (Christian Pontesegger)
We are going to prepare our first project setup with Oomph.Source code for this tutorial is available on github as a single zip archive, as a Team Project Set or you can browse the files online.   For a list of all Oomph related tutorials see my ... [More] Oomph Tutorials Overview.Step 1: A basic setup fileOf course Oomph setups can be created within eclipse. So start with a new General/Project named com.codeandme.oomph. Now create a new Oomph / Setup Project Model. The wizard will setup all kinds of default tasks for us, but we want to start from scratch to understand all the tasks involved.So select a Simple Project, provide a Label "Code and me" and Finish the wizard.The setup file created simply contains a root node for the project and a default stream named Master.Not much of a setup yet, but we can already add it to our eclipse installer.Step 2: Adding the setup to the installerLaunch the eclipse installer from our first tutorial, select an eclipse product and advance to page 2 of the wizard. There hit the + icon on the toolbar, select Browse File System and select the setup file we just created. The setup will be added to the node. Not much sense installing our empty setup yet, but now the installer references our setup file and we can test it for each step we add. On each start of the installer the setup file gets reloaded, so you do not have to add the file each time you want to test it.Step 3: Adding a simple ini file actionOne of the simplest actions to add is an ini file adjustment. As you might guess this adds entries to the eclipse.ini file provided with your product installation. Select the Code and me node in your setup, then use the context menu to add a New Child / Eclipse ini task. Now we are going to adjust the task using the Properties view.To change the initial heap size of your Java VM set Option to -Xms, Value to 1024m and VM to true. The last parameter is needed for all Java VM properties. Set it to false when changing any eclipse.ini properties like -showsplash or similar.Make sure to provide a unique ID and a usable Description. The IDs are important when we want to refer to a node later in our setup.Step 4: Add folders to structure your settingsWhen we start adding multiple ini tasks we should cluster them. Therefore add a new Compound item to your root node and D&D your ini settings in there. Compounds add more structure to your setup, but have no effect on the installation process.Optional: Investigate common tasksThe scheme for adding new tasks is the same for all kinds of things. Add a node, adapt its properties, save and run your setup to test it. Good sources for tasks are the existing eclipse project setups. You may browse them by opening the catalog from the toolbar or from the main menu: Navigate / Open Setup / Parent Models / Catalog Index. We will have a closer look at dedicated tasks in the following tutorials. [Less]
Posted 5 days ago
Register for the Eclipse IoT Day @ ThingMonk taking place in London on Sept. 12!
Posted 6 days ago
As promised in my last post, today we are rolling out the new Eclipse Contributor Agreement (ECA). As I mentioned earlier, if you already have an active Eclipse CLA, you don’t have to do anything….your CLA remains active and you can convert to the ... [More] new agreement when it expires after three years. That said, we think that the new agreement is clearer, and more consistent with the practices of the broader free and open source community. In other news, last Wednesday the Eclipse Foundation Board of Directors approved the new IP Policy that I discussed in late June. This means that by the end of this year, projects at the Eclipse Foundation will be able to pick the type of IP due diligence that they want. If you want to learn more, I strongly suggest that you read my previous post on the topic, and join in the conversation on bug 496959. The Eclipse Foundation continues to enhance its policies and procedures to make it a better place for developers to host their projects. I hope everyone agrees that these are all steps in the right direction.Filed under: Foundation [Less]
Posted 6 days ago
After several busy weeks, the PC has finally selected the talks and tutorials for EclipseCon Europe 2016. I would like to thank all members of the PC for their great work and all submitters for their proposals. I am sorry we had to reject so many ... [More] talks. We tried hard to provide a meaningful declined comment, so that people might understand our reasoning. In some cases, it was very difficult to decide though – we liked the submission, but we just liked others a bit more or had to think about the overall balance of topics throughout the conference. It was amazing to see the diversity and quality of the submitted talks. We could have easily extended the conference by one or two days and still filled them with interesting slots. This might be worth a thought for next year. The program reflects the diversity and strength of the Eclipse ecosystem. We are looking forward to interesting sessions about classic Eclipse technologies and tools, a strong web and cloud track, experience reports from industry, science talks and much more. Some special highlights for me are (among others): The strong Java 9 track, especially the discussion “Jigsaw vs. OSGi” and Eclipse Java 9 support The diverse content about JavaScript, cloud tooling, Angular and much more Talks about cross-cutting topics, such as usability, performance, open source and the community The presence of most major Eclipse projects including the Eclipse Platform, Git CDT, the modeling community and Xtext On top of that, we have very good content for the IoT theme day and the project quality day. So be prepared for a hard time when selecting the talks you want to attend at EclipseCon Europe 2016! Looking forward to see you in 2 month! Leave a Comment. Tagged with eclipse, eclipsecon, eclipse, eclipsecon [Less]
Posted 10 days ago by nore...@blogger.com (Fabio Zadrozny)
LiClipse 3.1.0 was just released.The major changes aren't really on LiClipse itself, but on the bundled PyDev (5.2.0) and EGit (4.4.0) plugins.PyDev changes may be seen at http://pydev.blogspot.com.br/2016/08/pydev-520-released-static-type.html.EGit changes may be seen at https://wiki.eclipse.org/EGit/New_and_Noteworthy.Enjoy!
Posted 11 days ago
Happy to announce AM3 (Developer Milestone 3) build for Eclipse Neon. Downloads available at JBoss Tools 4.4.1 AM3. A late bug has been ... [More] discovered in the Docker Tools on the Windows platform. It prevents the Docker Explorer to be displayed and affects also Openshift users. This will be fixed in the next release of JBoss Tools. A workaround exists: after you install JBoss Tools, restart your Eclipse and run Help > Install new software > Work with: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > select Docker Tooling > install. Restart when prompted. What is New? Full info is at this page. Some highlights are below. OpenShift 3 Although our main focus is bug fixes, we continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page. Events Events generated as part of the application livecycle are now displayed in the property view under the Events tab (available at the project level): Volume claims Volume claims are now displayed in the property view under the Storage tab (available at the project level): Here is a short video which demonstrates these new features: Docker Tools Support for Container Labels Users can now specify labels when running a container. The labels are saved in the launch configuration and can also be edited before relaunching the container. Docker Hierarchy View The new Docker Image Hierarchy view lets the user view the layers for a selected image in the Docker Explorer View. This is especially interesting when an image was built locally, as it helps understanding on which layers the top-level image depends. Automatically detect known Docker daemon connections When the Docker Explorer view is opened, the list of existing connections (saved from a previous session) is reloaded. In addition to this behaviour, the view will also attempt to find new connections using default settings such the &aposunix:///var/run/docker.sock&apos Unix socket or the &aposDOCKER_HOST&apos, &aposDOCKER_CERT_PATH&apos and &aposDOCKER_TLS_VERIFY&apos environment variables. This means that by default, in a new workspace, if a Docker daemon is reachable using one of those methods, the user does not have to use the "New Connection" wizard to get a connection. Extension point for Docker daemon connection settings An extension point has been added to the Docker core plugin to allow for custom connection settings provisionning. Server Tools QuickFixes now available in runtime detection Runtime detection has been a feature of JBossTools for a long while, however, it would sometimes create runtime and server adapters with configuration errors without alerting the user. Now, the user will have an opportunity to execute quickfixes before completing the creation of their runtimes and servers. To see this in action, we can first open up the runtime-detection preference page. We can see that our runtime-detection will automatically search three paths for valid runtimes of any type. Once we click search, the runtime-detection’s search dialog appears, with results it has found. In this case, it has located an EAP 6.4 and an EAP 7.0 installation. However, we can see that both have errors. If we click on the error column for the discovered EAP 7.0, the error is expanded, and we see that we’re missing a valid / compatible JRE. To fix the issue, we should click on this item. When we click on the problem for EAP 7, the new JRE dialog appears, allowing us to add a compatible JRE. The dialog helpfully informs us of what the restrictions are for this specific runtime. In this case, we’re asked to define a JRE with a minimum version of Java-8. If we continue along with the process by locating and adding a Java 8 JRE, as shown above, and finish the dialog, we’ll see that all the errors will disappear for both runtimes. In this example, the EAP 6.4 required a JRE of Java 7 or higher. The addition of the Java 8 JRE fixed this issue as well. Hopefully, this will help users preemptively discover and fix errors before being hit with surprising errors when trying to use the created server adapters. Forge Forge Runtime updated to 3.3.0.Final The included Forge runtime is now 3.3.0.Final. Read the official announcement here. Added Install addon from the catalog command From Forge 3.3.0.Final onwards it is now possible to query and install addons listed in the Forge addons page. Freemarker Improved automatic finishing of FreeMarker constructs When you type Enjoy! Jeff Maury [Less]
Posted 11 days ago
@nedtwigg wrote: Whether your preferred IDE is Eclipse, IntelliJ, or a magnetic needle and a steady hand, it's undeniable that Eclipse has many valuable components. Want to parse and analyze Java sourcecode? Easy. Want ... [More] to tinker with building some kind of automatic refactoring tool? Eclipse has low-level and high-level APIs for that. Eclipse's guts aren't constrainted to just Java, it has similar APIs for javascript, C/C++, and probably other stuff that I don't know about. Unfortunately, these components are usually not published to a maven repository - they're only published to a p2 repository. As we've discussed before, almost nobody knows how to use p2, which means that one of the hardest parts of using an eclipse component is just figuring out how to get the jar into your build. So let's say we wanted to take the code formatter out of eclipse and use it to make a lightweight code formatting tool, with Gradle as our build system. How would we do it? Grab pieces from eclipse The goomph project has a p2.asmaven plugin which tricks Gradle into thinking that a p2 repository is really a maven repository. It looks like this in your build.gradle plugins { id 'com.diffplug.gradle.p2.asmaven' version '3.0.6' } // The jars we'd like to pull from Eclipse's p2 repositories def eclipseDeps = [ // The dependencies we actually use 'org.eclipse.jdt.core', 'org.eclipse.text', // Their transitives 'org.eclipse.core.contenttype', 'org.eclipse.core.jobs', 'org.eclipse.core.runtime', 'org.eclipse.core.resources', 'org.eclipse.equinox.common', 'org.eclipse.equinox.preferences', 'org.eclipse.osgi' ] // build a maven repo in our build folder containing these artifacts p2AsMaven { group 'p2', { repoEclipse '4.6.0' eclipseDeps.each { p2.addIU(it) } eclipseDeps.each { p2.addIU(it + '.source') } } } // add these jars as dependencies dependencies { eclipseDeps.each { compile "p2:${it}:+" } } You're probably asking, "Why do I have to manually specify the transitive dependencies!?" And the answer is that p2 and maven's dependency models don't map onto each other that nicely. Goomph might support this in the future, but for now it's not so bad having to list them out by hand. Figure out how to use the eclipse piece Eclipse projects generally have fantastic javadoc, but it can be hard to figure out where to go to get help and discuss the project. Here's the algorithm I recommend to get help: Check the eclipse bugzilla. It's not the prettiest, but there's a wealth of information there, and the core developers are very active. Check the mailing lists. They all have searchable archives. Check the forums. They're generally geared more towards end-users than developers, which is why I recommend checking bugzilla and the mailing lists first, but sometimes there's something good there. If you want to see what's in the process of getting merged in, take a look at the Eclipse gerrit instance, but gerrit's not particularly beginner-friendly. Publish your thing If you're going to publish your thing to a public repository like maven central, you'd normally specify your dependencies in your pom. However, it's important for all of your dependencies to also be present within that repository, and your eclipse dependencies are not. The easiest way to fix that is to embed the classfiles from eclipse into your jar (a "fat jar"), and remove them from your maven pom. Here's how: // embed the eclipse jars into our "fat jar" jar { from { configurations.embeddedJars.collect { it.isDirectory() ? it : zipTree(it) } } // the eclipse jars are signed, and our fat jar breaks the signatures // so we've gotta be sure to filter out the signatures exclude 'META-INF/*.RSA' exclude 'META-INF/*.SF' } // remove the embedded jars from our pom apply plugin: 'maven-publish' publishing { publications { mavenJava(MavenPublication) { from components.java pom.withXml { asNode().dependencies.'*'.each() { if (it.groupId.text() == 'p2') { it.parent().remove(it) } } ... If you'd like to see a working example, check out Spotless. Just clone it and run gradlew ide, and you'll have a working eclipse IDE where you can play with the topics in this post. Follow @DiffPlug Follow @NedTwigg Blog, echoed on Medium Facebook Posts: 1 Participants: 1 Read full topic [Less]