February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1613) FileWatcher should handle missing folders after deleting a project root directory.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1613?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1613: ---------------------------------------- More output: {code} Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized test-profile.gradle - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0> ENTRY_MODIFY Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized settings.gradle - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0> ENTRY_MODIFY Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized Service.java - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0/src/main/interfaces/org/testproject> ENTRY_MODIFY Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized forge.txt - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0/src/main/images> ENTRY_MODIFY Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0/src/test/mocks/org/testproject> ENTRY_MODIFY Feb 28, 2014 6:21:21 PM org.jboss.forge.addon.resource.monitor.FileWatcher run SEVERE: WatchKey not recognized pom.xml - /usr/local/workspace/addon-gradle/tests/target/1393622461539-0/src/test/templates> ENTRY_MODIFY {code} > FileWatcher should handle missing folders after deleting a project root directory. > ---------------------------------------------------------------------------------- > > Key: FORGE-1613 > URL: https://issues.jboss.org/browse/FORGE-1613 > Project: Forge > Issue Type: Feature Request > Components: Resources > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs: > {code} > [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1613) FileWatcher should handle missing folders after deleting a project root directory.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1613?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1613: ----------------------------------- Description: It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs: {code} [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE {code} was: It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs and in some cases it causes OutOfMemoryError: {code} [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE {code} > FileWatcher should handle missing folders after deleting a project root directory. > ---------------------------------------------------------------------------------- > > Key: FORGE-1613 > URL: https://issues.jboss.org/browse/FORGE-1613 > Project: Forge > Issue Type: Feature Request > Components: Resources > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs: > {code} > [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1613) FileWatcher should handle missing folders after deleting a project root directory.

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1613: -------------------------------------- Summary: FileWatcher should handle missing folders after deleting a project root directory. Key: FORGE-1613 URL: https://issues.jboss.org/browse/FORGE-1613 Project: Forge Issue Type: Feature Request Components: Resources Affects Versions: 2.1.1.Final Reporter: George Gastaldi Fix For: 2.x Future It was observed that when the project.getRootDirectory().delete() is called, some warnings are printed in the logs and in some cases it causes OutOfMemoryError: {code} [INFO] SEVERE: WatchKey not recognized TestMainClass.java - /usr/local/workspace/addon-gradle/tests/target/1393619738127-0/src/test/mocks/org/testproject> ENTRY_DELETE {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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1599) Introduce a cache addon

by Adam Wyłuda (JIRA)

[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ] Adam Wyłuda commented on FORGE-1599: ------------------------------------ We decided to make API based on JSR-107 and Infinispan as an implementation. > Introduce a cache addon > ----------------------- > > Key: FORGE-1599 > URL: https://issues.jboss.org/browse/FORGE-1599 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: George Gastaldi > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > This would allow other addons to cache state. It should allow individual configurations of each cache. > There should also have a CacheFactory, to allow creation of caches on-demand. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1599) Introduce a cache addon

by Adam Wyłuda (JIRA)

[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ] Adam Wyłuda reassigned FORGE-1599: ---------------------------------- Assignee: Adam Wyłuda > Introduce a cache addon > ----------------------- > > Key: FORGE-1599 > URL: https://issues.jboss.org/browse/FORGE-1599 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: George Gastaldi > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > This would allow other addons to cache state. It should allow individual configurations of each cache. > There should also have a CacheFactory, to allow creation of caches on-demand. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1612) Allow the order of Addon commands to be customized

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1612?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1612: ----------------------------------- Fix Version/s: 2.x Future > Allow the order of Addon commands to be customized > -------------------------------------------------- > > Key: FORGE-1612 > URL: https://issues.jboss.org/browse/FORGE-1612 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > Priority: Minor > Fix For: 2.x Future > > > Currently the Addon commands are displayed in alphanumeric order, first by category then command name. For example: > PicketLink: Create Model > PicketLink: Setup > It would be nice to be able to override this default behaviour so that commands could be listed in the chronological order that they're typically executed in, like so: > PicketLink: Setup > PicketLink: Create Model -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1612) Allow the order of Addon commands to be customized

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1612?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1612: ----------------------------------- Component/s: UI - Eclipse > Allow the order of Addon commands to be customized > -------------------------------------------------- > > Key: FORGE-1612 > URL: https://issues.jboss.org/browse/FORGE-1612 > Project: Forge > Issue Type: Feature Request > Components: Addon Development, UI - Eclipse > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > Priority: Minor > Fix For: 2.x Future > > > Currently the Addon commands are displayed in alphanumeric order, first by category then command name. For example: > PicketLink: Create Model > PicketLink: Setup > It would be nice to be able to override this default behaviour so that commands could be listed in the chronological order that they're typically executed in, like so: > PicketLink: Setup > PicketLink: Create Model -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1612) Allow the order of Addon commands to be customized

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1612?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1612: ---------------------------------------- Perhaps we could implement this as an optional file to be placed in the addon's JAR with the order to be displayed. > Allow the order of Addon commands to be customized > -------------------------------------------------- > > Key: FORGE-1612 > URL: https://issues.jboss.org/browse/FORGE-1612 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Affects Versions: 2.1.1.Final > Reporter: Shane Bryzak > Priority: Minor > > Currently the Addon commands are displayed in alphanumeric order, first by category then command name. For example: > PicketLink: Create Model > PicketLink: Setup > It would be nice to be able to override this default behaviour so that commands could be listed in the chronological order that they're typically executed in, like so: > PicketLink: Setup > PicketLink: Create Model -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1612) Allow the order of Addon commands to be customized

by Shane Bryzak (JIRA)

Shane Bryzak created FORGE-1612: ----------------------------------- Summary: Allow the order of Addon commands to be customized Key: FORGE-1612 URL: https://issues.jboss.org/browse/FORGE-1612 Project: Forge Issue Type: Feature Request Components: Addon Development Affects Versions: 2.1.1.Final Reporter: Shane Bryzak Priority: Minor Currently the Addon commands are displayed in alphanumeric order, first by category then command name. For example: PicketLink: Create Model PicketLink: Setup It would be nice to be able to override this default behaviour so that commands could be listed in the chronological order that they're typically executed in, like so: PicketLink: Setup PicketLink: Create Model -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1465) Allow setup wizard fields to be combined into a single wizard page

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1465?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1465: ---------------------------------------- Introduced a NavigationResultBuilder: Here is a sample on how to use it: https://github.com/forge/core/blob/master/ui/example/src/main/java/org/jb... > Allow setup wizard fields to be combined into a single wizard page > ------------------------------------------------------------------ > > Key: FORGE-1465 > URL: https://issues.jboss.org/browse/FORGE-1465 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.CR1 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.1.1.Final > > > There are around 5-6 setup wizard page displayed to choose various Java EE spec versions. These could be combined into a single page as an optimization. -- 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014