In this session, I’ll highlight the easiest ways for Java developers to deliver their code to the cloud and the best ways to reliably make updates and maintain production cloud code. The focus will be on real-world examples using Linux command line tools, open source tools such as Jenkins, and other free SDKs and tools available on GitHub.
Declarative Services is the best way to provide and consume OSGi services when writing bundles. The OSGi Alliance continues to improve this key specification with new features making it better and more simple to use. For the R7 release, Declarative Services (DS) 1.4 will add constructor injection to the existing method and field injection support. Component property types can now be used to annotate components to set component property values in a type-safe manner. Learn about these and other new features in DS 1.4 to see how OSGi services are easy to use!
In the past 20 years, software has become increasingly important for industrial manufacturers. This trend is expected to continue in the future. At the same time, the share of open source technologies in the software business has increased rapidly. While closed software development can be considered “daily business”, the active participation in open source communities is still a fairly new approach for industrial manufacturers. Bosch has recognized the relevance of open source for its future business.
When the first Eclipse projects were created, in-house IT services had to be provided for everything. The Eclipse Foundation provided CVS servers (then SVN, then Git) for managing source code; a Bugzilla instance for tracking issues; mailing lists, news server, and a webserver for reaching out to the community; and a download server for disseminating the results of a project team's hard work. Over the years, these services have expanded to include build and static analysis tools, metadata tracking, and more.
We have introduced Eclipse SW360, a component management hub that allows organizations to manage Open Source, commercial as well as custom software components throughout their entire life cycle. Using SW360 as a one-stop shop for component information, organizations can track the components used in projects or products to:
Xtext provides an API to easily implement formatters for your language, which is used both when a user presses CTRL+SHIFT+F in the editor and when Xtext serializes EMF models.
For users, a good formatter is not only a convenience while typing, it also simplifies having a consistent formatting across all files of the project and avoid whitespace-changes in code reviews.
One of the basic requirement to enable big-data analytics is a rational and effective approach to data ingestion. In long running projects the need arises to evolve the domain model and this potentially affects data quality. As a consequence, the concept of versioning is crucial to keep data centric systems consistent: the importance of service dynamicity and good modularity support in a sound data ingestion workflow implementation cannot be easily overestimated.
Starting an open source project with the Eclipse Foundation is a little more involved than, say, creating a repository on GitHub. The Eclipse Development Process provides a model for successful product development in commercial open source: Eclipse projects value good governance, robust provenance tracking, and professional intellectual property management. The Eclipse Foundation provides services in all of these areas, but leveraging those services requires engagement the development team and the Eclipse Foundation staff.
In this talk I give an introduction to a new Project at Eclipse (1): Xpect, a framework that allows to embed test expectations into comments inside your Xtext language. The approach is non-intrusive to your code, integrates with JUnit and has a smart editor for the Xpect-specific syntax.
Since Xpect separates DSL-Documents from Java-Test implementations, it becomes incredibly easy to add real-world code snippets to your test suite. You even can use your languages’s Xtext-Editor to edit your test cases.
An open source project is more than just a code repository. If you want to be more than a single-developer project in an obscure corner of the world, you need to build community around the code. But building communities of users, adopters, and developers requires planning and work.
JDT introduced support for @Nullable and @NonNull. Applying these annotations to an existing codebase, like the Eclipse Platform, would seem to be straightforward mechanical work. In this session, I report on lessons learned from a first attempt at applying nullness annotations to Platform/UI, and describe the process I've followed since. These lessons will be helpful for others attempting to retrofit nullness annotations to existing codebases.
(Note to PC: this is based on on-going work. It's a bit risky in that I'm just re-starting this process again.)
Cloud computing is gaining more and more attention with the ubiquity of on-demand Internet-based services and resources, such as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS) and more generally Everything as a Service (XaaS). However, the public cloud offers (Amazon, Google, Microsoft, IBM, etc.) and the cloud software stacks (VMware, OpenStack, Docker, etc.) are extremely heterogeneous in terms of provided services, resources, and API.
As a leader in the field of software qualification, we are facing new challenges in controlling the quality of software projects whose development is being externalized. More and more often, large business-critical and organization-specific projects are being developed and maintained by contractors. In the worst-case scenario, organizations are left with few means of controlling the quality:
• of the tests being made and of the quality process as a whole,
• of the software under construction itself.
The IDE market is in rapid evolution. The last couple of years have seen the creation of IDEs for both cloud and desktop as well as new tools and processes that embrace containers, cloud-native development and hybrid apps. This talk will provide an overview of those tools and trends and discuss how Eclipse Che fits in.
Software developers spend much of their time exploring the source code of their software systems, seeking to understand how it works and to assess the implications of making a change. But many developers report occasionally becoming disoriented during this exploration, where they become "lost" and are unable to recall what they were doing and why they were looking at some program element. Becoming disoriented is frustrating, and recovering from disorientation is difficult.
OSGi provides specifications for HTTP whiteboards as well as JAX-RS whiteboards. This talk will give you an real world insight of how these specifications can work together.
Are you familiar with the the problem when you quickly need a site setup consisting of whiteboard services such as static web resources, servlets and REST services for integration testing or a customer review?
So we got Jetty and Jersey in the team, they provide sample implementations for both of the specifications.
Eclipse RAP is a framework to write Web application based on a Java API. This API is based on SWT, and allows to run existing SWT/RCP application as web applications from the same code base. With RAP 3.2 (Oxygen), there is a integration of e4 available and supported by the project team that allows to run Eclipse 4 applications in a web browser.
IoT and Smart Home are hot topics today, and their popularity has spawned a lot of nice frameworks for developing applications, such as Eclipse Smart Home. However, real smart homes tend to be complex systems that pose hardware-software and systems integration challenges, which can provide a lot of headache to software developers lacking significant hardware experience.