JBoss Tools - Posts tagged with 'jbosscentral'

Maintenance update of JBoss Tools 4.2.1 and Red Hat JBoss Developer Studio 8.0.1 for Eclipse Luna is now available.

Installation

JBoss Developer Studio 8.0.1

This is an updatesite-only update. If you have JBoss Developer Studio 8.0.0.GA already installed, just run:

Help > Check for updates

JBoss Tools 4.2.1 and JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE)

JBoss Tools and JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) require at least Eclipse 4.4 (Luna) but we recommend using the Eclipse Luna SR1 Java EE Bundle since then you get most of the dependencies preinstalled. Once you have installed Eclipse, you can find us on Eclipse Marketplace under "JBoss Tools (Luna)" or "JBoss Developer Studio (Luna)".

For JBoss Tools you can also use our update site directly if you are up for it.

http://download.jboss.org/jbosstools/updates/stable/luna/

What is new ?

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

BrowserSim and CordovaSim skins for iPhone 6 and 6 Plus

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

OpenShift Explorer: Start and Stop Applications

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.

Arquillian validator for not public/static deployment method

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 auto enablement for Java EE 7 projects

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.

Updated Forge 2 Runtime

The included Forge 2 runtime is now 2.12.3.Final.

What is Next

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

We recently tweeted and posted a blog asking you to give your input to what the JBoss Tools team should be doing in 2015.

Today the results are in!

This is not a scientific survey, just an informal one thus neither we or you should use this as source of the single truth of what JBoss Tools users want or think - it is just one of many datapoints on the internet.

Background

We based the survey on the overall topics we have on our tentative roadmap for 2015:

(Hybrid) Mobile Tooling
HTML5/JavaScript/AngularJS
Making Eclipse Better
Docker/Vagrant
JBoss Modules support
Java EE 7 (Server, Batch, Web Services, JAX-RS, etc.)
OpenShift 3 (kubernetes)
Persistence tools (hibernate, JPA, querying, etc.)

And we asked two questions:

"What features would help you ?" and "Which single feature would you prefer JBoss Tools team work on ?".

Results

You can see full summary of the results at twtpoll, below is just my musings about it.

We had 113 votes in total for the 2 weeks the poll was open - I think that is pretty good for something just announced on our blog and twitter account.

The overall distribution is as follows (sorted by which features most said would help them):

Looking at this we should continue making Eclipse better, improve Javascript and enhance the JavaEE 7 support if looking at what would help most of the voters.

What is interesting is that Hybrid mobile tooling did get a higher proportional vote if there was just one single feature you wanted to choose.

But if there is one thing you all wanted then it was that we made Eclipse Better and that becomes very visible when plotting the two questions in a bubble chart:

Then it becomes more clear how important you feel making eclipse better is. And trust me - we agree and it is one of our top priorities in 2015.

Comments

In addition to the questions above the survey allowed you to specify other in the field of what features would help you most. Below are a summary and my initial answers to these.

Better connection between app that’s deployed to (local) running server and debugger for source lookup?

I’m not sure what this refer to since if you are running locally and have use the server adapter to launch the server in debug mode source lookup should happen automatically for your projects. If you who made this comment are seeing this, please leave a comment or pointer to a JIRA so we can follow up ? Thank you.
Better Netbeans support: syntax highliting for .drl?

I wish I could snap my fingers and then just have people working on Netbeans support. We actually did try that in the past and I have the picture to prove it:

On the serious note we actually in past reached out to the NetBeans community to let them know if they would like to have better support for JBoss technology in NetBeans we would gladly help but it would need someone separately to drive the implementation. A few showed up but most faded away again (unfortunately).

That said recently there seem to be an active Drools plugin and WildFly integration (maintained by Red Hatter Emmanuel Hugonnet) and the Forge team is working on making its scaffolding and wizard tools available from Netbeans too. So there is hope!
bpmn, drl tools?

The BPMN and Drools tools are part of the Integration stack that is part of overall JBoss Tools but works at a different release cadence which is why they were not included in this survey. I think it would make sense we made a similar one when they start planning for their new development.

BPMN tooling is being maintained, but Drools is currently mainly just sustained since they focus more on their web based Uberfire based toolsuite.
ccccccdkkfkfdhjcviebihnvturkunncufjtnnntfhui?

Thanks for your salty password. It was very tasty.
Cordova?

Apache Cordova is what Hybrid mobile tooling mainly covers at the moment. We will continue to make the integration better via the Eclipse Thym project that Gorkem Ercan leads. In this area you will also see FeedHenry integration to show up soon(tm).
IoT stack?

We do not have any intermediate plans for Internet-of-Things related tooling; but if you are interested in this area do checkout out the IoT Eclipse working group which has a lot of interesting projects and tools.
Java 9/Project Jigsaw support?

This is being worked on in the Eclipse JDT platform as part of the Java 9 feature development. This is also part of a platform vision being worked at in the Eclipse Foundation and I hope I can post more details/info about this soon.
JSF?

JSF is fully supported by our Java EE runtimes and tooling, but we do not have active plans on doing much feature addition or new features around JSF tooling. We are even planning on deprecating the JSF visual tooling since it has become a high cost to maintain and our usage stats shows only a small portion of users use it. That said we do want to keep JSF tooling updated to spec for content assist, code navigation etc. thus if you have specific issues you feel are missing do let us know in our issue tracker and we will follow up.
m2e?

We are committers on the Maven tooling for Eclipse and Fred Bricon leads the m2e-wtp integration that makes it possible to easily to configure, build and deploy war and ear modules. All our examples rely on Maven thus we are definitely actively working on making the Maven experience better from within Eclipse and JBoss Tools. In that context if you are still on Eclipse Kepler based tooling then try our Luna tools where m2e import performance have been greatly improved!
move to idea as a base?

There are many that wish this to happen, and I understand the reasoning. Intellij IDEA is an awesome IDE, has a lot of great features but it is not possible for us to contribute to because the interesting parts are closed source. I’ve always said that if IDEA had been opensource 10+ years ago when I started moving Hibern8IDE to an IDE, JBoss Tools would probably have been IDEA based today. But Eclipse being opensource and the most used IDE Eclipse that is where we ended up.

Many thinks IntelliJ IDEA is opensource, but it is only its core features that are opensource. All the interesting tools (for JBoss technology) are mainly part of the Ultimate Edition which is closed source; meaning we have no sensible way to make an opensource tooling offering on IDEA (assuming we had an army of developers with free time available :)

That said, IntelliJ already has good JBoss support and we are engaged with the IntelliJ team on making information about it more readily available. Arun Gupta made a few blogs and webinars on the IDEA support for JBoss and Java EE.

But, just be aware all of that does require the Ultimate Edition.

For those that do not know, JBoss Forge is available today in Intellij. That at least gives you some of the scaffolding features also available from JBoss Tools.
Nestor?

Nestor is one of our JBoss Tools Playground features that are experiments that we are making to explore what things we can do to improve the Eclipse experience. Nestor is the one that allows viewing your projects nested as they are on your filesystem instead of the flat project layout default available in Eclipse.

And I’m happy to say that the Eclipse platform lead have accepted to get this integrated into the upcoming Eclipse Mars release if we submit a Gerrit patch for it - which we are working on to happen ASAP.

We are also going to make our Easymport feature available as incubation for Mars which also will help importing your existing projects into Eclipse much smoother.

Conclusion

I want to say many thanks to those who participated and let their voice heard about what we should be working on in 2015. I hope you will see that we do attack most of the high priority items.

But do remember we can always use your help too - bug reports, feature requests and pull requests are always welcome!

If you are interested then please do look into our JBoss Tools Community Acceptance Testing program or get dirty with the code at http://github.com/jbosstools.

Have fun and Happy holidays!
Max Rydahl Andersen
@maxandersen

When you have have typed collections in your code like:

public void process(List<Product> products) {
  List<Customer> customers = getCustomers();
  // cursor here
}

Most know that you can use the foreach template via normal content assist to quickly generate code like this:

public void process(List<Product> products) {
  List<Customer> customers = getCustomers();
  for(Customer c : customers) {
    // cursor here
  }
}

But the foreach template will always choose the nearest collection, making it impossible to use with for example the products parameter in the above example.

The solution is to use the 'enhanced for loop' Quick Fix.

It is available when you have type the name of the collection and use the Ctrl+1 (Cmd+1 if on OS X) shortcut.

To illustrate it, here is a small video of it in Eclipse.

Hope you enjoyed this little tip!

Thanks to Xavier Coulon for asking the question and giving the idea for this Tip blog, and thanks to Markus Keller (JDT UI lead) for reminding me about the Quick Fix solution.

Have fun,
Max Rydahl Andersen
@maxandersen

I previously decribed how to use a combination of maven-war-plugin webresources and Maven profiles, in order to deploy minified resources. In this article, we’ll expand on these concepts a bit, to demonstrate how to deploy test resources, in a somewhat elegant and portable way.

User story

In some cases, you want your web application to deploy test resources, whether it’s logging or database configuration files, or even some test mocks during development.

When you’re using Eclipse Java EE, m2e-wtp explicitely prevents test resources from being deployed (in order to limit behavior discrepancies between Maven CLI and Eclipse), and if you try to mess with Eclipse’s Deployment Assembly page, its settings will be reset next time you perform a Maven > Update projet configuration.

So you need a solution that works for both Eclipse, command line and even other IDEs as well. Let’s see how you can achieve that…

Pre-requisites

You only need :

a Java EE based Eclipse distribution for the following to work: stock Eclipse, JBoss Developer Studio or SpringSource Tools Suite for instance, as long as m2e-wtp is installed with it.
a Maven project with packaging war

Configure a new `dev` profile

In order to deploy test resources with WTP, we need to add a new Maven dev profile to the <profiles> section of your pom.xml. This can easily be done with Ctrl+space assist. Selecting the m2e profile template and changing the id to dev will get you started.

The profile is automatically enabled when running in m2e, via the m2e.version property.

Then, you need to add a maven-war-plugin configuration to the <build><plugins> section of the new profile, and configure <webResources> so that test resources from the test output directory are copied to WEB-INF/classes, using a regexp to only include specific files.

Eventually, this is how your dev profile should look :

<profile>
  <id>dev</id>
  <activation>
    <property> <!-- this will automatically be enabled when using m2e -->
    <name>m2e.version</name>
    </property>
  </activation>
  <build>
    <plugins>
    ...
      <plugin>
        <artifactId>maven-war-plugin</artifactId>
        <!-- this will inherit existing maven-war-plugin configuration-->
        <configuration>
          <webResources>
            <resource>
              <directory>${project.build.testOutputDirectory}</directory>
              <includes>
                <include>**/some/test/resources/**</include>
              </includes>
              <targetPath>WEB-INF/classes/</targetPath>
            </resource>
          </webResources>
        </configuration>
      </plugin>
    </plugins>
  </build>
</profile>

In Eclipse, the matching test resources are not served directly but are actually copied/processed to target/m2e-wtp/web-resources/WEB-INF/classes and deployed from there.

If the original configuration already defines <webResources>, use <webResources combine.children="append"> in the dev profile, so all resources get deployed. You can learn more about merging plugin configuration on the Sonatype blog.

If you decide to declare this profile in a parent pom, don’t forget to put the <plugins> node under the <pluginManagement> section, or else, these configurations will not be inherited by your war projects.

This extra configuration will be merged to your existing maven-war-plugin configuration (check the maven-war-plugin configuration in the Effective POM tab of the pom.xml editor).

Now, using m2e-wtp, every time a test resource is modified, it will automatically be deployed to your server, on-the-fly. This is borderline magic, I know.

Conclusion

Hopefully, this article gave you a glimpse of the powerful Maven capabilities m2e-wtp brings to Eclipse, showing how you can easily deploy your test resources in your development environment in a portable way.

Take it easy!

Fred Bricon https://twitter.com/fbricon

We are working on our plans for JBoss Tools and Eclipse in 2015 and got some high level topics we are looking into working on and was wondering what you would like to see improved.

Overall features

The overall features we are currently planning to work on in 2015 for our core tools (excluding Integration stack plugins) is listed below at a high level.

(Hybrid) Mobile Tooling
HTML5/JavaScript/AngularJS
Making Eclipse Better
Docker/Vagrant
JBoss Modules support
Java EE 7 (Server, Batch, Web Services, JAX-RS, etc.)
OpenShift 3 (kubernetes)
Persistence tools (hibernate, JPA, querying, etc.)

Make your voice heard

You can make your voice heard by going to http://twtsurvey.com/jbosstools2015 and answer the 2 simple questions!

…and we do have a 'Other' field where you can let us know if we forgot something above ? :)

Thanks for your input!

Have fun!
Max Rydahl Andersen
@maxandersen

JavaScript is extremely popular nowadays and the fact Eclipse JavaScript Development Tools supports JavaScript ECMA3 standard only didn’t let us sleep well, so we decided to do something about it.

First we got to work and fixed tons of issues in Eclipse JavaScript Development Tools to make it usable, then when it esd good enough we extended it with some good features to make it even better.

Tern.java is now working behind the scene to provide JavaScript code analysis and content assist. Good news there is no need to configure it manually. Just install Tern.java Adapter from JBoss Tools update site and it configures projects with JavaScript facet automatically to unleash all Tern IDE features for you.

ECMA5 Support

HTML and JavaScript source editors now show JavaScript ECMA5 proposals in content assist for projects with JavaScript facet.

javascript content assist

Popular JavaScript Frameworks Support

You can also get content assist for many popular JavaScript Libraries through Tern Modules. Manual configuration is required in Project Preferences.

javascript modules

CordovaJS Module for Tern.java

We provided CordovaJS Module for Tern to improve Cordova related content assist in JavaScript source. Tern integration configure it for Eclipse Thym Project automatically, so you don’t need to do manual configuration to see content assist for CordovaJS. Just create Thym project, open index.htm and start using it.

javascript cordova content assist

AngularJS Tools Early Access

JBoss Tools provides support for AngularJS through JBoss Tools Central Early Access. It installs full distribution of AngularJS IDE with many cool feature like:

source code highlighting and navigation
source code content assist
AngularJS model view
and more.

Read about all AngularJS IDE features here.

/Denis Golovin

The JBoss Developer Studio 8 and JBoss Tools 4.2 release enables developers to use these tools to build mobile applications by using the Apache Cordova framework. Apache Cordova (fka, PhongeGap) is a framework for building packaged mobile applications using web technologies such as HTML5, JavaScript and CSS3. In this article, I will explore different scenarios for getting started with the tools and Apache Cordova.

Where are the tools?

Hybrid mobile tools are not part of the default installation but getting them is easy. Although there are other ways, I usually use JBoss Central to pull them in. Here is how.

First switch to Software/Update tab on JBoss Central. Next select JBoss Hybrid Mobile Tools + CordovaSim. I usually select the AngularJS for Web Tools option before hitting the Install/Update, in order to get the improved support for Ionic framework.

Here is a screeen cast for getting started with the hybrid mobile tools.

1. Start a new Cordova project

This is the option when starting a new project or just experimenting with Apache Cordova development.It gives a basic project template that you can easily change and you can select the initial set of cordova plug-ins to include into your project. I usually add the console plugin at this time, to be able to use console.log() during development and remove it before the final export.

The video above not only shows how a project is created but also introduces the tools at your disposal going forward.

2. Import your existing Cordova application

If your Cordova application already exists and it was developed using a compatible tool such as Cordova CLI, you can import it easily and start using all the functionality available. Import process will also restore your plugins if you have been using the new cordova save command.

Here is a short video that shows the import feature in action.

3. Use existing mobile web site code

Often getting started with your packaged mobile application requires sharing the assets with a web application. We do support linking of resources from different locations to create a Cordova based mobile application. Although I do not recommend using artifacts, let alone whole web sites, that were created for desktop to be turned to mobile applications, but it helps to know that your tools are capable when it gets desperate.

While JBoss Forge has been included in JBoss Tools and Developer Studio for a while now, the recent JBoss Tools 4.2 and Devloper Studio 8.0 releases contain support for Forge 2.12.1. Forge has now become a mature component inside JBoss Tools and Developer Studio with a plethora of available commands that can be executed either using the convenient wizard style or using the integrated Forge console.

Wise Wizards

To use the wizards, you need to issue the Ctrl+4 key combination (or Cmd+4 on a Mac). It will bring up a popup containing all the commands that are available in the currently selected context.

If this key combination does not work, chances are high that you are using a keyboard layout such as AZERTY. Don’t panic, in this case it is just a matter of redefining the key combination to something that works on your hardware. Use the Eclipse preferences dialog (Window→Preferences or something similar) to do this.

Selecting the 'Project: new' entry of the popup will open the Forge wizard that allows you to create a new project.

Core Console

If you are a console afficionado and typing and code completion is more your thing, you can use the integrated Forge console. One way to bring up the console is to type 'Forge Console' in the 'Quick Access' text field in the toolbar of your Eclipse workbench and then select the 'Forge Console' entry that is visible in the popup.

Another way would be to select 'Window→Show View→Forge Console' from the main menu bar. This will only be possible when you are using the 'JBoss' perspective. In another perspective, you can use 'Window→Show View→Other…' and then navigate to the 'Forge→Forge Console' entry.

In the console you can type Forge commands to perform the same tasks as if you were using the wizard-style approach.

Chatty Cheatsheet

If you are new to Forge, this new feature will certainly help you on the way. And as a bonus it will also help you with learning to develop an HTML5 application with REST, CDI and AngularJS. You can open this brand new cheatsheet by importing the 'AngularJS Forge' example from the 'JBoss Central' page.

In case the 'JBoss Central' page is not open or you inadvertently closed it, no worries. You can always bring it back by clicking the 'JBoss Central' icon in your Eclipse toolbar.

After clicking the 'AngularJS Forge' example hyperlink, a wizard will guide you through the import process. Just accept all the defaults. When the wizard is done, a popup will ask you if you want to open the cheatsheet.

Make sure you keep the open option checked when you click the 'Finish' button. Now the cheatsheet will reveal itself in all its glory.

There is no point in repeating here all the information that is available in the cheatsheet but in short, it will provide you with some general information and then guide you through the development, deployment and execution of a HTML5 application. You will see different examples of using Forge commands such as REST endpoint generation and scaffolding an AngularJS user interface. Check it out!

Happy Forging,
Koen Aers
@koentsje

Burr Sutter recently recorded and uploaded a handful of screencasts on Hybrid Mobile Development Tools that we recently shipped in JBoss Tools 4.2.0.Final and JBoss Developer Studio 8.0.0.Final.

Those videos (totalling more than 1h15 of materials!) cover the following topics:

Sit back, grab your headphones and enjoy ;-)

Xavier
@xcoulon

In JBoss Tools and JBoss Developer Studio, we’re continuously working to augment the Maven integration experience in Eclipse. Some of the features we’ve been playing with, if deemed successful, will eventually be contributed back to m2e, like the Maven Profile Management UI. Others, more centered around JBoss technologies, will stay under the JBoss Tools umbrella.

JBoss Tools 4.2 and Developer Studio 8, based on Eclipse Luna, take advantage of all the nice improvements made to m2e 1.5.0 and then, add some more :

m2eclipse-egit integration

The Import > Checkout Maven Projects from SCM wizard doesn’t have any SCM provider by default, which can be pretty frustrating at times. With Git becoming the new de facto source control system, it only made sense to make m2eclipse-egit the sensible default SCM provider for m2e.

m2eclipse-egit will now be automatically installed when a JBoss Maven integration feature is installed from the JBoss Tools update site.

It is installed by default with JBoss Developer Studio 8.0.0 as well.

Maven Central Archetype catalog

Since m2e 1.5.0 no longer downloads Nexus Indexes by default, a very small, outdated subset of Maven Archetypes is available out of the box.

To mitigate that, the JBoss Tools Maven integration feature now registers by default the Maven Central Archetype catalog, providing more than 9600 archetypes to chose from, when creating a new Maven project. Accessing the complete list of archetypes is even way, waayyyy faster (a couple seconds) than relying on the old Nexus index download.

Pom properties-controlled project configurators

JBoss project configurators for m2e now support an activation property in the <properties> section of pom.xml. Expected values are true/false and override the workspace-wide preferences found under Preferences > JBoss Tools > JBoss Maven Integration.

Available properties are :

<m2e.cdi.activation>true</m2e.cdi.activation> for the CDI Project configurator,
<m2e.seam.activation>true</m2e.seam.activation> for the Seam Project configurator,
<m2e.hibernate.activation>true</m2e.hibernate.activation> for the Hibernate Project configurator,
<m2e.portlet.activation>true</m2e.portlet.activation> for the Portlet Project configurator.

The pom.xml editor also provides matching XML templates for these properties, when doing ctrl+space in the <properties> section.

Maven Repository wizard improvements

The Configure Maven Repositories wizard, available under Preferences > Jboss Tools > JBoss Maven Integration saw a couple improvements as well :

Advanced options for maven repositories

You can now choose the repository layout, enable/disable snapshots or releases, and change the update policy in the advanced section :

Automatically identify local Maven repositories

When adding a new Maven repository, you can scan for JBoss Maven repositories unzipped locally, with the Recognize JBoss Maven Enterprise Repositories… button, in order to automatically add it to your .m2/settings.xml.

The identification process now looks for a .maven-repository file at the root of the folder you selected. This file follows the .properties file format and is expected to contain up to 3 attributes :

repository-id : the repository id
name : a (descriptive) repository name. Optional, defaults to repository-id
profile-id : the profile id the repository will be activated from. Optional, defaults to repository-id

As a concrete example, the JBoss Mobile repository .maven-repository file would contain :

repository-id=local-jboss-mobile
name=JBoss Mobile Maven Repository
profile-id=local-jboss-mobile

What’s next?

Tired of seeing these "Project configuration is out-of-date" errors whenever you tweak your pom.xml? We’re currently playing with a plugin that will automatically do the Maven > Update project configuration for you. You can try a very alpha version from the following p2 repository : http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground_master/all/repo/. Let us know if/how it works for you, so we can decide what to do next with it.

Enjoy and see you soon!

Fred Bricon
@fbricon

Posts tagged with 'jbosscentral'

Installation

JBoss Developer Studio 8.0.1

JBoss Tools 4.2.1 and JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE)

What is new ?

BrowserSim and CordovaSim skins for iPhone 6 and 6 Plus

OpenShift Explorer: Start and Stop Applications

Arquillian validator for not public/static deployment method

CDI auto enablement for Java EE 7 projects

Updated Forge 2 Runtime

What is Next

Background

Results

Comments

Conclusion

User story

Pre-requisites

Configure a new dev profile

Conclusion

Overall features

Make your voice heard

Tern.java Adapter for JavaScript Facet

ECMA5 Support

Popular JavaScript Frameworks Support

CordovaJS Module for Tern.java

AngularJS Tools Early Access

Where are the tools?

1. Start a new Cordova project

2. Import your existing Cordova application

3. Use existing mobile web site code

Wise Wizards

Core Console

Chatty Cheatsheet

m2eclipse-egit integration

Maven Central Archetype catalog

Pom properties-controlled project configurators

Maven Repository wizard improvements

Advanced options for maven repositories

Automatically identify local Maven repositories

What’s next?

Configure a new `dev` profile