August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-614) Pressing <TAB> too many times chops off the “java” from “.java” resource completions

by George Gastaldi (JIRA)

George Gastaldi created FORGE-614: ------------------------------------- Summary: Pressing <TAB> too many times chops off the “java” from “.java” resource completions Key: FORGE-614 URL: https://issues.jboss.org/browse/FORGE-614 Project: Forge Issue Type: Bug Reporter: George Gastaldi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] (FORGE-654) Forge console for Eclipse cannot run git

by Burkay Gur (JIRA)

Burkay Gur created FORGE-654: -------------------------------- Summary: Forge console for Eclipse cannot run git Key: FORGE-654 URL: https://issues.jboss.org/browse/FORGE-654 Project: Forge Issue Type: Bug Reporter: Burkay Gur When tried to run the git command from the Eclipse Forge Console an error is returned saying that no program is found. And yes, I have added git into my PATH. git runs without problems from terminal as well as the terminal forge (not the eclipse one). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] (FORGE-656) "Did you mean ?" feature ignores alias commands

by George Gastaldi (JIRA)

George Gastaldi created FORGE-656: ------------------------------------- Summary: "Did you mean ?" feature ignores alias commands Key: FORGE-656 URL: https://issues.jboss.org/browse/FORGE-656 Project: Forge Issue Type: Bug Reporter: George Gastaldi Priority: Minor Fix For: 1.0.7.Final The "Did you mean ?" list shown when you type an invalid command does not show aliased commands, like: {code:java} alias "ll=ls -l" {code} And then you type L in lowercase, it currently displays: {code} ***ERROR*** No such command: l Did you mean any of these ? ls {code} but should display the aliased commands as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (FORGE-620) MovePlugin throws RuntimeError with relative paths

by George Gastaldi (JIRA)

George Gastaldi created FORGE-620: ------------------------------------- Summary: MovePlugin throws RuntimeError with relative paths Key: FORGE-620 URL: https://issues.jboss.org/browse/FORGE-620 Project: Forge Issue Type: Bug Reporter: George Gastaldi The following test case illustrates the bug: {code:java} @Test public void testMoveDifferentRelativeDirectories() throws Exception { initializeJavaProject(); getShell().execute("mv src/main/resources/META-INF/forge.xml src/test/resources/forge.xml"); assertTrue(getProject().getProjectRoot().getChild("src/test/resources/forge.xml").exists()); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (FORGE-2) 'mv' command does not function on directories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2?page=com.atlassian.jira.plugin.sy... ] George Gastaldi closed FORGE-2. ------------------------------- Assignee: Jose Donizetti (was: George Gastaldi) > 'mv' command does not function on directories > --------------------------------------------- > > Key: FORGE-2 > URL: https://issues.jboss.org/browse/FORGE-2 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: Jose Donizetti > Labels: Starter > Fix For: 1.0.6.Final > > > [forge-distribution] dist $ cd ~/Projects/ > [no project] Projects $ mv > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv > [source (of type org.jboss.seam.forge.resources.Resource)] > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv plugin-prettyfaces/ > [target (of type java.lang.String)] > [no project] Projects $ mv plugin-prettyfaces/ prettyfaces/forge-plugin > ***ERROR*** [mv] [UnknownFileResource] can have no children > [no project] Projects $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-626) The "Debugging Section" on Forge website should encourage the use of --debug

by George Gastaldi (JIRA)

George Gastaldi created FORGE-626: ------------------------------------- Summary: The "Debugging Section" on Forge website should encourage the use of --debug Key: FORGE-626 URL: https://issues.jboss.org/browse/FORGE-626 Project: Forge Issue Type: Patch Reporter: George Gastaldi Thanks to FORGE-556, it is possible to debug forge using the "--debug" flag. This should be encouraged on the Docs in forge.jboss.org -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
6
0 / 0

[JBoss JIRA] (FORGE-653) Unexpected error when attempting to run an invalid command

by George Gastaldi (JIRA)

George Gastaldi created FORGE-653: ------------------------------------- Summary: Unexpected error when attempting to run an invalid command Key: FORGE-653 URL: https://issues.jboss.org/browse/FORGE-653 Project: Forge Issue Type: Bug Reporter: George Gastaldi When I type "xx" for example and run in 1.0.6.Final, I get: {code} ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) {code} however in 1.0.5.Final, I get {code} ***ERROR*** No such command: xx {code} This is the offending stack trace: {code} java.lang.NullPointerException at org.jboss.tools.forge.runtime.ext.EventHandler.flattenObjectArray(EventHandler.java:43) at org.jboss.tools.forge.runtime.ext.EventHandler.getParameterString(EventHandler.java:38) at org.jboss.tools.forge.runtime.ext.EventHandler.handleCommandExecuted(EventHandler.java:27) 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) at org.jboss.forge.shell.command.Execution.perform(Execution.java:155) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:817) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:840) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:630) 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.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:147) at java.lang.Thread.run(Thread.java:722) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
4
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-619: ---------------------------------- Fix Version/s: (was: 1.0.6.Final) Git Pull Request: https://github.com/forge/core/pull/184 (was: https://github.com/forge/core/pull/184) Forum Reference: https://community.jboss.org/message/751887#751887 (was: https://community.jboss.org/message/751887#751887) > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-32) FSHParser is too agressive (destroys command input)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-32?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-32: --------------------------------- Fix Version/s: (was: 1.0.6.Final) > FSHParser is too agressive (destroys command input) > --------------------------------------------------- > > Key: FORGE-32 > URL: https://issues.jboss.org/browse/FORGE-32 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > > FSHParser is breaking up statements that clearly are not scripts: > [example] Customer.java $ prettyfaces mapping --resource /scaffold/customer/view.xhtml --pattern /customer/#{id} --id viewCustomer > ***INFO*** The command [mapping] takes [0] unnamed argument(s), but found [1]. > ***INFO*** Swallowed unknown token [{] for command [mapping]. > ***INFO*** Swallowed unknown token [id] for command [mapping]. > ***INFO*** Swallowed unknown token [}] for command [mapping]. > ... etc > [example] Customer.java $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-33) Pathspec parser does not properly handle Regex character in input (revealed when using tab-completion)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-33?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-33: --------------------------------- Fix Version/s: (was: 1.0.6.Final) > Pathspec parser does not properly handle Regex character in input (revealed when using tab-completion) > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-33 > URL: https://issues.jboss.org/browse/FORGE-33 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Environment: Ubuntu > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > > cd I(<TAB>" > results in: > [forge-distribution] dist $ set verbose on > [forge-distribution] dist $ cd ~/Desktop/ > [no project] Desktop $ cd I(<TAB>[INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 17.077s > [INFO] Finished at: Tue Dec 14 18:56:28 EST 2010 > [INFO] Final Memory: 16M/218M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (default-cli) on project forge-distribution: An exception occured while executing the Java class. null: InvocationTargetException: Unclosed group near index 6 > [ERROR] ^I(.*$ > [ERROR] ^ > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (default-cli) on project forge-distribution: An exception occured while executing the Java class. null > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. null > at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) > ... 19 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.util.regex.PatternSyntaxException: Unclosed group near index 6 > ^I(.*$ > ^ > at java.util.regex.Pattern.error(Pattern.java:1713) > at java.util.regex.Pattern.accept(Pattern.java:1571) > at java.util.regex.Pattern.group0(Pattern.java:2533) > at java.util.regex.Pattern.sequence(Pattern.java:1806) > at java.util.regex.Pattern.expr(Pattern.java:1752) > at java.util.regex.Pattern.compile(Pattern.java:1460) > at java.util.regex.Pattern.<init>(Pattern.java:1133) > at java.util.regex.Pattern.compile(Pattern.java:823) > at org.jboss.seam.forge.project.util.PathspecParser.resolve(PathspecParser.java:130) > at org.jboss.seam.forge.shell.completer.PluginCommandCompleter.getOptionCandidates(PluginCommandCompleter.java:337) > at org.jboss.seam.forge.shell.completer.PluginCommandCompleter.complete(PluginCommandCompleter.java:173) > at org.jboss.seam.forge.shell.completer.CommandCompleterAdaptor.complete(CommandCompleterAdaptor.java:49) > at jline.console.completer.AggregateCompleter$Completion.complete(AggregateCompleter.java:105) > at jline.console.completer.AggregateCompleter.complete(AggregateCompleter.java:66) > at jline.console.ConsoleReader.complete(ConsoleReader.java:1101) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:898) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:834) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:822) > at org.jboss.seam.forge.shell.ShellImpl.readLine(ShellImpl.java:265) > at org.jboss.seam.forge.shell.ShellImpl.doShell(ShellImpl.java:246) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:198) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:200) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:605) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:592) > at org.jboss.seam.forge.shell.Bootstrap.main(Bootstrap.java:56) > ... 6 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > lb3@quadshark ~/JBoss/forge/dist $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012