Friday Nov 29, 2013

Distribution of GlassFish plugin for Eclipse

Last week I blogged about removing GlassFish plugin from java.net update site. Maybe I have chosen wrong words to express myself, because according to some Twitter reactions many people think it means to lower or discontinue support for GlassFish plugin for Eclipse. This is not what I meant so I have decided to rewrite the blog a bit and remove the original blog post not scare people further.

It has been almost a year since GlassFish plugin was moved to OEPE team. As I mentioned in my last blogs, this was done to bring more quality to the plugin development from experienced Eclipse plugins developers from OEPE team. OEPE would also like to focus more on quality than quantity in distribution channels so we have just closed one of three places where the plugin is distributed. It does not mean the plugin is discontinued - I hope it was obvious also in my previous blog. It has and will still have the support it had in the last years. 

The plugin is still available on OEPE OTN site and Eclipse Marketplace. I hope the issue is more clear now and sorry for the confusion. 

Removing GlassFish plugin for Eclipse from java.net

UPDATED: Please check this blog for an updated message about the plugin

As I wrote in my last blogs, the official version of GlassFish plugin for Eclipse is distributed as part of OEPE product. On java.net we have been still delivering developer builds with bug fixes and enhancements. Now there are no more resources that could look after this channel so it was decided to bring it down. From now on there will be only official versions of GlassFish plugin available here on OEPE OTN site.

In future there may origin a channel for unofficial releases of plugin, probably as a part of OEPE OTN site. This will necessary for supporting new versions of GlassFish which will be available to public during development.  

Wednesday Mar 20, 2013

New version of GlassFish Eclipse plugin - migration guide

Who is this guide intended for

This short step-by-step guide should help users that have installed GlassFish Tools plugin for Eclipse to update to the new version. The new version contains many changes, like

  • dropping GlassFish 2.x support
  • changing structure of server adapters
  • changing names and structure of provided project facets
  • adding GlassFish 4 support

Before and after the update the user needs to take neccesery actions to adapt his workspace and projects to these changes. These action unfortunately can't be taken automatically during the update process.

Update GF tools plugin

Backup

Before we start to update the plugin, backup your Eclipse installation and workspaces that your are using. In case something goes wrong, you can easily restore your environment.

Where to update from?

You could have installed your current version of GlassFishTools plugin either from OEPE bundle or from java.net update site (current one http://download.java.net/glassfish/eclipse/juno). The OEPE package contains oficial releases (more stable, tested) of GF plugins and new releases come one or two times per year. The update sites on java.net contain developer builds that are released as needed, typically a lot more often then OEPE. You can download from whatever meets your needs.

What to do before updating the plugins?

Since we changed structure of server adapters, after the update your currently registered GF runtimes and servers won't work with the new version of plugin. So you need to unregister both GF runtimes and servers. The easiest way to do that is following:

  1. Open Eclipse preferences. Go to Server->Runtime Environments section.
  2. Remove all GlassFish server runtimes. Remove the runtime from targeted projects and remove also affected servers when Eclipse asks you.

Now you they are probably many errors reported in your workspace. We will resolve them after update.

The second big change touches the facets structure. The old GlassFish Deployment Descriptors Files facet (hereinafter referred to as sun.facet) is not defined in new version anymore so it would become unusable and (what is even worse) almost unremovable after the update. So for every project that used sun.facet (it could be web, EJB or EAR project) do:

  1. Right-click the project and open Properties.
  2. Go to Project Facets section.
  3. Uncheck the sun.facet and click OK or Apply button.

If you forgot to remove sun.facet from some project, do not worry, there is a way how to do it even after update but it is more tricky.

Last thing you need to do before the update is uninstalling all GlassFish 3.1.x Application Server runtime plugins. You can keep GlassFish 3.1.2.2 Application Server runtime plugin. Steps:

  1. Go to About Eclipse section.
  2. Click "Installation details" button.
  3. Uninstall all GlassFish 3.1.x Application Server runtime plugins.

How to update the GF plugins?

  1. Make sure that you have either java.net or OEPE update site enabled.
    • Go to Preferences->Install/Update->Available Software Sites and make sure that these sites are defined and checked.
  1. If you have GlassFish 3.1.2.2 Application Server runtime installed (you can check it in About Eclipse->Installation Details section), do additional step
  1. Go to Help menu and choose Check for updates.
  2. You should be offered to update (assume that you install from java.net site):
    • GlassFish 3.1.2.2 Application Server runtime (only when you have installed it before)
    • GlassFish Tools
    • Java EE 5 Documentation
    • Java EE 6 Documentation
  3. Update all these plugins in one update batch.
  4. Restart Eclipse.
  5. Optionally you can now install two new plugins:
    • GlassFish 4.0 Server Runtime plugin from http://download.java.net/glassfish/eclipse/runtime site
    • Java EE 7 Documentation from OEPE or java.net site
      After restart the GlassFish 4.0 Server Runtime plugin will register GlassFish 4.0 runtime and server, saving you work.

How to solve problems after update?

You will see probably many problems after your workspace is opened again. Let's solve them.

  1. Register again your servers. Right-click into Servers section and choose New server. All 3.1+ servers are now registered under common server type called GlassFish 3.1.x. You shouldn't loose any configuration if you use the same server and same domain as before.
  2. For every project (currently opened in workspace or opened/imported later) that targeted removed GlassFish runtimes (now probably reporting issues) do
    1. Right-click the project and open Properties.
    2. Go to Targeted Runtimes section. Check newly registered server that you want to deploy project on. Uncheck other (not existing) GlassFish runtimes. Click Apply or OK button.
    3. line-height: 13pt; padding: 0px; margin: 0px;">Go to Project Facets section. If you see warning that sun.facet could not be found you were using old facet and forgot to remove it. The sun.facet can't be now removed in GUI - just note the project. Instead of this facet you check glassfish.web (for Web projects) or glassfish.ejb (for EJB projects). Click Apply and confirm.

For every project still referencing the old sun.facet, do:

  1. Go to Navigator view.
  2. open .settings/org.eclipse.wst.common.project.facet.core.xml file.
  3. delete element that has value of facet attribute "sun.facet". Save the file.

Wednesday Mar 13, 2013

Migration of Eclipse plugins, Java EE 7 support

There is lot of stuff currently going on with Eclipse plugins. First big change is migration of almost all plugins to OEPE, second big change is preparing plugins for Java EE 7 release.

Some of you have already noticed that our main distribution channels for GlassFish plugins development builds - update sites http://download.java.net/glassfish/eclipse/juno[indigo] - had not worked properly in last weeks. The reason for this is internal migration of Eclipse plugins to it's new "home". The plugins will be distributed in the future as part of OEPE - Oracle Enterprise Pack for Eclipse. They will be available in form of both official releases and developer builds.

The reason for migration is that we do not want to confuse users by offering the same plugins on more places. Logically, the GlassFish plugins should be inside OEPE so we chose it as main distribution channel. You can find the official release update site on http://download.oracle.com/otn_software/oepe/juno. Unfortunately the version of GF plugins there is two versions behind java.net last developer build. So for now you can still use old update site http://download.java.net/glassfish/eclipse/juno. In short time we will redirect the page to the OEPE update site containing new developer build from OEPE. The build will contain GF 4 support and other changes and bugfixes. A migration guide is already prepared that will help you transfer.

To be more precise, the migration applies to following plugins:

  • GlassFish Server Tools plugin - provides ability to register GlassFish server, deploy on it, defines GlassFish specific facets
  • Java EE 5 Documentation - contains Java EE 5 documentation which is automatically bound to jars provided by GlassFish server
  • Java EE 6 Documentation - the same for Java EE 6

The GlassFish Runtimes plugins that contain GlassFish server distribution and automatically register it for you will be still available on java.net update site. The exact location will be announced after new OEPE release.

As you may know soon there will be released new Java EE 7. Guys from OEPE are currently working on supporting new features of this release and I have already integrated GlassFish 4 support (reference implementation of Java EE 7) in GF Eclipse plugins. There was also big refactoring done while migrating. The code is now finally more maintainable. After the Java EE 7 release I would like to focus on finishing promised new feature - make it possible to register GF clusters/instances inside Eclipse.

I hope this  blog helped you to keep up with changes.

Thursday Jul 26, 2012

Glassfish 3.1.2.2 in Eclipse plugin, bugfixes, news

I would like to announce new update of Glassfish Eclipse plugin. This update brings new micro Glassfish release 3.1.2.2 support and also some bugfixes.

The update can be installed from http://download.java.net/glassfish/eclipse/indigo (or juno for guys that already switched to the new Eclipse release). If you have already installed older version of GlassFish plugins, you can use Check for Updates functionality in Eclipse (menu Help).

For folks that want the new version of glassfish server registered automatically I have prepared new runtime plugin that is available at the same update sites. As I deliver it as a new feature and not an update (I do not want users using e.g. automatically registered GF 3.1.2 to lose the environment) you can't use Check for Updates, you have to go through Install New Software in Help menu.

We have also fixed recently reported issues 356  and 357. The second one required more work as I decided to rewrite menu a toolbars contributions of Eclipse plugin.

My current work on Eclipse plugin is aimed on providing possibility to deploy on Glassfish cluster or instance, not only on default DAS server.  I try also to consolidate different parts of code to be able to bring other features supporting new Glassfish releases.

That's all for now :). 

Thursday Apr 05, 2012

Bug fix for Eclipse runtime plugin

This blog is intended to inform about bug fix that solves this issue. Before continuing further, one important note – the linux and mac users do not need to read further because this bug appears only on Windows. 

The problem was that the runtime plugin registered new runtime and server each time the Eclipse started. Users ended up with server view looking like this:

I have created new runtime plugin which is now available at the update site http://download.java.net/glassfish/eclipse/indigo (or the same ending with juno for Juno users). You will still need to unistall the buggy plugin and (optionally but recommended) to remove runtimes created by this plugin. Here is the guide how to install bugfix:

  1. Uninstall buggy runtime plugin via menu Help->About Eclipse->Installation details.
  2. Remove runtimes created by old plugin – via Window->Preferences->Server->Runtime Environment. After pressing remove button you may be asked if you want to remove also the servers based on runtime being removed. Recommended is to do so.

  3. Now you can install new runtime plugin. Go to Help->Install New Software.

You may ask why I haven‘t provided the update for buggy runtime which could be installed via Check for updates feature of Eclipse. It has two main reasons:

  • The bug fix is needed only for Windows users so I didn't want to bother other users by updating working plugin.
  • The runtime plugin has had structure that was not quite suitable for Eclipse update. This structure is now changed so future bugs (I am sure that there will be no such ;)) can be fixed by standard update.
Have a good one!

About

This blog is intended (but not limited) to inform about new features and changes done in Glassfish plugins for Eclipse and Netbeans IDEs.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today