[JBoss JIRA] (FORGE-1500) ProjectFactoryImpl.findProject() should iterate over directories first then over build systems
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1500?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1500:
-------------------------------------------
Hey Adam,
Sorry, I thought I had replied to this earlier! I just found the draft email, unsent.
In short, I think this is a good idea, definitely worth fixing.
Is this something you'd like to do?
~Lincoln
> ProjectFactoryImpl.findProject() should iterate over directories first then over build systems
> ----------------------------------------------------------------------------------------------
>
> Key: FORGE-1500
> URL: https://issues.jboss.org/browse/FORGE-1500
> Project: Forge
> Issue Type: Bug
> Components: Builtin Plugins
> Affects Versions: 2.0.0.CR1
> Reporter: Adam Wyłuda
> Fix For: 2.x Future
>
>
> https://github.com/forge/core/blob/2.0/projects/impl/src/main/java/org/jb...
> In case we have a project structure:
> a/pom.xml
> a/b/build.gradle
> Starting from a/b/, if registry.getServices(BuildSystem.class) returns MavenBuildSystem as first, then it will pick up a/pom.xml.
> My solution is inverting loops:
> for (each build system) { for (each directory) { ... } } ---> for (each dir) { for (each build system) { ... } }
> This causes problems in Gradle addon Maven build as temporary projects are run inside target/ directory, which has always pom.xml above.
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1563) Unable to launch infocmp in a linux (opensuse) machine.
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1563:
--------------------------------------
Summary: Unable to launch infocmp in a linux (opensuse) machine.
Key: FORGE-1563
URL: https://issues.jboss.org/browse/FORGE-1563
Project: Forge
Issue Type: Bug
Components: UI - Shell
Affects Versions: 2.0.0.Final
Reporter: Vineet Reynolds
Priority: Critical
Unable to launch forge 2.0.0.Final shell in a linux (opensuse) machine. $forge command throws the following error :
{code}
kumaran@linux-p1a9:~> forge
_____
| ___|__ _ __ __ _ ___
| |_ / _ \| `__/ _` |/ _ \ \\
| _| (_) | | | (_| | __/ //
|_| \___/|_| \__, |\___|
|___/
JBoss Forge, version [ 2.0.0.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /tmp/1391710914740-0/native/unix_32_xadisk.native which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
java.io.IOException: Cannot run program "infocmp": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at org.jboss.aesh.terminal.InfocmpHandler.fetchInfocmp(InfocmpHandler.java:51)
at org.jboss.aesh.terminal.InfocmpHandler.parseInfocmp(InfocmpHandler.java:42)
at org.jboss.aesh.terminal.InfocmpHandler.<init>(InfocmpHandler.java:36)
at org.jboss.aesh.terminal.InfocmpHandler.<init>(InfocmpHandler.java:20)
at org.jboss.aesh.terminal.InfocmpHandler$InfocmpHolder.<clinit>(InfocmpHandler.java:27)
at org.jboss.aesh.terminal.InfocmpHandler.getInstance(InfocmpHandler.java:31)
at org.jboss.aesh.terminal.InfocmpManager.alternateBuffer(InfocmpManager.java:165)
at org.jboss.aesh.util.ANSI.<clinit>(ANSI.java:39)
at org.jboss.aesh.terminal.TerminalCharacter.toString(TerminalCharacter.java:97)
at org.jboss.aesh.console.Prompt.generateOutString(Prompt.java:75)
at org.jboss.aesh.console.Prompt.<init>(Prompt.java:61)
at org.jboss.forge.addon.shell.ShellImpl.createPrompt(ShellImpl.java:131)
at org.jboss.forge.addon.shell.ShellImpl.<init>(ShellImpl.java:84)
at org.jboss.forge.addon.shell.ShellFactoryImpl.createShell(ShellFactoryImpl.java:51)
at org.jboss.forge.addon.shell.ShellInitializer.startupDefaultShell(ShellInitializer.java:36)
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:606)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:274)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:261)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:240)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:171)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:167)
at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:121)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:673)
at org.jboss.weld.util.ForwardingBeanManager.fireEvent(ForwardingBeanManager.java:101)
at org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider.postStartup(WeldAddonLifecycleProvider.java:106)
at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:101)
at org.jboss.forge.furnace.impl.addons.AddonRunnable$2.call(AddonRunnable.java:85)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:84)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:135)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
... 39 more
[kumaran]$
{code}
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1562) Migrate the wait command from Forge 1
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1562:
--------------------------------------
Summary: Migrate the wait command from Forge 1
Key: FORGE-1562
URL: https://issues.jboss.org/browse/FORGE-1562
Project: Forge
Issue Type: Feature Request
Components: Builtin Plugins
Affects Versions: 2.0.0.Final
Reporter: George Gastaldi
Fix For: 2.x Future
It should be present in the configuration addon. The original code is in org.jboss.forge.shell.plugins.builtin.ListConfigPlugin
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1561) Migrate the list-config command from Forge 1
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1561:
--------------------------------------
Summary: Migrate the list-config command from Forge 1
Key: FORGE-1561
URL: https://issues.jboss.org/browse/FORGE-1561
Project: Forge
Issue Type: Feature Request
Components: Builtin Plugins
Affects Versions: 2.0.0.Final
Reporter: George Gastaldi
Fix For: 2.x Future
It should be present in the configuration addon. The original code is in org.jboss.forge.shell.plugins.builtin.ListConfigPlugin
--
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
10 years, 4 months