Monday, 31 March 2014

Rapid Bootstrap CDN Support in NetBeans

I've just published a NetBeans 8 plugin that allows developers to quickly add links to Bootstrap CSS (hosted by into their .xhtml files.

Once installed, the plugin is appears on the "Insert Code..." dialog within .xhtml files.
Selecting the "Bootstrap CDN..." option causes the Bootstrap version selector dialog to be displayed.
Select a version of Boostrap CSS to be linked to and press the "OK" button and a link will be added into the file, e.g.

<link href="//"

The .NBM can be downloaded from GitHub along with the full source code.

Let me know if you find this useful or if you find any bugs in the plugin.

Monday, 24 March 2014

Unable to start WildFly from NetBeans ?

NetBeans 8 provides native support for WildFly 8.
Sometimes however, WildFly can fail to start from within NetBeans.
In these instances, the following error is displayed within the NetBeans "WildFly Application Server" output window.
Calling "C:\DevTools\wildfly-8.0.0.Final\bin\standalone.conf.bat"
| was unexpected at this time.
This error has been reported as NetBeans error 242661.
To get around the problem, bring up the server properties for WildFly (right click on WildFly in the services tab and choose Properties).  On the platform tab, uncheck the "Use IDE Proxy Settings" option and then restart NetBeans.

You should now be able to start/stop WildFly directly from within NetBeans.

Monday, 17 March 2014

Creating Maven Projects For WildFly

The JBoss/WildFly way to configure Maven projects makes developing Java EE 7 applications with WildFly very straightforward.

Configuring a project to use the JBoss Java EE 7 Bill Of Materials (BOM) removes the difficulty of specifying what version of dependencies are required as these are already defined within the BOM.

So, to configure a WildFly project, we need to first define the BOM in the project's pom.xml file.



Once we've defined the BOM, we can easily add Maven dependencies without worrying about versions.


Simple !

Friday, 14 February 2014

Is Maven 2 about to be EOL'ed?

In the Maven mailing list,Stephen Connolly has posted a question, should we "declare Maven 2.x as end of life".

He states:
We have not made a release of Maven 2.x since 2.2.1 which was August 2009. During that period no release manager has stepped up to cut a release. I would argue that we should just therefore just declare Maven 2.x as end of life.

At the time of writing, most votes are agreeing with Stephen implying that the end of Maven 2 may be coming soon.

Have you upgraded to Maven 3, or are you still using Maven 2?  Is it a good thing to eol Maven 2?  Add your thoughts in the comments below.

Don't forget to read Stephen's full thread for all the details.

Thursday, 13 February 2014

The new Eclipse logo

In a blog post today, Ian Skerrett has announced the new logo for Eclipse.
Last fall we [The Eclipse Foundation] started a process to update the Eclipse logo. The existing logo had not been change since Eclipse was launched and it was showing its age. I am happy to announce we have finished the process and am pleased to introduce the updated Eclipse logo.

The new logo has a fresh modern look to it, which I think is a good improvement and will stand Eclipse in good stead for the future.

The new logo will be included with the next Eclipse release train, Luna, and gradually rolled out across the Eclipse site and projects.

What do you think?  Do you like the new logo?  Add your comments below.
© doobries domain
Designed by BlogThietKe Cooperated with Duy Pham
Posts RSSComments RSS
Back to top