Genuitec » All Posts Wed, 16 Jan 2019 02:54:58 +0000 en-US <![CDATA[Oracle JDK, OpenJDK and MyEclipse]]> Fri, 11 Jan 2019 19:30:18 +0000 Brian Fernandes There is a lot of concern regarding Oracle JDK in Enterprises, in particular with the new licensing model that is now in effect.

If you are immediately required to discontinue use of all Oracle JDKs, scroll to the end for steps to facilitate that change.

If you can wait just a little bit, it’s important to clarify a few key points:

For context, you can get a summary of key information about the change from

1. Existing versions of MyEclipse ship with Oracle JDK versions prior to JDK 11. In short, these versions are not directly impacted by this change.
2. The change to licensing for older Oracle JDK versions impacts the access to security updates, not the ability to continue to use MyEclipse with the bundled version of the JDK.
3. Future MyEclipse releases will be based on Open JDK version 11, or later.
4. We understand that some companies are being safe by fully restricting the usage of Oracle’s JDK in general regardless of version and have provided steps below to switch to Open JDK immediately if required.
5. Our target timeline for the next MyEclipse release is in February 2019.

As mentioned above, if your company is requiring a move off of Oracle JDK, you have the following two options:

A) Download and install a Zulu build of OpenJDK.
These builds of OpenJDK can be used with MyEclipse out of the box.

Edit your myeclipse.ini file (for Mac OS, this is the eclipse.ini file; refer to this post for file locations), and change the -vm argument to point to the appropriate java binary in the Zulu build. This varies by OS, as follows (showing the path after the JDK installation folder):

  • Windows bin/javaw.exe
  • Linux bin/java
  • Mac OS lib/jli/libjli.dylib

MyEclipse 2018: Works with Zulu OpenJDK 10
MyEclipse 2017: Works with Zulu OpenJDK 8 / 10 (use --add-modules=ALL-SYSTEM in ini file for version 10)


B) Import missing GoDaddy certificates into your OpenJDK installation

Download this cert file (you may need to right click and choose “Save link as”).
Use the following command to import the certificate into your OpenJDK installation.
keytool -import -trustcacerts -keystore <openjdk-location>/lib/security/cacerts -storepass changeit -alias godaddyclass2ca -import -file gd-class2-root.crt

Use the steps in A to modify your MyEclipse installation to use this OpenJDK installation.
The keytool executable can be found in the binary folder of your JDK installation.

As stated earlier, MyEclipse will not work with any version of Java 11 (Oracle or OpenJDK). This will be addressed in the next release.

]]> <![CDATA[MyEclipse 2018 is Now Available]]> Tue, 07 Aug 2018 14:06:26 +0000 Brian Fernandes MyEclipse 2018 has been released, this release is based on the Eclipse Photon stream.

Key features:

  • Java 9 & 10
  • Java EE 8
  • Code Mining
  • DevStyle – enhanced startup, inline search, new dark theme!
  • Spring Boot enhancements

Please read our blog post for a quick walk-through these features, or the delivery log for details.

]]> <![CDATA[PhoneGap Support in MyEclipse 2015]]> Mon, 08 Aug 2016 21:10:33 +0000 Brian Fernandes Existing PhoneGap tooling in MyEclipse 2015

When we introduced PhoneGap tooling in MyEclipse 2015 our aim was to provide comprehensive support for Hybrid Mobile App development using the Cordova and PhoneGap technologies. We support a range of capabilities, taking you from project creation, to building production versions of your application, with the ability to test your application in our Mobile Web Simulator. We wanted to empower users with the ability to build apps locally, without needing to rely on the remote PhoneGap Build service.

For some users, our PhoneGap tools continue to perform well, but at the same time, there are also many users who experience a variety of issues, like those described below:

  • Plugin wizard no longer functions
  • Building fails due to signing problems or other issues
  • Inability to create a PhoneGap project
  • Simulator fails to work or correctly simulate some PhoneGap plugins

Why are these problems occurring?

Tools in MyEclipse must interface with an external SDK environment, comprising the PhoneGap CLI and framework, Android SDK or XCode installation, etc., which we have no control over. This environment often is drastically different from one machine to the next and a deviation from an expected environment could result in behavior that our tooling is unable to handle. Even with detailed documentation, it is hard to get users to replicate the exact environment the tool required.

In addition, the PhoneGap SDK and project architecture have undergone major changes as the PhoneGap project matured, and it continues to change even now. While these are positive changes, this means our tooling must change as well, adapting to the newer project structures, configuration file formats and CLI behaviors, while maintaining backward compatibility for users who were already developing with older versions of PhoneGap which MyEclipse supported – a difficult task. In some cases, bugs in the PhoneGap SDK make this task harder, with behavior that was different, and buggy, for local and remote builds.

Working with PhoneGap in MyEclipse 2015

While we would have liked to continue to support the PhoneGap tooling as it stands in MyEclipse 2015, our experience over the last two years as well as the rapid pace at which the PhoneGap ecosystem is changing, both indicate that this is unfeasible. As we have seen over the past several months, fixes that we make to the PhoneGap tooling don’t work well universally, and still fail frequently when the PhoneGap build system changes.

If the PhoneGap tooling is working fine for you in 2015, you don’t need to make any changes to your development process. However, if you experience issues, we recommend that you start using the PhoneGap CLI instead of the in-product wizards, and start building your app remotely using the remote PhoneGap build service instead of locally. We believe this will actually give you a more reliable and robust experience with PhoneGap and MyEclipse as opposed to using our in-built tooling.
Read this document which details how the PhoneGap CLI can be used to add plugins and build your application remotely. While the document does talk about PhoneGap in MyEclipse 2016, its notes on CLI usage apply to 2015 as well.

In MyEclipse 2016, we have removed our PhoneGap tooling and we will be adding tooling that is focussed more on the app development process, not building specifically. Read our PhoneGap in MyEclipse 2016 announcement here.

]]> <![CDATA[PhoneGap Support in MyEclipse 2016]]> Wed, 20 Jul 2016 12:21:13 +0000 Brian Fernandes Existing PhoneGap tooling in MyEclipse 2015

When we introduced PhoneGap tooling in MyEclipse 2015 our aim was to provide comprehensive support for Hybrid Mobile App development using the Cordova and PhoneGap technologies. We supported a range of capabilities, taking you from project creation, to building production versions of your application, with the ability to test your application in our Mobile Web Simulator.

For some users, our PhoneGap tools performed well, but at the same time, there were also many users who experienced a variety of issues. We wanted to empower users with the ability to build apps locally, without needing to rely on the PhoneGap Build service. This meant having tools in MyEclipse interface with an external SDK environment which we had no control over, an environment which could be drastically different from one machine to the next. Even with detailed documentation, it was hard to get users to replicate the exact environment the tool required. As a result, the local application build support was not as robust as we would have liked.

The PhoneGap SDK and project architecture on which MyEclipse depends has undergone major changes as the project matured. While these were positive changes, this meant our tooling had to change as well, adapting to the newer project structures, configuration file formats and CLI behaviors, while maintaining backward compatibility for users who were already developing with older versions of PG which MyEclipse supported – a difficult task. In some cases, bugs in the PhoneGap SDK made this task harder, with behavior that was different, and buggy, for local and remote builds.

PhoneGap in MyEclipse 2016

At Genuitec, we have to continually balance the cost to implement a feature with the benefit it provides to our user base, and continuing to chase PhoneGap versions, project models, or atypical build environments wasn’t nearly as impactful as investing in other areas. We realize that developing a hybrid mobile app is so much more than project creation, configuration and building – the primary processes we supported in MyEclipse 2015. Most of your time will be spent designing your app’s user interface, and actually writing code in JavaScript. As a result, we will be be focusing our efforts on capabilities like improved JavaScript for a far better coding experience, or CodeLive, which makes it so much easier to work iteratively on your app’s user interface design. Upcoming Angular 2 support will help with next-gen hybrid apps and usability features like Emmet and the Minimap make everyday coding easier.

As far as ongoing integrated PhoneGap tool support is concerned, we would recommend that our users switch to using the PhoneGap command line for a more reliable and transparent experience. In the last few years, command line tools have become far more powerful and flexible, and in the case of PhoneGap, the CLI is easy to use. MyEclipse 2016 includes a Terminal View which can be used to execute PhoneGap commands in a local shell directly within the IDE. We will be adding features like project context awareness, environment set-up, content assist, etc., which will make terminal use more convenient.

Migrating to MyEclipse 2016
The following guide will help you migrate your PhoneGap project from MyEclipse 2015 into MyEclipse 2016 and continue development using the PhoneGap CLI. If you would still like some integrated tool assistance, you can try the Eclipse Thym plugin, though almost all actions can be performed using the CLI – the guide talks through both options. For the easiest application build experience, we recommend building your app remotely using the PhoneGap Build service. However, if you are comfortable with local SDK setup, you can choose to build your applications locally and switch to using the Cordova CLI directly instead of the PhoneGap CLI – our guide takes you through the remote build approach.

PhoneGap Migration Guide

]]> <![CDATA[MyEclipse 2016 CI 0 is Now Available]]> Wed, 10 Feb 2016 10:46:45 +0000 Brian Fernandes MyEclipse 2016 CI 0 is the first release built on Eclipse Mars, with refreshed software integrations across the product. We now also include a command-line terminal within MyEclipse, for easy access to a local console or a remote shell. PhoneGap support is currently not a part of this release. MyEclipse 2016 ships with, and requires Java 8 to run.

For more details, please see our delivery log.

]]> <![CDATA[Deprecation Notice: HTML 5 Mobile Apps]]> Tue, 02 Dec 2014 22:57:15 +0000 support-tony Deprecation Notice: HTML5 Mobile Apps

In MyEclipse 2015, we enhanced our hybrid mobile application development capabilities with the PhoneGap Application support feature. Our PhoneGap tooling allows you to use the latest Cordova versions and remotely or locally build native iOS or Android applications on Windows, Linux or OS X.

MyEclipse 2014 has an HTML5 Mobile Apps feature which provides similar functionality based on Cordova 2.x and a custom remote build service. This feature has been superseded by the superior PhoneGap application support mentioned above, and, on January 30, 2015, we will be discontinuing Cordova 2.x build support for HTML 5 Mobile apps.

What this means

  • If you are using MyEclipse 2014 GA, you can continue to create HTML5 Mobile Apps and preview them in the simulator. However, you will no longer be able to build native apps from your projects.
  • MyEclipse 2015 and future versions of MyEclipse will not allow you to create HTML5 Mobile Apps.

Why was this feature deprecated?

Our HTML5 App support had a number of significant drawbacks:

  • Dated Cordova version:
    • The remote build service that built the HTML5 apps is based on dated Cordova 2.x technology.
  • Cordova version lag:
    • While we could update our build service to Cordova 3.x, there will always be a lag between the build technologies supported by MyEclipse and those released by open source communities like the PhoneGap / Apache Cordova community. We’d like our users to be able to use new versions of Cordova as soon as they become available.
  • Cordova version flexibility:
    • The remote build service locks developers to a fixed version of Cordova. We want you to be able to control the versions of Cordova you build your apps with.
  • Limited / dated plug-ins:
    • Given the hundreds of plugins that are available in the Cordova space, the remote build service can only leverage a small subset of these plugins, limiting the versatility of your native apps. Furthermore, plugins suffer from the same problems listed above for the core Cordova technology – dated versions, laggy support for new plugins and no version control.
  • No local build:
    • You must rely on our remote build service to build your native app, ergo, you cannot build offline and will typically experience a higher turnaround time for your builds.

PhoneGap Application Support

The PhoneGap application support introduced in MyEclipse 2015 replaces the HTML5 App support and has a number of advantages over it.

Cordova versions
The tooling in MyEclipse 2015 has been built to work with Cordova 3.x, and there is no version lock-in; you can choose between any of the versions we have shipped with MyEclipse or download a new version of Cordova yourself and point our tooling to that version.*

You are free to use any of the hundreds of Cordova plugins available in the PhoneGap and Cordova plug-in registries.

Build flexibility
Use the PhoneGap’s remote build service to build Android and iOS apps on any platform. Alternatively, you can set up required SDK locally and benefit from the ability to build Android and iOS apps locally. Local Android builds work on all platforms, local iOS builds can only be created on OS X.

* Occasionally, breaking changes introduced in PhoneGap will prevent brand new versions from being immediately usable; our new architecture allows us to quickly adapt to these changes and release timely updates to support the new version.

Migrating from HTML5 Apps to PhoneGap Applications

HTML5 Apps are similar in structure to PhoneGap Applications. Download MyEclipse 2015 and follow these steps to convert your project into a PhoneGap application project. Alternatively, we have a more detailed tutorial which you can follow to migrate your apps.

  1. Create a new PhoneGap Application project
    1. Choose the same application Id that you used for your HTML5 Mobile App.
    2. On Page 2 of the wizard, choose the Basic Template – Blank Application.
    3. If you were using any native functionality in your app (contacts, geolocation, etc.) then select those plug-ins on page 3 of the wizard.
  2. Copy resources from your HTML5 project’s www folder into the www folder of the PhoneGap project.
    1. Edit the index.html file and replace script references to rte/cordova.js and rte/rte.js with a single reference to cordova.js
  3. Copy images from your HTML5 project’s apps folder into the www folder (with a directory structure of your choosing).
    1. Use our form based config.xml editor to reference these copied images in the corresponding fields, the mapping between the old and new images is straightforward.
  4. With HTML5, we had a separate buildconfig.xml file for each platform. With PhoneGap projects, we have a single config.xml. You will need to transfer settings in each of these files to the config.xml editor. Again, the mapping should be straightforward.
  5. As opposed to the signing profiles specified in the buildconfig.xml files, you must select the signing profile at build time, in the Build wizard. Profiles must still be configured on the preference page, MyEclipse > Mobile Tools > Signing Profiles

If you have any question or concerns, please post them here.

]]> <![CDATA[MyEclipse 2015 CI 7 is Now Available]]> Thu, 13 Nov 2014 13:10:49 +0000 Brian Fernandes MyEclipse 2015 CI 7 adds the following key features:

New editor for config.xml files as well as several key fixes when building local and remote applications in the signing and icon/splash handling areas.

We also support building both local and remote applications with PhoneGap 3.6 (must be externally installed and configured).

JavaScript and Angular JS
Continued improvements in the JavaScript area with an improved Tern JS integration. We also now include tooling for Angular JS development by default.

Our embedded Tomcat 7 connector has been updated from version 7.0.30 to 7.0.56.

The TomEE server connector can now support TomEE 1.7 servers as well.

Maven Dependencies Only Mode
Use this mode when you want only Maven’s dependency management capabilities.

Our documentation has been updated and is now available through the Learning Center tab in the dashboard. Click Help > MyEclipse Learning Center to bring up the dashboard.

Known Issues

Update failure due to Tern / Angular Incompatibilities

MyEclipse has included Tern Eclipse and Angular Eclipse plugins since CI 6 and CI 7 respectively. If you installed either of these plugins from the Eclipse Marketplace or an external update site, you may not be able to update to CI 7 due to conflicts with the Tern / Angular Eclipse plugins contained in CI 7.

To resolve this issue, please uninstall the Tern and Angular plugins, restart MyEclipse and then attempt to update to CI 7.

PhoneGap 3.6
While we do not ship with PhoneGap 3.6, if externally installed, MyEclipse can use this version for both local and remote builds.

When attempting a remote build with PhoneGap 3.6, please ensure your phonegap-version preference in config.xml is set to 3.6.3 (3.6.0 will not work).

 <preference name="phonegap-version" value="3.6.3" />

Please see the Delivery Log for more details and screenshots.

]]> <![CDATA[MyEclipse 2015 CI 5 is Now Available]]> Fri, 19 Sep 2014 07:50:27 +0000 Brian Fernandes MyEclipse 2015 CI 5 is now available for immediate consumption.

CI 5 adds the following key features:

1) Spring 4.1, Spring Security 3.2.5, Spring Web Flow 2.4.0
2) Support for WebSphere Portal Server 6.1 – 8.5
3) Several key fixes in the PhoneGap area, including support for the latest versions of the Android SDK and corrections to the local build support for iOS apps.
4) A new report that provides you information about how much coding time you spend and in what areas of MyEclipse.

Please see the Delivery Log for more details.

]]> <![CDATA[MyEclipse 2015 CI 4 is Now Available]]> Mon, 25 Aug 2014 03:37:26 +0000 Brian Fernandes MyEclipse 2015 CI 4 is now available for immediate consumption.

CI 4 adds the following key features:

1) Template support for PhoneGap projects.
2) PhoneGap 3.5 support
3) REST Project Explorer

Please see the Delivery Log for more details. Click here to download.

]]> <![CDATA[MyEclipse 2015 CI 2 is Now Available]]> Wed, 16 Jul 2014 13:49:23 +0000 Brian Fernandes MyEclipse 2015 CI 2 is now available for immediate consumption.

CI 2 is a bug fix release which focuses on fixes several deployment issues as well as a fix for the PhoneGap simulator, a local build is no longer required before the simulator can be used.

Please see our delivery log for a list of new features as well as known issues.
Download here.

]]> <![CDATA[MyEclipse 2015 CI 1 is Now Available]]> Tue, 01 Jul 2014 03:59:02 +0000 Brian Fernandes MyEclipse 2015 CI 1 is now available for immediate consumption.

Please see our delivery log for a list of new features as well as known issues.
Download here.

About the Continuous Integration (CI) Stream
With the MyEclipse 2015 CI stream, you will have access to new features and important fixes without having to wait for a GA release that could be a few months down the road. MyEclipse 2015 CI will receive frequent updates as development progresses towards our GA release.

While CI builds are stable and are tested, a few omissions and rough edges are to be expected; your feedback on fixes as well as new features is highly appreciated.

Note that this is a unified product which includes advanced WebSphere and Spring features traditionally found in the Blue Edition and MyEclipse for Spring products respectively. While you still need the corresponding license to access these features, you no longer need to install a different product – all functionality is included in 2015 CI.

]]> <![CDATA[2014 Issue Status]]> Mon, 21 Apr 2014 02:04:21 +0000 Brian Fernandes We are aware of the following issues in 2014. Given our current development targets, a fix for these issues will be available in the 2015 EA release due towards the end of May 2014. A 2014 SR1 release, to be released post 2015 EA will include fixes for these issues. Both 2015 EA and 2014 SR1 will include Java 8 support.

Several of these issues are, unfortunately, regressions and you may go back to using 2013 SR2 if these are of significant concern to your team. We regret the inconvenience caused but our team believes that focusing on a solid 2015 release is the best way to assist our customers. For more details on the 2015 release, please see this post.

  • JPA performance issue
    There can be a significant slow down when the JPA tooling refreshes the JPA model.
  • JS performance issue
    In some cases, with a large number of JS resources in the workspace, your the IDE slows down significantly.
  • Matisse missing from primary myeclipse distribution
    Matisse will be added back in the 2015 release.
  • Evaluation of expressions & conditional breakpoints not working during Debug of deployed applications
  • Spring Validation settings not persisted
  • CDI support error when deploying to WebSphere
  • New reports projects cannot be deployed due to signing issue
  • MyEclipse hangs on OS X when disabling validators
  • Packaged deployments incorrectly marked as needing redeployment on workspace restart
]]> <![CDATA[What’s coming in MyEclipse 2015]]> Fri, 18 Apr 2014 15:22:16 +0000 Brian Fernandes MyEclipse 2015 is our next major release set for release in mid 2014. We will be releasing an early access (EA) version for public consumption to be followed by a GA release. 2015 EA is due towards the end of May ’14.

Our REST explorer has been completely rewritten to now work on all OSes and architecures. Explore your own REST web services or those provided by Google, Flickr, etc. It will also have the ability to generate clients for REST services.

Mobile – PhoneGap
2015 will include offline build support for both Android and iOS (requires a Mac) along with support for the latest Cordova 3.x release. You can also build using Adobe’s PhoneGap build service.

We have a number of changes in this department, focusing on an efficient and productive workbench. From views that provide quick contextual actions as well as assistance to cleaner and focused perspectives, our Usability initiative will make you much more productive when using the tool.
We know MyEclipse has grown significantly over the years and can be overwhelming with hundreds of buttons and actions available, the usability initiative will ensure we have a tool that is easy and keeps you productive.

Server Modifications
We’ve rewritten our server support to take advantage of connectors being designed by server providers themselves. In 2015, servers will be much more configurable, and MyEclipse we will be compatible with third party connectors with finer grained deployment updates and control.

Single Product Distribution
Std, Pro, Spring, Blue and Bling editions will now be distributed with a single set of installers for all products. Use whatever features you need by adding / removing components and using a corresponding license.

Besides the above, 2015 will support Java 8 with a large number of miscellaneous enhancements and fixes across the product.

]]> <![CDATA[MyEclipse 2014 and Matisse]]> Wed, 01 Jan 2014 05:47:41 +0000 Brian Fernandes We had made a decision to deprecate and remove Matisse gradually from MyEclipse in favor of the Window Builder Swing Designer that is now included. We made it an optionally installable feature in 2013 and removed it from 2014 as announced through our release notes.

However, after having removed it from 2014, several users asked us to bring it back into the IDE. I’m happy to announce that we have rescinded the decision to remove Matisse in response to this feedback. Existing users of 2014 can add Matisse to 2014 via an update site. We will reintroduce the addition via the component wizard in an upcoming maintenance release of 2014.

To install via an update site:
1) Click Help > Install from Site…
2) Add this update site using the Add button
3) Ensure that “Group items by category” is not checked.
4) Select “MyEclipse Visual Swing Designer” and proceed to finish the wizard. Matisse will be available on restart.

]]> <![CDATA[MyEclipse 2014 GA is now Available]]> Fri, 06 Dec 2013 16:37:20 +0000 Brian Fernandes The latest release of MyEclipse, MyEclipse 2014 GA is now available. 2014 is based on Eclipse 4.3.1 and powered by Genuitec’s Secure Delivery Center – installation is easy and will work alongside your existing MyEclipse installs.This release includes releases of MyEclipse Blue, MyEclipse Professional, MyEclipse for Spring and the MyEclipse Bling editions.

To see what’s new in this release, please read the New and Noteworthy.

Installing MyEclipse Secure
MyEclipse / MyEclipse for Spring Release Notes
MyEclipse Blue Edition / MyEclipse Bling Release Notes