July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-992) Create a Github hook for the Plugin/Addon repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-992?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-992. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done > Create a Github hook for the Plugin/Addon repository > ---------------------------------------------------- > > Key: FORGE-992 > URL: https://issues.jboss.org/browse/FORGE-992 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Plugin Repository > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > > This service should notify the Forge Addon repository application of any new releases to an addon/plugin -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1806) IDE commands should be executed in background thread to allow backgrounding of the window

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1806?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1806. ------------------------------------- Assignee: Lincoln Baxter III (was: Koen Aers) Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Implemented cancellation. Windows should not be backgroundable however, so closing this issue. > IDE commands should be executed in background thread to allow backgrounding of the window > ----------------------------------------------------------------------------------------- > > Key: FORGE-1806 > URL: https://issues.jboss.org/browse/FORGE-1806 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: UI - Eclipse > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.7.0.Final > > > http://youtu.be/5xO3jhntTt8?t=38m23s > The task cannot be cancelled and the window is blocking eclipse. Wizards that are executing should be run in a separate thread so that they can be moved to the background. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1266) Implement IgnoreEOF in Forge 2 Shell

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1266?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1266: ------------------------------------ Assignee: George Gastaldi (was: Ståle Pedersen) It is not working correctly with Aesh 0.56 and Forge 2.7.0.Final. Reopening > Implement IgnoreEOF in Forge 2 Shell > ------------------------------------ > > Key: FORGE-1266 > URL: https://issues.jboss.org/browse/FORGE-1266 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.1.0.Final > > > See current IGNOREEOF behavior in Forge 1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1924) AddonRegistry should return the Furnace instance it belongs to

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1924?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1924: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: (was: 2.x Future) Resolution: Rejected Doesn't seem to be a good idea, because you can @Inject Furnace and this would be the only place where Furnace would be exposed > AddonRegistry should return the Furnace instance it belongs to > -------------------------------------------------------------- > > Key: FORGE-1924 > URL: https://issues.jboss.org/browse/FORGE-1924 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Furnace (Container) > Affects Versions: 2.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > > This would be useful in a scenario where multiple Furnaces could be started, for example. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1924) AddonRegistry should return the Furnace instance it belongs to

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1924?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1924: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/furnace/pull/17 > AddonRegistry should return the Furnace instance it belongs to > -------------------------------------------------------------- > > Key: FORGE-1924 > URL: https://issues.jboss.org/browse/FORGE-1924 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Furnace (Container) > Affects Versions: 2.7.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > This would be useful in a scenario where multiple Furnaces could be started, for example. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1924) AddonRegistry should return the Furnace instance it belongs to

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1924: -------------------------------------- Summary: AddonRegistry should return the Furnace instance it belongs to Key: FORGE-1924 URL: https://issues.jboss.org/browse/FORGE-1924 Project: Forge Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Furnace (Container) Affects Versions: 2.7.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.x Future This would be useful in a scenario where multiple Furnaces could be started, for example. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loses defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1848: ------------------------------------------- Any change Aslak? > IDE loses defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-273: ------------------------------------- Assignee: George Gastaldi (was: Rodney Russ) > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-273: ------------------------------------------ In Java: https://github.com/fabric8io/fabric8/blob/master/tooling/camel-tooling-ut... > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > Fix For: 2.x Future > > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1875) Console hangs during auto-complete

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1875?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1875: ---------------------------------------- Is this still reproducible in 2.7.0.Final? > Console hangs during auto-complete > ---------------------------------- > > Key: FORGE-1875 > URL: https://issues.jboss.org/browse/FORGE-1875 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.6.0.Final > Environment: JBDS 8 Beta 2, Mac OS X Mavericks 10.9.3, Oracle JDK 1.8.0_05 > Reporter: Vineet Reynolds > > When I TAB out for auto-complete options for JPA entities during scaffold generation, like so: > {noformat} > scaffold-generate --provider AngularJS --targets <TAB> com.redhat.sessions.model. > {noformat} > then the console hangs after displaying the initial package selection i.e. {{com.redhat.sessions.model.}}. > The following stacktrace is reported: > {noformat} > !ENTRY org.jboss.tools.forge.aesh.core 4 1 2014-06-09 20:44:52.663 > !MESSAGE Error logged from Aesh Core Plugin: > !STACK 0 > java.lang.Throwable: Unimplemented command: DEVICE_STATUS_REPORT > at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:11) > at org.jboss.tools.aesh.core.internal.io.DocumentHandler.handleCommand(DocumentHandler.java:35) > at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:34) > at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:21) > at java.io.PrintStream.write(PrintStream.java:480) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104) > at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185) > at java.io.PrintStream.write(PrintStream.java:527) > at java.io.PrintStream.print(PrintStream.java:669) > at org.jboss.aesh.console.Console$ConsoleShell.getCursor(Console.java:935) > at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:156) > at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:125) > at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:114) > at org.jboss.aesh.console.AeshCompletionHandler.displayCompletion(AeshCompletionHandler.java:218) > at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:162) > at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:381) > at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:149) > at org.jboss.aesh.console.Console.processInternalOperation(Console.java:596) > at org.jboss.aesh.console.Console.execute(Console.java:586) > at org.jboss.aesh.console.Console.access$700(Console.java:60) > at org.jboss.aesh.console.Console$6.run(Console.java:503) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2014