JIRA projects
Currently JIRA contains a number of projects that relate in part to the JBoss projects listed on jboss.org:
JBoss.ORG Category | JBoss.ORG Project Name | JIRA Category | JIRA Project Name | JIRA Project Key | |
|---|---|---|---|---|---|
JEMS Projects | JBoss Application Server | JEMS | JBoss Application Server | JBAS | |
JBoss jBPM | - | JBoss jBPM | JBPM | ||
Hibernate | JEMS | Hibernate | HIBERNATE | ||
JBoss IDE for Eclipse | JEMS | JBoss IDE | JBIDE | ||
JBoss Cache | - | JBoss Cache | JBCACHE | ||
JBoss Transactions | - | JBoss Transaction Manager | JBTM | ||
Apache Tomcat | - | - | - | ||
JGroups | JEMS | JGroups | JGRP | ||
JBoss Rules | - | JBoss Rules | JBRULES | ||
Portal Projects | JBoss Portal | - | JBoss Portal | JBPORTAL | |
Portlet Swap | - | PortletSwap | SWAP | ||
JBoss Wiki | JBoss Labs Projects | JBoss Wiki | JBWIKI | ||
JBoss Forums | JBoss Labs Projects | JBoss Forums | JBFORUMS | ||
JBoss Blog | - | JBoss Blog | JBBLOG | ||
JBoss.ORG Projects | JBoss Seam | - | JBoss Seam | JBSEAM | |
JBoss EJB3 | JEMS | EJB 3.0 | EJBTHREE | ||
JBoss Web Services | - | JBoss Web Services | JBWS | ||
JBoss Microcontainer | - | JBoss MicroContainer | JBMICROCONT | ||
JBoss AOP | JEMS | JBoss AOP | JBAOP | ||
JBoss Remoting | - | JBoss Remoting | JBREM | ||
JBoss Collaboration Server | - | JBoss Mail | JBMAIL | ||
JBoss Messaging | JEMS | JBoss Messaging | JBMESSAGING | ||
JBoss IIOP | - | - | - | ||
JBoss Security | - | JBoss Security | SECURITY | ||
JBoss Web | - | JBoss Web | JBWEB | ||
JBoss Serialization | - | JBoss Serialization | JBSER | ||
JBoss ESB | - | JBoss ESB | JBESB | ||
JBoss Labs | - | JBoss Labs | JBLAB | ||
JBoss Profiler | - | JBoss Profiler | JBPROFILER | ||
JBoss JRunit | - | - | - | ||
Reporting Services | - | Reporting Services | JBREPORT | ||
Shotoku | JBoss Labs Projects | JBoss Shotoku | JBSHOTOKU | ||
JEMS Installer | - | JEMS Installer | JBINSTALL | ||
JBoss Federated SSO | - | JBoss Federated SSO | JBSSO | ||
Gravel | - | - | - | ||
Community Labs Projects | Kosmos | JBoss Labs Projects | Kosmos | KOSMOS | |
DavCache | JBoss Labs Projects | DavCache | DAVCACHE |
As you can see there are some discrepancies between the categorization of JBoss.ORG projects and their JIRA counterparts.
This reflects that fact that JIRA has previously been dealt with in a separate way to the jboss.org site and changes to the two have not been co-ordinated.
Extra JBoss.ORG projects
You can see from the table that there are 4 JBoss.ORG projects that don't have an equivalent JIRA project:
Apache Tomcat
JBoss IIOP
JBoss JRunit
Gravel
The Apache Tomcat project is actually hosted at http://tomcat.apache.org and as such should not be expected to have a JIRA project.
The others should have JIRA projects created to allow them to be managed in a productive way.
Extra JIRA projects
The following projects exist in JIRA but are not listed on JBoss.ORG:
JIRA Project | Description | |
|---|---|---|
Metajizer | A JBoss Labs Semantic Web Project | |
JBoss JMX | ||
README 1st - JBoss Project Template | A generic template for new JBoss projects. | |
Apache Project Integration Issues | Issues related to integration of Tomcat, Apache Httpd, mod_jk, apr and other Apache projects with JBoss | |
Documentation | ||
Javassist | Javassist (Java programming assistant) is a class library for editing Java bytecode in Java. | |
JBoss Admin Console | The JBoss Admin Console offers a user friendly interface that enables system administrators to setup services running on the JBoss platform. | |
JBoss AS Patches | The issues included in JBoss AS patches, released via the JBoss Operations Network. | |
JBoss Benchmarking | Benchmarking is an important aspect of the QA cycle. This project aims to develop tools, metrics and benchmarking methodologies for JBoss products. | |
JBoss Blog | The JBoss Blog portlet project. | |
JBoss Build System | The new build system. | |
JBoss Clustering | A cross cutting project encompassing clustering issues related to common clustering utilities and clustering layer integration. | |
JBoss Common | The JBoss Common project. | |
JBoss Genetic | Fast bridge between Java VM and .NET Runtime. | |
JBoss JAAE (JBoss Application Authorization Engine) | The JBoss JAAE Project - A subproject of JBoss Security. | |
JBoss jBPM BPEL | Web services orchestrator, compliant with the BPEL (Business Process Execution Language) standard, version 1.1 and 2.0. | |
JBoss jBPM GPD | This project is setup to track the Graphical Designer component intially setup under the JBoss jBPM top-level project. | |
JBoss Native | Portable Java VM interface to OS native code. | |
JBoss Reflex | Java Reflection bridge for obtaining reflective information about classes and object from outside VM. | |
JBoss XML Binding (JBossXB) |
Categorization
As JIRA offers only a single level of categorization it must be used to give the greatest added value.
For example there is little need to create a top-level JBoss.ORG category since the public face of the JIRA system is that it manages JBoss.ORG projects. This is why it is called the JBoss.org JIRA on the main page.
If internal projects are configured then these can be hidden from view by configuring the security accordingly.
If there are multiple JIRA projects that correspond to a single JBoss.ORG project then a category should be created to highlight the fact. For example:
Category | Project | |
|---|---|---|
Web | JBoss Web | |
JBoss Genetic | ||
JBoss Native | ||
JBoss Reflex | ||
Apache Project Integration Issues | ||
AOP | JBoss AOP | |
Javassist |
If any of the projects provide software or services for use by the other projects then these could be assigned to a group called 'Common':
Category | Project | |
|---|---|---|
Common | JBoss Build | |
JBoss Benchmarking |
If any of these projects are experimental then they should probably be in a category called 'Incubation' to make it clear that they haven't reached the status of a full JBoss.ORG project yet.
It should be apparent that the number of JIRA projects can be greater than the number of JBoss.ORG projects but each JBoss.ORG project should have a corresponding JIRA project (or category) and the categories should be as simple and logical as possible.
Comments