You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Duncan Doyle (JIRA)" <ji...@codehaus.org> on 2009/01/08 13:43:19 UTC
[jira] Created: (MRM-1061) 'Used By' page incorrect and 'Dependency
Tree' page crash when specifying dependency version using
in parent POM.
'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
-----------------------------------------------------------------------------------------------------------------------------------------
Key: MRM-1061
URL: http://jira.codehaus.org/browse/MRM-1061
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.1.3
Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
Reporter: Duncan Doyle
In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
{quote}
org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
{quote}
Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Olivier Dehon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167476#action_167476 ]
Olivier Dehon commented on MRM-1061:
------------------------------------
One possible way of solving this would be to require that artifacts be built with an invocation of the help:effective-pom mojo, and Jar up the generated effective POM inside the artifact (like in META-INF/maven, alongside the actual pom.xml), or maybe attach the generated effective POM file to the project so that it gets deployed alongside the main artifact.
If present, Archiva could then exploit the effective POM information to generate its index and DB info.
If not present, then the behavior would remain the same as today...
My $.02
-Olivier
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Reiner Saddey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177548#action_177548 ]
Reiner Saddey commented on MRM-1061:
------------------------------------
The technical process of indexing is not an end in itself. So what does Archiva index for?
The Maven repository format is self contained and does not require any additional indexing for clients to successfully retrieve or browse artifacts. Indeed Maven build processes accept file system based repositories (and even create them on their own as well within ~/.m2/repository).
Basically, indexing is a way to prepare information in advance, that would otherwise be time consuming to compute on demand. Where could this demand stem from? Besides some internal processes within Archiva (possibly for efficiently implementing automatic purges or repository groups, aka virtual repositories) it's humans (or continuous build systems), that benefit from structural information, such as 'Used By' and 'Dependency Tree'.
For 'Used By' and 'Dependency Tree' we would like to have two choices to derive information from:
1. Dependencies as stated in the pom.xml of an artifact
2. Dependencies as having been interpolated during the actual build of an artifact
However, alternative 2 requires comprehensive access to the information that has been used within the reactor at the time it was performing the actual build of an artifact. To my knowledge, as of now, Maven does not specify a format that would describe how this information should be bound or incorporated within the pom.xml that results from a Maven build.
If this additional information were supplied in a non-agreed-upon way, any dependency tree would be bound to be very small and incomplete, showing nodes whose vertices are unknown, as the nodes most probably would lack the additional information that would be required to complete the tree (e.g. most, if not all, artifacts present within repo1.maven.org).
In order to be of relevant use, alternative 2 cannot be implemented in a local fashion, but instead requires cooperation that is far beyond the reach of any artifact repository manager that solely accepts what has been produced by Maven, Hudson or Continuum. It's only them builders and the data they provide who can help us understand what and how they were doing while producing an artifact.
In the meantime we should stick to alternative 1 and try to extract information from the pom.xml in a way that reflects its semantics as truly as possible. In my opinion, Gwen's suggestion appears to fit the bill for now.
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Olivier Dehon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177552#action_177552 ]
Olivier Dehon commented on MRM-1061:
------------------------------------
Indexing/Searching is one of most important features for which I use Archiva. It provides the ability for a developer to retrieve artifacts based on method names, package names, dependencies used, ... If it were working properly, it would also allow to perform impact analysis, report statistics on shared components usage... Possibilities are endless.
The simple (and common) case where dependency versions are defined in the dependencyManagement section of the parent pom is enough to render the search feature useless, let alone when dependencies themselves are dependent on the activation of a profile.
I don't understand why using the output from help:effective-pom cannot be agreed upon... After all, it is a pom also. Even better it is *the* pom.
I wonder how Nexus deals with this...
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1061) 'Used By' page incorrect and 'Dependency
Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1061:
------------------------------
Fix Version/s: 1.x
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Reiner Saddey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177476#action_177476 ]
Reiner Saddey commented on MRM-1061:
------------------------------------
I'd rather prefer Archiva do the effective pom stuff itself (or anything equivalent in order to properly interpret a maven 4.0.0 model version pom), because...
1. in my opinion, supplying additional hints to Archiva within a maven project in a non-standard way would be a plain no-no
2. it would be hard to modify existing external maven projects - and doing so would inevitably lead to chaos and confusion
Maybe Archiva should integrate emerging dependency tools (e.g. http://code.google.com/p/q4e/wiki/DependencyGraphViewer) instead of creating one of its own.
Last-not-least I wonder, whether it would be cleaner and easier to separate concerns, i.e. let the repository manager just do its archiving task and use a universal viewer that can be used with any repository manager. At first I thought that there's something missing from other repository managers. Now, when I come to think of it, it might turn out not to be a bug, but a feature instead.
Just my thoughts,
Reiner
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-1061) 'Used By' page incorrect and 'Dependency
Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1061.
-----------------------------
Resolution: Fixed
Assignee: Brett Porter
fixed with changes in trunk
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Assignee: Brett Porter
> Fix For: 1.4
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1061) 'Used By' page incorrect and 'Dependency
Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1061:
------------------------------
Fix Version/s: (was: Backlog)
1.4
for testing
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.4
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Olivier Dehon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177542#action_177542 ]
Olivier Dehon commented on MRM-1061:
------------------------------------
We are talking about the indexing facility of Archiva, not viewing or archiving. The only way for any indexing tool (Archiva or external standalone indexer) to have the relevant information that was used at build time is to have access to the effective pom that was used to build the artifact.
The effective pom is not just additional hints, it is the actual build setup for that version of that artifact, and it seems fairly standard to me.
Maybe even the Jarring-up of the effective pom could be a nice enhancement to the Archiver(s) that Maven uses to construct the Jars/Wars/Ears... helping understand what the actual environment was when the artifact was built.
YMMV... -Olivier
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1061) 'Used By' page incorrect and
'Dependency Tree' page crash when specifying dependency version using
in parent POM.
Posted by "Gwen Harold Autencio (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164538#action_164538 ]
Gwen Harold Autencio commented on MRM-1061:
-------------------------------------------
The cause of this issue is that the effective pom is not loaded.
http://jira.codehaus.org/browse/MRM-731 may be related.
Thanks.
> 'Used By' page incorrect and 'Dependency Tree' page crash when specifying dependency version using <dependencyManagement> in parent POM.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1061
> URL: http://jira.codehaus.org/browse/MRM-1061
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.3
> Environment: Debian GNU/Linux (unstable), Apache Tomcat 6.0.18
> Reporter: Duncan Doyle
> Fix For: 1.x
>
>
> In our projects we specify the versions of artifacts/dependencies in a parent POM using the <dependencyManagement> mechanism. This enables us to easily specify the version of an artifact to be used for all the modules in our project. However, when looking at the 'Dependencies' page of such a module in Archiva, the versions of the dependencies are not listed. Furthermore, when opening the 'Dependency Tree' screen, it crashes with the following error:
> {quote}
> org.apache.maven.archiva.common.ArchivaException: Unable to generate graph for [com.fortis.fffj:FFFJ-Integration:1.1.1-20090105.220705-5] : Unable to create ArchivaArtifact with empty version [junit:junit:null::pom]
> {quote}
> Another problem, that is probably a result of this issue, is that when looking at an artifact's 'Used By' page (for example JUNIT), the page does not list the modules that use the artifact if the artifact's version is specified in the modules parent POM using the <dependencyManagement> mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira