|
|||
|
The newsletter is early this month because we had some unusually good news to report — Cenqua team and products join Atlassian! Additional reading in this issue includes Bamboo security architecture, an OSGi plugin for Struts 2 and more. Happy reading!
|
||
|
We're really excited, not only because we've gained three fantastic products — products that assist us with our own software development — but also because almost the entire Cenqua team has moved into our new Sydney offices to continue developing and supporting their software. We've known the Cenqua guys for a long time, and on both a personal and professional level they're top notch. They've made some truly great products; by great we mean products that developers use because they add utility and value without creating more work. Read the details of the deal. Over the next few weeks and months, more content from the Cenqua website, including product documentation, will be ported over to the Atlassian site. In the meantime, please let us know what you think or if you have any questions.
|
||
|
In Bamboo 1.2, we introduced plan level permissions as a major feature. Already with an Acegi Security framework in place, we figured it was a natural extension to build our permissions framework on top of Acegi. Bamboo Security Architecture
|
||
|
Wanting this same functionality in Struts 2, but enhanced to support versioned transitive plugin dependencies (plugin A uses services from plugin B which uses services from plugin C) that are automatically resolved and verified at runtime, I wrote the first cut at an OSGi plugin for Struts 2. This plugin allows you to group your actions and services into different jars, namely OSGi bundles.
|
||
|
Confluence has a nifty feature in that if you go to a page that does not exist, Confluence will check the database to see if there might be some obvious pages you might want to see instead. These include, for example, pages with the same name in a different space, pages that used to be called by that name but have since been renamed, or pages that start with the name you entered (in case the name was truncated when someone sent you the URL). To stay good Internet citizens, this page is still served with a 404 HTTP status code. This way robots, caches and the like know there isn't really a page at that URL. Well, this feature has been broken on Atlassian's extranet for a while. If you go to a page that should return a redirect, you just get the generic error page instead. (CONF-8766)
|
||
|
One of my daily responsibilities is to look over the code that is checked into our JIRA source base. I look at every commit and check for any obvious mistakes, typos or things that can be instantly improved. I recently blogged internally about some minor findings. Some of these were not recent mistakes, rather the code that I recently touched (as part of changing some other parts in JIRA), the old code that exposed some of the caveats of Java that still live inside JIRA source base. I received a very positive feedback to my post. This blog post also sparked a discussion between developers (including developers from other teams). I would like to sum this discussion up and share it with you. In my post I suggested to use DateFormat class only locally. The reason behind it is that the implementation of DateFormat class is not thread-safe. As its JavaDoc states: "Date formats are not synchronized. It is recommended to create separate format instances for each thread. If multiple threads access a format concurrently, it must be synchronized externally."The problem with this class is that it has a state and if you have two or more threads calling methods on the same instance, you could get results you would not expect.
|
||
|
Last month, Atlassian hosted Sydney's Java User Group meeting at our new offices in Sussex St. We were lucky enough to see a presentation by Terence Parr, the author of Antlr, a well-known tool for language parsing, compiling and much more. Watch the presentation:
|
||
|
In addition to the big Cenqua acquisition, we have some smaller headlines: Atlassian T-Shirts User Groups
Looking for a sponsor for your JUG? Give us a shout!
|
||
|
Like the JIRA team, the Confluence team has a screen set up in the corner of the office so we can all keep an eye on the health of our Bamboo builds. Unfortunately we broke a lot of tests the other week, after a few major dependency updates. Since then we've been having a nightmare of a time getting all of the builds to stay green. Lateral thinking to the rescue!
|
||
|
Here are some blogs and sites we've been tagging on our company del.icio.us feed:
|
||
|
To all those who have built the site into what it is today, a heartfelt thanks! You are building something of immeasurable value to all wiki users.
|
||
|
Other ways to keep on top of what's happening at Atlassian: |
|||
Read or subscribe to our 
See what everyone's talking about on the Atlassian 
Get a