Posts tagged with 'jbosscentral'

Red Hat JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and install it like this:

JBoss Tools or JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) requires a bit more:

This release requires at least Eclipse 4.4 (Luna) but we recommend using the Eclipse Luna SR2 Java EE Bundle since then you get most of the dependencies preinstalled with Java EE Bundle and SR2 release includes some critical fixes.

Once you have installed or if you have JBoss Tools 4.2.x already installed, you can use our update site directly for JBoss Tools:

And for JBoss Developer Studio Bring-Your-Own-Eclipse:

Note: JBoss Tools 4.2.3 and JBoss Developer Studio 8.1.0 will become available in Marketplace only for Final releases at early April

This release is update for Eclipse Luna and also includes some new features which we would like to highlight. You can see everything in the What’s New section for this release.

This version of JBoss Tools targets Eclipse Luna SR2. More stability. Less false positive JavaScript errors. And many other fixed bugs.

If you are a FeedHenry user we’ve now added support for easy importing and running of your FeedHenry Cordova applications.

WildFly 8.2.0.GA archetypes are now available for the HTML5, JavaEE Web & EAR project wizards. They will be automatically enabled when you select a WildFly runtime in the project wizards.

HTML validation in Eclipse Web Tools Luna has an annoying issue with custom HTML5 tags. It warns about any HTML tag name that is not mentioned in the HTML specification. We contributed a patch to Eclipse Mars which allows to disable those warnings for any particular tag name (or a tag name mask, e.g. <ion-*>). Though this was fixed in Eclipse Mars only we back ported this useful feature to JBoss Tools 4.2.3 which is based on Eclipse Luna SR2:

JavaSript file validation now respects ECMA5 keywords.

Tern.java and AngularJS Eclipse (available via JBoss Central - Early Access) has been upgraded to the latest 0.8.2 version.

There is a bunch of new features which were introduced in 0.8.0 releases:

0.8.2 releases also include bug fixes for some critical issues which caused Eclipse to freeze.

On Linux Visual Page Editor can be opened in HTML5 mode for HTML files, where all HTML5 features are supported. Visual Page editor mode can be changed with dialog, which appears during HTML file opening or in Visual Page Editor Preferences.

For JBoss 7 and Wildfly installations, using hostnames with an IPv6 format often failed to connect, show webpages, or even verify the server’s state. Several changes have made this work as expected. With updated wildfly jars, management commands will execute without issue. In addition, our tools will now automatically recognize host names in an IPv6 pattern, and update your launch configuration’s various launch arguments to ensure that the server starts properly and with all expected flags set.

We are going to release a candidate release for JBoss Tools 4.2.3 and JBoss Developer Studio 8.1.0 soon, and we are also working on the next Alpha release for Eclipse Mars.

Enjoy!

Alexey Kazakov

CDT Summit about using Eclipse for C/C++, Linux tools etc.

Docker and Linux Tools with Jeff Johnston

18:00 - 19:00 Docker in Eclipse - BOF hosted by Red Hat

Making Eclipse IDE better at handling real-life projects with Mickael Istria

Hackathon where Mickael and I will be to work on Easier & smart import of projects

Java EE 7 using Eclipse by Arun Gupta

Making Eclipse with HTML and JavaScript fun again! by me

Red Hat will also have a booth this year, come and say Hi!

oh..and we might have a surprise :)

If you are near Burlinggame, SFO then be aware there are other Theme Days such as ioT, Science, polarsys and XText, these you can get into for $200.

EclipseCon is also co-loated with the FOSS4G conference if you are into location technology.

See you there!

Have fun!

Max Rydahl Andersen
@maxandersen

In computing, the Same Origin Policy is an important security concept for a number of browser-side programming languages, such as JavaScript. The policy permits scripts running on pages originating from the same site to access each other’s methods and properties with no specific restrictions, but prevents access to most methods and properties across pages on different sites. Basically, if the web application sends request to the same server, then there will be no restrictions and everything will work like a charm. However, if the request is sent to another server (Cross-domain request - XDR), the browser will block it with the following error:

In the general case there are several ways to do it:

Ripple and CordovaSim use Proxy approach for handling Cross-domain AJAX.

There is a Cross Domain Proxy setting in CordovaSim / Ripple. Basically, Cross-domain AJAX work depends drastically on it. User can choose between three options:

In the 4.2.3.Beta1 and 4.3.0.Alpha1 releases a security warning for "Remote" proxy was added.

To put it in a nutshell, there is no silver bullet for handling all Cross-domain AJAX requests in CordovaSim / Ripple, due to the fact that it dramatically depends on the server side setup. So, if one has faced the issue coupled with the Same Origin Policy / Cross-Domain AJAX (i.e. GET / POST / PUT / DELETE requests the hybrid app is trying to perform are either blocked by the browser or server returns 5XX error), the first thing they should do is to "play" with Cross Domain Proxy settings. Using one of the options must definitely tackle the problem.
Have fun!

Ilya Buziuk
@ilyabuziuk

There are a lot of improvements and bugfixes and I just want to pick the most important things for now. You can see a full list of changes in the What’s New section for the release.

You probably already used the tracing functionality for a running Camel Context, but now we are happy to finally give you a Camel Debugger. Using the Eclipse Debug Framework we created our own Camel Debugger which works fully through the design view of the Camel editor. Here you can set your breakpoints (static and conditional ones) and breakpoints hit are highlighted in your design view. Instead of using the "Run as → Local Camel Context" menu you can now use the "Debug as → Local Camel Context" to startup the Context in debug mode. Once a breakpoint is hit Eclipse will automatically change to the Eclipse Debug perspective.

Step through your routes, add watch expressions, change message content on the fly or simply monitor what your routes do with the messages. Add a conditional breakpoint if you only want to debug on a certain condition. You choose the condition language and you setup the condition in an easy to use expression builder.

Over the past weeks we worked on improvements regarding the usability of our Camel Route Designer. The result of that work is that we introduced a new drawer to the palette of the designer which provides easy to use items for Apache Camel Components. In the past you had to know that the Endpoint palette entry has to be used to create a connector for a Camel component just by prepending the right protocol name to the endpoints uri attribute field. That still left you alone in adding the correct Maven dependency to your projects pom.xml. When you now drop a component connector to the route the pom.xml gets updated automatically so you don’t need to care any longer.

Starting with version 2.14 the Apache Camel developers started implementing a model to determine URI parameters and their meta data. We now use the provided functionality to give our users improved property pages for the Apache Camel Components.

(the above image shows the properties for a file connector endpoint)

Our server adapters have been reworked and we now provide adapters for the latest version of Apache ServiceMix, Apache Karaf and JBoss Fuse.

The wizard pages for creating the servers have been reworked too and you are now able to download the binaries directly from within your Eclipse session.

Another thing to mention is that we replaced the old deployment options in favor to the modules publishing way using the servers view. You can select the server entry there and choose to Add or Remove modules to/from the server. The deployed projects from your local workspace will be visible as a child node under the server item. Depending on your settings for the server publishing options your application will be republished automatically when it gets out of sync / is changed locally.

I hope you enjoy the new stuff. Have fun!

Lars Heinemann

This version of JBoss Tools targets Eclipse Mars 4.5 (M5).

We recommend using the Eclipse 4.5 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you use our update site directly:

Note: Marketplace entry and Integration Stack tooling will become available from JBoss Central at a later date.

As always there is more than can be covered in a single blog but here are some of my favorites. You can see everything in the What’s New section for this release.

The initial work on providing a structured editor for Java EE 7 Batch job.xml files are in. The editor is based on Eclipse Sapphire and over time we want to extend it for smarter content assist both in the structured editor but also in the source view.

Furthermore for Java EE 7 we’ve now added auto enablement of CDI for Java EE 7 projects. Meaning the tools also now honor Java EE 7 CDI spec about no longer requiring beans.xml for activating CDI.

BrowserSim adds skins and layout for iPhone 6 devices.

These skins and others are also available in BrowserSim Standalone mode which allow you to run Browersim without depending on a full Eclipse install.

You can use this "oneliner" to try it out:

If you are on OSX you need this one:

We’ve extended the HTML5 palette to allow easier adding of often used html5 elements.

This grew the palete to be rather big thus we came up with adding a 'Most popular' slot so you always have easy access to the elements you used most often.

The following video shows how that works.

If you are a FeedHenry user we’ve now added support for easy importing and running of your FeedHenry Cordova applications.

Apache Cordova support now includes support for Windows Phone projects (requires you to run on Windows still though :)

This also adds support for running Windows Phone Emulator.

This feature is actually part of Eclipse M5 and not directly JBoss Tools but I wanted to mention it because the feature is awesome and it was contributed by us by the great work of Mickael Istria.

In Eclipse M5 the Project Explorer now have a "Projects Presentation" in its view menu. Allowing you to switch from the traditional "Flat" view to the new "Hiearchical". This new option lets you view the projects as they are structured on the filesystem as opposed to one big flat list.

This is especially super helpful for those who have large multimodule Maven projects. Now you can get some sanity back.

While we wait for feedback on Alpha1, we are already working on what will become Alpha2. Some of the things that are moving here are:

As always, ask/suggest away and we’ll keep you posted!

Have fun!

Max Rydahl Andersen
@maxandersen

This is a JBoss Developer Studio/JBoss Tools maintenance update for Eclipse Luna with critical security and performance bug fixes.

JBoss Developer Studio 8.0.2 includes Eclipse Luna SR1a Git Security Release which has a fix for a serious security vulnerability in JGit client. You can read more here.

JBoss Central software page had a performance regression that caused the page to take several pages to load where it should only be a few miliseconds. That is fixed.

And we fixed it so Early Access features (like integration stack) can now contribute wizards to central when users have enabled Early access.

The included Forge 2 runtime is now 2.13.0.Final. See the release notes here.

We are working on the next update witch will be based on Eclipse Luna SR2 and the first milestone (Alpha) for Eclipse Mars is coming soon.

Enjoy!

Alexey Kazakov

All of these components have been verified to work with the same dependencies as JBoss Tools 4.2 and Developer Studio 8.

To install the Integration Stack tools, first install JBoss Developer Studio from the all-in-one installer, bundled and configured out of the box with everything you need to get started. Alternatively, if you already have eclipse-jee-luna installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

Once Developer Studio is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view. The current 8.0.0.Beta2 integration stack is available as "Early Access" so you must check the "Enable Early Access" checkbox in the installer window. Select the items you’d like to install:

The standard p2 installer is available for JBoss Developer Studio Integration Stack. Simply start jbdevstudio or eclipse-with-jbds, then:

The community JBoss Tools Integration Stack installation is easy as well. If you already have eclipse-jee-luna installed, install JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

Once JBoss Tools is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view. The current 4.2.0.Beta2 integration stack is available as "Early Access" so you must check the "Enable Early Access" checkbox in the installer window. Select the items you’d like to install:

The standard p2 installer is available for JBoss Tools Integration Stack. Simply start eclipse-with-jbt, then:

Note: If you installed into your own Eclipse you should bump up the launch resource parameters:

We’re getting closer to the final release date. You’ll notice feature source bundles are available from all of the integration stack components. For more specifics see:

Hybrid mobile tools uses ADB to work with Android devices and emulators. Fortunately, it is possible to use ADB to connect to Genymotion. which means that you still need the Android SDK installed for this to work.

By default, Genymotion uses its own Android tools but you can change it to use the tools from the Android SDK. After you start the Genymotion application, open settings using the Settings from the menu bar. On the settings dialog switch to ADB tab. Select Use custom Android SDK tools option and specify the location the Android SDK field. End result should look similar to the screen capture below.

Once Genymotion is configured to use ADB, start a virtual device from Genymotion application. ADB will recognize it as a device, rather than an emulator. Hereafter, you can use Run On Android Device from the run menu on Hybrid Mobile projects to test Cordova applications on Genymotion.

So what happens when you already have a real device connected on debug mode? Unfortunately, you can work with only one device at a time, so you need to disconnect the device, to allow Genymotion to receive the application. You can follow the issue on Eclipse Bugzilla to find out when such use will be supported, and as usual, encourage for a quicker resolution.

Gorkem Ercan

Firstly, let’s introduce several fundamental concepts which we will need in the further discussion:

Now let’s move from theory to practice. Run BrowserSim, open preferences (Right click → Preferences…​) and push the Add button on the Devices tab :

The Add Device dialog will be shown:

Now all you need is to input correct data for your specific device and press the "OK" button - newly created device will be added to the preferences. Let’s practice on the real sample - Microsoft Lumia 928. This phone has the following parameters:

Unfortunatelly, there is no Microsoft Lumia skin yet, so you will have to select some other one. Of course this doesn’t make the experience smooth and complete but you will be able to achieve the main aim: test and reproduce layout issues for that device. Although we are trying to update the list of skin / devices, we won’t be able to cover every single case anyway. So, from time to time you will need to do it manually. By the way, in the brand new 8.0.1.GA release we have added IPhone 6 / 6 plus devices:

For those who don’t use Eclipse / JBoss Developer Studio there is a standalone mode of BrowserSim. More details about BrowserSim standalone can be found in the following blog.

We are trying our best to make our tools as good as possible. User feedback is what we are seeking for now. We look forward to hearing your comments, remarks and proposals.
Merry Xmas and Happy New Year!
Have fun!

Ilya Buziuk
@ilyabuziuk

This maintenance release includes mostly bug fixes but there are also a few new features which we would like to mention.

Brand new IPhone 6 / 6 plus skins are now available in BrowserSim and CordovaSim

You can now start and stop your OpenShift-hosted application within Eclipse. OpenShift tools offers start- and stop-actions in the context menu of the server adapter and the application in the OpenShift Explorer.

The Arquillian validator creates a marker and a quick fix if a test contains a deployment method that is not public and/or static.

CDI (Contexts and Dependency Injection) support is now enabled automatically for Eclipse Web Tools faceted projects if they have any Java EE 7 facet. For example if you create a project via New Dynamic Web Project Wizard and select Web facet v.3.1 you don’t need to enable CDI support in project properties or to install CDI facet. CDI Tools will do it automatically.

The included Forge 2 runtime is now 2.12.3.Final.

More maintenance updates for Eclipse Luna are planned and we continue to work on the major release for Eclipse Mars but it’s all for 2015!

Happy Holidays and a joyful New Year!

Alexey Kazakov