[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15663 at 10/14/13 9:46 AM:
--------------------------------------------------------------------
The important fixes included from master are:
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Enhancement JBIDE-14856: Allow users to remove several connections at once
* New Feature JBIDE-12574: support multiple domains in OpenShift tooling
was (Author: adietish):
The important fixes included from master are:
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Enhancement JBIDE-14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2797:
--------------------------------------
The laucher/JDK issue is specific to Mac and was fixed for Kepler SR1: https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361
It looks like the update mechanism doesn't update the launcher path in the .ini file. I'm not sure what would be the correct behaviour regarding launcher during update.
Anyway, if it is a bug, it is on Eclipse side.
About the discovery path, it looks a bug to me. Needs to verify what is the value in a "vanilla" JBDS to see whether it affects all 7.0.1 or just the installation scenario described on forum.
> .ini upgrade issue for 7.0.1 users
> ----------------------------------
>
> Key: JBDS-2797
> URL: https://issues.jboss.org/browse/JBDS-2797
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.0.1.GA
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
>
> User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation.
> The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior.
> Worrisome issues are:
> development url used in GA update:
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> startup/launcher directories are hardcoded in the .ini file:
> -startup
> ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
> --launcher.library
> ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835
> Have these been forgotten/set wrong in the update or is this some specific update path that is failing ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Radoslav Rábara commented on JBIDE-15304:
-----------------------------------------
I am not able to reproduce this issue. Please, provide some another information like steps to reproduce or new log to verify if the issue was resolved. Thank you.
> NullPointerExceptions in JAX-RS doesn't report what project is affected
> -----------------------------------------------------------------------
>
> Key: JBIDE-15304
> URL: https://issues.jboss.org/browse/JBIDE-15304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> I've seen this exception happens many times when I have several projects imported out of JBoss Central:
> {code}java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69)
> at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178)
> at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114)
> at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136)
> at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105)
> at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406)
> at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
> {code}
> couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15661) new application wizard: switches from new to existing application when I change the domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15661?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15661:
-------------------------------------
Steps to Reproduce:
# ASSERT: have a connection with 2 domains (ex. foobarz and foogoo) and at least 1 application in both
# EXEC: launch new application wizard and provide some new application name
# EXEC: switch the domain in the domain-combo
Result:
Existing appliaction checkbox is checked and existing application named filled in with the first application that's present in the domain you switched to.
Expected:
Switching the domain should not change from new application to existing application
was:
# ASSERT: have a connection with 2 domains (ex. foobarz and foogoo)
# EXEC: launch new application wizard and provide some new application name
# EXEC: switch the domain in the domain-combo
Result:
Existing appliaction checkbox is checked and existing application named filled in
Expected:
Switching the domain should not change from new application to existing application
> new application wizard: switches from new to existing application when I change the domain
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-15661
> URL: https://issues.jboss.org/browse/JBIDE-15661
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15663 at 10/14/13 9:20 AM:
--------------------------------------------------------------------
The important fixes included from master are:
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Enhancement JBIDE-14856: Allow users to remove several connections at once
was (Author: adietish):
The important fixes included from master are:
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15663 at 10/14/13 9:19 AM:
--------------------------------------------------------------------
The important fixes included from master are:
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
was (Author: adietish):
The important fixes included from master are:
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15663 at 10/14/13 9:18 AM:
--------------------------------------------------------------------
The important fixes included from master are:
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
was (Author: adietish):
The important fixes included from master are:
* Enhancement JBIDE-15081: Unknown errors are now not displayed in all details any more. User is told about an unknown error and told to inspect the Eclipse logs
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15663 at 10/14/13 9:15 AM:
--------------------------------------------------------------------
The important fixes included from master are:
* Enhancement JBIDE-15081: Unknown errors are now not displayed in all details any more. User is told about an unknown error and told to inspect the Eclipse logs
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE-14856: Allow users to remove several connections at once
was (Author: adietish):
The important fixes included from master are:
* Enhancement JBIDE-15081: Unknown errors are now not displayed in all details any more. User is told about an unknown error and told to inspect the Eclipse logs
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE 14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15663) merge master into jbosstools-4.1.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15663?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15663:
------------------------------------------
The important fixes included from master are:
* Enhancement JBIDE-15081: Unknown errors are now not displayed in all details any more. User is told about an unknown error and told to inspect the Eclipse logs
* Fix JBIDE-15200: informing user when creating a new application timeouted
* Enhancement JBIDE-15161: Warn user if he wants to embed phpmyadmin into a scalable app or switchyard into a non-jboss cartridge
* Enhancement JBIDE-10939: "New Connection" is now available in the context-menu (not in the toolbar any more)
* New Feature JBIDE-15319: Allow users to configures markers from project context-menu
* Fix JBIDE-15261: creating application from source will now fully work (was failing with timeout issues and because of embedded cartridges only being added after creation)
* Enhancement JBIDE 14856: Allow users to remove several connections at once
> merge master into jbosstools-4.1.x
> ----------------------------------
>
> Key: JBIDE-15663
> URL: https://issues.jboss.org/browse/JBIDE-15663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> In order to be able to deliver the latests new features, that are requested by our customers, in JBDS 7.1 we need to merge master (jbosstools-4.2.x) into the maintenance branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ]
SBS JIRA Integration updated JBDS-2797:
---------------------------------------
Forum Reference: https://community.jboss.org/message/840331#840331
> .ini upgrade issue for 7.0.1 users
> ----------------------------------
>
> Key: JBDS-2797
> URL: https://issues.jboss.org/browse/JBDS-2797
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build, installer
> Affects Versions: 7.0.1.GA
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Critical
>
> User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation.
> The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior.
> Worrisome issues are:
> development url used in GA update:
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> startup/launcher directories are hardcoded in the .ini file:
> -startup
> ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
> --launcher.library
> ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835
> Have these been forgotten/set wrong in the update or is this some specific update path that is failing ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months