1 2 3 Previous Next


40 posts

We're proud to announce new feature 'Social Log In and Sign Up' for jboss.org website released few days ago.


It allows you to use your Google, GitHub, LinkedIn, Facebook and/or Twitter account to create a new jboss.org user account. You can also link these accounts to your existing jboss.org account.

The linking allows you to login to jboss.org website later without entering other password if you are logged in on Google for example. You can simply resolve "I forgot jboss.org password" cases also, by logging in over linked account and changing jboss.org password then.


You can find Social provider icons directly on jboss.org login page and use them for Log In or Sign Up.



If social account is not linked with any jboss.org account yet, you can do that via next screen allowing you to link it with your existing jboss.org account or create a new one.

Registration form is prefilled by name and email obtained from your social account to save your work a bit.



Later you can manage your Social accounts links from jboss.org user profile page.



Based on statistics this new feature is very useful since aprox. 30% of newly created jboss.org user accounts are created over it now. Google provider is the most popular one, making over three quarters of all uses. Facebook provider is second well ahead of other providers.


I'm pleased to announce new feature in jboss.org forums.


You can reply to the forum's e-mail notification directly in your e-mail client.


Here's how it works:

  1. Someone posts a discussion message (either a new thread or a reply to an existing one).
  2. The forums sends email notifications to those people who have requested them.
  3. After reading the content of the post in the notification email, someone replies to the notification email with their response (taking care not to delete the token in the subject line).
  4. Forums parses the e-mail and locates the discussion thread to which the reply belongs and posts the reply to the community.


Note that this feature supports only discussion replies -- posts of new content and replies to other kinds of content aren't supported.



"comment by email" feature has been enabled for jira running at issues.jboss.org during today's outage.

It means you can reply to a notification email received from jira, and your text will be added as comment for the issue received email was about.


"Add a comment from the non quoted email body" handler is used. This message handler creates a comment, but only uses the 'non quoted' lines of the body of the email message. A quoted line is any line that starts with a '>' or '|' symbol and such lines of text will not be added to the comment. The issue to which the comment is added is chosen from the first issue key found in the email subject. The author of the comment is taken from the address of the email message's From: field. Messages from unknown email addresses are ignored silently.


As part of this task we have to change email address JIRA uses as From in emails to issues@jboss.org

You have to upgrade your "from JIRA" email filters if they depend on it.

Community Updates (aka Community Digest) are turned off by default from 13th of November, 2013.

It means that all users who have never changed their email preferences they'll not receive Community Updates.


If you'd like to turn it on back simply go to email preferences and change value of Community Digest field from "Never" to any other option e.g. Once-a-week summary.




Jboss Maven repository (repository.jboss.org) supposed to have three levels of users of staging profiles. Anonymous users had no rights to Nexus staging suite. A JBoss Developer group was supposed be able to deploy artifacts to staging group and a Productization group was supposed to be able to release and promote staging artifacts.


However for some historical reason the last two groups were merged together allowing the developer group to be able to release and promote artifacts as well.


After the server upgrade today, these two groups will be distinguished again. So that means it is possible it may affect your work - it did not matter, if you had been  just in the "JBoss Developer" group before, but if so and you need to release or promote staged artifacts, you need to ask me (e-mail to help(at)jboss.org) and your project leader (to confirm your privilege).

Right now anonymous users have read access to all the artifacts on this server. This policy is about to be changed. The old repositories, that were accessible will remain accessible for anonymous users in future and also some other repositories will be added.


However some of the new repositories will not be accessible for general public (they will contain immature testing stuff). Why am I writing about a change, that most of the people will not even notice?


The thing is I might have missed something. If you want to know if your project will be OK, you can try to build it using  "jboss-anonymous" account (password "anonymous") instead of the anonymous access. If it fails due to missing rights, please, report the issue here.



     We've released a new theme for project pages deployed on jboss.org domain. It's based on Bootstrap v.2.3.1 on top of which our JBoss Community theme is applied. To make the theme as easy to start with as possible, we've developed an Awestruct site project https://github.com/jbossorg/bootstrap-community which can be forked on github and used as a starting point for any jboss.org project site. Thanks to this project you gain all the needed configuration done together with layouts, custom Awestruct extensions and the theme itself applied. If you're interested to see how it looks live after it's built and deployed, click on the screenshot below.




For more information on how to start with your jboss.org project site please refer to README.md file of the github project.



now you can send documentation pages from Confluence running at https://docs.jboss.org/author to your Amazon Kindle reader.



This feature was introduced over new Confluence to Kindle plugin.



during jboss.org JIRA outage last week we introduced new plugin called JIRA DVCS Connector for Bitbucket and GitHub.

This plugin allows to directly show commits from Github repositories on JIRA issue page, with links pointing back to the Github directly. So it's not necessary to use FishEye at source.jboss.org anymore for this kind of functionality.


New "Commits" tab is shown on issue detail page. It contains informations about GitHub commits with key of the issue mentioned in the commit message.


Plugin allows JIRA issue transitions directly from a Github commit message also.


JIRA DVCS connector plugin uses Github web hooks to propagate commits into JIRA immediatelly, which brings small restriction into process of connection.


Project lead, who wants to link his project's Github repository with JRA, must follow next steps:

  1. Repository must be owned by github "Organization", personal repositories can't be linked
  2. jboss-jira-hook github user must be added into the organization's Owners group. Jira needs this to add webhooks.
  3. then you have to contact jira administrators to add repository into JIRA configuration. You have to specify which Github repositories do you want to add (all owned by some Organization, or few named only), and if you want to allow automatic JIRA issue transitions from a Github commit messages.



jboss.org JIRA instance has been updated last Thursday to bring you latest version of JIRA and GreenHopper, as you can see in release notes.


JIRA upgrade from 5.2.5 to 5.2.7 brings mainly few bugfixes, no any significant change for users was introduced here.


GreenHopper upgrade from 6.1.1 to brings few new features, for example:

  • Search for Issues by Epic Name
  • Search for Sprint by Name
  • Add more Fields to the Issue Detail View
  • Create Issue when viewing an Epic in JIRA

You can find links to complete release notes for all new versions in ORG-1616.


Two new plugins was introduced also. Separate blogpost will be published for both of them later to introduce what they bring for users.



a few weeks ago we configured jboss.org JIRA instance (issues.jboss.org) to allow remote linking of issues with Hibernate JIRA (hibernate.onjira.com) and Apache JIRA (issues.apache.org/jira). This feature allows better linking of issues with upstream/downstream project issues. Linking with Hibernate JIRA is bidirectional, so you can link from Hibernate JIRA issues to jboss.org issues too. Linking with Apache jira is possible from jboss.org JIRA only,  linking is not configured on Apache jira side.


The feature is available from common jira issue Link action. Linking dialog now contains new field called "Server", where you can specify JIRA server you want to link issue from. Then you can directly type in issue key from selected server, or search issue against the server.


Details about JIRA remote issue linking are available in JIRA documentation.

jboss.org JIRA instance has been updated this Wednesday to bring latest version of JIRA and other installed plugins and some bugfixes as you can see in release notes.



JIRA point upgrade from 5.2 to 5.2.5 brings mainly bugfixes and performance improvements. One noticeable change is move of reports from dropdown menu to the panel on the Project Summary page, so they are more accessible now.




GreenHopper has been upgraded from 6.0.8 to 6.1.1 which brings few new features and enhancements. Main enhancement is introduction of Epics, which provide you with an additional hierarchy of story management, providing planning guidance for groups of issues within, or across, projects. For details see 6.1 and 6.1.1 release notes.


Balsamiq Mockups

Balsamiq Mockups plugin for JIRA has been upgraded from 2.2.2 to 2.2.4 which brings support for linking to web addresses (URL's) in all controls that support linking and other improvements and fixes. See relese notes for full list of changes.

Pages like http://www.jboss.org/gatein/downloads/gateinportal.html or http://www.jboss.org/drools/downloads use a nice "Directory listing" paragraph. This paragraph mirrors a file system and keeps the download pages up-to-date without the actual page to be manually updated. This paragraph was introduced by Jozef Chocholáček, but in the next release (= 7.8.0 Magnolia) several enhancements and  fixes were done. The release will go public on Wednesday December 5th at 2:00 PM (CET).


Latest release hightlight

This feature was present in the previous version, but it was completely overhauled. It is backwards compatible thought. You can place a hightlight to the new version of your product between the paragraph title and the directory listing. Originally the highlight text was hard-coded to "Looking for the latest version? Download". Now it is just a default text, but you can change it to whatever you want. Also originally it was possible to higlight just one link, now it is up to you how many of them you want to use.


How to set this up? First of all you need to have a file lastRelease.properties in the root directory of your project. If this file is found, it is not displayed in the paragraph, but its content is parsed and used to set the content of the paragraph instead. Why are those settings in the filesystem and not in the Magnolia paragraph dialog? It is likely the latest versions are generated and deployed by some automatic process. And while it is easy to just copy one more file to some directory, it would be much harder to modify things in a web form automatically.


OK. So we have this lastRelease.properties file. It is a classical property file, where on each line you write a key, "=" character and after it its value. The lastRelease.properties has following keys:



lastReleaseA link to the page with the last release. The URL can be either absolute (in that case no processing is done on it) or relative. If it is relative a base URL is added to the link (in case of JBoss pages it is http://downloads.jboss.org). If this key is missing, the latest release will not be highlighted and just the directory listing will be displayed in the paragraph.
lastReleaseTextIf ommited, this key defaults to "Looking for the latest version? Download ". If you specify it, your text will be displayed prior to the link on the web page.
lastReleaseURLTextWhile lastRelease specifies the URL to the latest release, the path might not be pretty for human readers. Therefore you can specify a text, that will be displayed in the web browser. If ommited, the paragraph tries to dig some pretty name from the lastRelease value, but the result will not be as nice as if you specify it yourself.


If you need more links to the latest versions (i.e. your project has several parts and you want to highlight each part), now you can add numbers to the key after the name starting with 0 and increasing by one in the lastRelease.properties file.  The paragraph will render all the highlights unless finds a missing number. So if you specify lastRelease0, lastRelease1 and lastRelease3 keys, the first two will be displayed, but lastRelease3 will be ignored, because lastRelease2 is not present.


The keys lastReleaseText and lastReleaseURLText have their numbered variants and of course the number binds all together. However the defaults are slightly different here, because the long texts are not good if used several times:


lastRelease<n>A link to the page with the last release. If ommited, lastRelease<n+1> and the higher will not be processed.
lastReleaseText<n>The text prior to the link.It defaults to lastReleaseURLText<n> with ": ". If neither lastReleaseURLText<n> is specified, the default value of lastReleaseURLText<n> + ": " is used.
lastReleaseURLText<n>Similar to the unnumbered lastReleaseURLText.




lastReleaseText=Download the newest version here:

lastReleaseURLText=Latest Release



lastReleaseText1=Latest release 1:


lastReleaseText2=Latest release 2:



Will render as


What you can not see on the picture are the values of the links. So the first link (under Latest Release) will be  as http://absolutepath.some.org/dir/subdir, because the path was absolute and therfore unchanged. The second highlight is not nice, because lastReleaseText0 and lastReleaseURL0 were not specified and latest0: latest0 is the best what the paragraph was able to dig out from it. The URL under latest0 will be http://downloads.jboss.org/latest0, because the link is relative. The remaining two highlights are better, because the values are specified.


Note: the numbered and unnumbered keys are independent. You can use just numbered, just unnumbered or both variants.


Enough about the last release highlights. I need to explain some other new feature before I will be able describe some magic you can do with those highlights.


More directory listing paragraphs on a single web page


The old directory listing paragraph was supposed to be alone on a web page. Also it interfered with another Magnolia paragraph, but it is another story. It was not mentioned anywhere, so some users put several directory listing paragraphs on a single page. When someone navigated within the directory structure displayed in the paragraph, that paragraph displayed the content of the chosen subdirectory (correct), but the other paragraphs reported errors, because they tried to search for the same subdirectory in their part of file system, but they did not have it.


Now the navigation is independent in each paragraph. Originally "dir" attribute was added to the URL of the download page. E.g. http://localhost:8080/exampleformpage.html?dir=java caused the paragraph to render the content of the "java" directory. Now it changed. The dir attribute now holds the identification of the paragraph. I.e. if we have two paragraphs on the single page, the URL might look like http://localhost:8080/author/exampleformpage.html?dir=01%3Ddownloads%3B00%3Djava%3B. The URL says, that in the  paragraph 01 downloads subdirectory should be displayed and the paragraph 00 should display the java subdirectory. It looks horrible, but %3D is "=" and %3B is ";". So if you hover your mouse above the link in your browser, you will see something like http://localhost:8080/author/exampleformpage.html?dir=01=downloads;00=java; . I think that makes things clear.



The promised "directory listing magic"

In case you know how the dir parameter works, you may use this knowledge to construct the URL to your "latest release highlight" section. And if I speak about this feature as "latest release", the reason why you have it there may be completely different. I.e. if you have a project with several logical parts - one with a validation, second with a persistence or whatever.


The easiest way how to use it is to find the directory with the content you would like to highlight in the web browser. Copy the link and use it into your lastRelease.properties file. Keep in mind that that way you can set all the directory listing paragraphs of a single page.



Complete list of directoryListing paragraph changes in the new version


(just in the case someone cares).


- fixed crashes when serveral directoryListing paragraphs were on the same page

+ when date is selected as a sorting column, a file name is a secondary column

- fixed a problem with broken colors after sorting in directoryListing paragraph

- removed several possibilities to crash directoryListing paragraph by adding wrong paths

+ if more than just one directoryListing paragraph are present on a page, user can navigate independently in each. The system rembers the position in each paragraph instead of displaying an error

- fixed a problem with expanding of checksums of files, that have the same checksum (a completely different div on the page was expanded)

* newer version of Modeshape library is used

+ added some info about how to use the paragraph into Magnolia form of the paragraph.

- fixed a problem with spaces in the latest release highlight links.

Hi all,


new integration point for JBoss Community systems is here as I promised last week. It's based on feature request ORG-1560 and allows you to display build results from Jenkins instance running at the hudson.jboss.org on the issues.jboss.org hosted JIRA dashboard or on some pages of community.jboss.org.

Displaying build status on JIRA Dashboard

If you want to display build status on jira dashboard, simply login to JIRA and display your dashboard (you have to create your personal dashboard if not created one yet and use only default dashboard). Then use "Add Gadget" button at top right, select "Other" group in "Gadget directory", and use "Add now" button for "Build Status" gadget.


Then you can close "Gadget directory" and configure gadget on dashboard to show selected build. Use small arrow button on top right of gadget window to open menu, and use "Edit" item here. Then you can put name of selected jenkins job into provided input field and "Save" it.


Page is reloaded and voila, build status for selected job is shown here.


Color around Job title is changing depending on status of last builds to provide you quick visual information. It can be green, yellow or red. Job title acts as link to the job page in Jenkins server. And there are links to the latest, latest successful and latest stable builds of given Job too.


If you want to monitor more jobs simply add other "Biuld Status" gadgets into Dashboard.

Displaying build status in community.jboss.org

Very similar process can be used to display build status in some pages of community.jboss.org system. It can be used on all pages with configurable layout as is Personal dashboard, Space main page, Group main page etc. 


Technical background

Build status displaying is based on Google Gadget technology, so in reality it can be used in each system/container supporting this technology. Gadget is hosted as plugin in JIRA, and uses Jenkins REST API to obtain build status information to be displayed.

If you want to use this gadget in another gadget container system, you can find URL to the Gadget definition xml file on JIRA "Gadget directory" page, it's https://issues.jboss.org/rest/gadgets/1.0/g/org.jboss.jira.plugin.build-gadgets:build-status-gadget/gadget.xml .


And finally, source code for this gadget is available at https://github.com/jbossorg/jira-jenkins-gadget





this week we performed upgrade of JIRA instance running at issues.jboss.org to fix some bugs and bring you few new features.

JIRA point version upgrade from 5.1.4 to 5.1.7 is about bugfixes only, but GreenHopper upgrade from 6.0.3 to 6.0.6 brings you something new as you can see in release notes:


We also continue to improve our community members experience, productivity and collaboration by better integration of distinct systems. Latest addition to this topic on JIRA side is automatick linking to the RedHat bugzilla, based on  ORG-1098 feature request.

Simly if you use something like BZ-12345 or BZ#12345 or Bug 12345 in JIRA issue descriptions, comments etc. it's automatically rendered as link pointing to the bug in RedHat bugzilla.

And we are working on more integrations in our systems, stay tuned ;-)



Filter Blog

By date:
By tag: