[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič closed JBIDE-13527.
-------------------------------------
Yes Brian, I agree. Generation SOAP message is working, this issue was fixed. Verified.
> [tester] freeze parsing wsdl
> ----------------------------
>
> Key: JBIDE-13527
> URL: https://issues.jboss.org/browse/JBIDE-13527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.2.Final
> Reporter: Alessio Soldano
> Assignee: Brian Fitzpatrick
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
> Attachments: jaxws-complex.war, threaddump.txt
>
>
> JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite.
--
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, 10 months
[JBoss JIRA] (JBDS-2481) JBDS 5.0.0 and 5.0.2 is able to recognize EAP 5.2 runtimes - but does not automatically create a corresponding server
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2481?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2481:
-------------------------------------------
[~ldimaggio] is this being requested to be released in 5.x stream ? users can use JBDS 6 or 7 now for this - or is this because SOA-P 5.2 tooling is not available on JBDS 6/7 yet ?
> JBDS 5.0.0 and 5.0.2 is able to recognize EAP 5.2 runtimes - but does not automatically create a corresponding server
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2481
> URL: https://issues.jboss.org/browse/JBDS-2481
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: runtime
> Affects Versions: 5.0.0.GA, 5.0.2.GA
> Environment: JBDS 5.0
> JBDS 5.0.2
> EAP 5.2
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Fix For: 5.x
>
> Attachments: JBDS_50_GA.png, Screenshot-12.png, Screenshot-13.png, Screenshot-14.png
>
>
> If an EAP 5.2 server installation is referenced (Preferences->JBossTools Runtimes), the runtime is correctly found by JBDS and listed as a runtime to be scanned at startup - but - the corresponding EAP 5.2 server instance is not automatically created. The user must create this server definition manually.
> JBDS 5.0.0, and 5.0.2 is able to both create the runtime and automatically create corrseponding servers for EAP 5.1 and EAP 6.0 - the issue seems to be limited to EAP 5.2
> JBDS 6.0.0 is able to both create the runtime and automically create corrseponding servers for EAP 5.1, EAP 5.2 and EAP 6.0
> See attached screenshots.
> (Thanks to Eric Schabell for finding this one!)
--
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, 10 months
[JBoss JIRA] (JBIDE-14807) Don't maven update the project on maven example project import, if not necessary
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14807?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-14807:
--------------------------------
Description:
Currently, after we import a maven project example, we run a maven update project right after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerably, taking almost 50% longer to create a project from central.
We should only trigger that project update if some "out of date" markers are actually added on the project.
was:
Currently, after we import a maven project example, we run a maven update project right after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerable, taking almost 50% longer to create a project from central.
We should only trigger that project update if some "out of date" markers are actually added on the project.
> Don't maven update the project on maven example project import, if not necessary
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14807
> URL: https://issues.jboss.org/browse/JBIDE-14807
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, project-examples
> Affects Versions: 4.1.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta2
>
>
> Currently, after we import a maven project example, we run a maven update project right after, to prevent some random m2e out-of-date red markers from popping up.
> That slows imports down considerably, taking almost 50% longer to create a project from central.
> We should only trigger that project update if some "out of date" markers are actually added on the 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, 10 months
[JBoss JIRA] (JBIDE-14807) Don't maven update the project on maven example project import, if not necessary
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-14807:
-----------------------------------
Summary: Don't maven update the project on maven example project import, if not necessary
Key: JBIDE-14807
URL: https://issues.jboss.org/browse/JBIDE-14807
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven, project-examples
Affects Versions: 4.1.0.Beta1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.1.0.Beta2
Currently, after we import a maven project example, we run a maven update project right after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerable, taking almost 50% longer to create a project from central.
We should only trigger that project update if some "out of date" markers are actually added on the 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, 10 months
[JBoss JIRA] (JBIDE-14806) concurrent modification in central proxy wizard list
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14806:
-------------------------------------------
Summary: concurrent modification in central proxy wizard list
Key: JBIDE-14806
URL: https://issues.jboss.org/browse/JBIDE-14806
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
not sure how I got it but I got this error:
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819)
at java.util.ArrayList$Itr.next(ArrayList.java:791)
at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.notifyListeners(ProxyWizardManager.java:260)
at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:105)
at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:44)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I *think* I had closed and reopened central again but not sure - the error took some seconds before it showed up.
--
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, 10 months
[JBoss JIRA] (JBIDE-14804) Uninstall from jboss central
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14804:
-------------------------------------------
Summary: Uninstall from jboss central
Key: JBIDE-14804
URL: https://issues.jboss.org/browse/JBIDE-14804
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: central
Reporter: Max Rydahl Andersen
since I can install from central, shouldn't we also provide an uninstall button for our connectors?
--
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, 10 months
[JBoss JIRA] (JBIDE-14803) eclipse CSS outling resulting in Null pointer exception
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14803:
-------------------------------------------
Summary: eclipse CSS outling resulting in Null pointer exception
Key: JBIDE-14803
URL: https://issues.jboss.org/browse/JBIDE-14803
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Reporter: Max Rydahl Andersen
EXECUTE: open screen.css from kitchensink mobile.
EXECUTE: double click on #members.row in outline
asssert: screen.css editor higlights members.row
what happens: multiple errors + dialogs logged with:
java.lang.NullPointerException
at org.eclipse.wst.sse.ui.internal.contentoutline.ConfigurableContentOutlinePage$5.getShowInContext(ConfigurableContentOutlinePage.java:444)
at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getContext(WorkbenchSourceProvider.java:418)
at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:484)
at org.eclipse.ui.internal.services.WorkbenchSourceProvider.updateActivePart(WorkbenchSourceProvider.java:445)
at org.eclipse.ui.internal.services.WorkbenchSourceProvider.getCurrentState(WorkbenchSourceProvider.java:134)
at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:684)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4163)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
at org.eclipse.swt.widgets.Shell.windowDidBecomeKey(Shell.java:2157)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5602)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:214)
at org.eclipse.swt.widgets.Widget.becomeKeyWindow(Widget.java:366)
at org.eclipse.swt.widgets.Shell.becomeKeyWindow(Shell.java:523)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5426)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSWindow.close(NSWindow.java:54)
at org.eclipse.swt.widgets.Shell.destroyWidget(Shell.java:797)
at org.eclipse.swt.widgets.Widget.release(Widget.java:1318)
at org.eclipse.swt.widgets.Control.release(Control.java:2848)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
at org.eclipse.jface.window.Window.close(Window.java:336)
at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:994)
at org.eclipse.ui.internal.statushandlers.InternalDialog.close(InternalDialog.java:710)
at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
at org.eclipse.ui.internal.statushandlers.InternalDialog.buttonPressed(InternalDialog.java:190)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4164)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4010)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3649)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
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, 10 months
[JBoss JIRA] (JBIDE-14798) html5-mobile app does not work out of the box on eap6/eap6.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14798?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-14798.
---------------------------------------
Resolution: Cannot Reproduce Bug
> html5-mobile app does not work out of the box on eap6/eap6.1
> ------------------------------------------------------------
>
> Key: JBIDE-14798
> URL: https://issues.jboss.org/browse/JBIDE-14798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
>
> took the html5 app.
> it deploys but on usage I get these errors:
> java.lang.IllegalArgumentException: JBAS016069: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named in deployment jboss-as-kitchensink-html5-mobile.war
> org.jboss.as.weld.services.bootstrap.WeldJpaInjectionServices.getScopedPUName(WeldJpaInjectionServices.java:96)
> org.jboss.as.weld.services.bootstrap.WeldJpaInjectionServices.resolvePersistenceContext(WeldJpaInjectionServices.java:61)
> org.jboss.weld.util.Beans.injectEEFields(Beans.java:687)
> org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:160)
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
> org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
> org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
> org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
> org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:293)
> org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:68)
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:608)
> org.jboss.weld.bean.AbstractReceiverBean.getReceiver(AbstractReceiverBean.java:77)
> org.jboss.weld.bean.AbstractProducerBean$AbstractProducer.produce(AbstractProducerBean.java:317)
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:307)
> org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:68)
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:608)
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:674)
> org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:134)
> org.jboss.weld.util.Beans.injectBoundFields(Beans.java:763)
> org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:772)
> org.jboss.weld.bean.SessionBean$SessionBeanInjectionTarget$1.proceed(SessionBean.java:179)
> org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
> org.jboss.weld.bean.SessionBean$SessionBeanInjectionTarget.inject(SessionBean.java:176)
> org.jboss.resteasy.cdi.JaxrsInjectionTarget.inject(JaxrsInjectionTarget.java:36)
> org.jboss.as.weld.injection.WeldEEInjection.inject(WeldEEInjection.java:78)
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:60)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.as.jpa.interceptor.SFSBPreCreateInterceptor.processInvocation(SFSBPreCreateInterceptor.java:46)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:145)
> org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:76)
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85)
> org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:135)
> org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:76)
> org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.createInstance(TransactionAwareObjectFactory.java:53)
> org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.create(NonPassivatingBackingCacheImpl.java:106)
> org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.create(NonPassivatingBackingCacheImpl.java:57)
> org.jboss.as.ejb3.cache.spi.impl.AbstractCache.create(AbstractCache.java:53)
> org.jboss.as.ejb3.cache.impl.SimpleCache.create(SimpleCache.java:69)
> org.jboss.as.ejb3.cache.impl.SimpleCache.create(SimpleCache.java:40)
> org.jboss.as.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptorFactory$StatefulComponentSessionIdGeneratingInterceptor.processInvocation(StatefulComponentSessionIdGeneratingInterceptorFactory.java:75)
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:280)
> org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:157)
> org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:153)
> org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:50)
> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133)
> org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
> org.jboss.as.naming.InitialContext.lookup(InitialContext.java:129)
> org.jboss.as.naming.NamingContext.lookup(NamingContext.java:215)
> javax.naming.InitialContext.lookup(InitialContext.java:392)
> org.jboss.resteasy.plugins.server.resourcefactory.JndiComponentResourceFactory.createResource(JndiComponentResourceFactory.java:53)
> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:210)
> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:536)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:513)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:125)
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
> org.jboss.tools.example.html5.util.JSONPRequestFilter.doFilter(JSONPRequestFilter.java:80)
> If I go and remove 'primary' name from persitence.xml it seems to deploy fine.
--
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, 10 months