February 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-561) Forge generating only five fields for search.xhtml?

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-561?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-561: ---------------------------------- Affects Version/s: 2.14.0.Final > Forge generating only five fields for search.xhtml? > --------------------------------------------------- > > Key: FORGE-561 > URL: https://issues.jboss.org/browse/FORGE-561 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.14.0.Final > Reporter: easy koala > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-561) Forge generating only five fields for search.xhtml?

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-561?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-561: ---------------------------------- Fix Version/s: 2.x Future > Forge generating only five fields for search.xhtml? > --------------------------------------------------- > > Key: FORGE-561 > URL: https://issues.jboss.org/browse/FORGE-561 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Reporter: easy koala > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-561) Forge generating only five fields for search.xhtml?

by Silviu PM (JIRA)

[ https://issues.jboss.org/browse/FORGE-561?page=com.atlassian.jira.plugin.... ] Silviu PM reopened FORGE-561: ----------------------------- According to George Gastaldi's reply to my similar question, yes, the number of search criteria is limited to five and it is set here: core/UnsearchableWidgetProcessor.java at master · forge/core · GitHub In my opinion, it would be more convenient for developers to have all searchable entity's fields available as search criteria in search.xhtml. Thank you. Silviu > Forge generating only five fields for search.xhtml? > --------------------------------------------------- > > Key: FORGE-561 > URL: https://issues.jboss.org/browse/FORGE-561 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Reporter: easy koala > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2257) Introduce initial (NEW) status for newly deployed addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2257?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2257: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Introduce initial (NEW) status for newly deployed addons > -------------------------------------------------------- > > Key: FORGE-2257 > URL: https://issues.jboss.org/browse/FORGE-2257 > Project: Forge > Issue Type: Enhancement > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Environment: Fedora 20 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.14.1.Final > > > Right now Furnace has experienced some race conditions while loading addons, mainly because {{MISSING}} is the initial state. This behavior is ambiguous, because the same state is used for addons that were loaded but had missing dependencies > We should introduce a {{NEW}} state that should be used as the initial state. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2125) Frequent errors like this "java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon."

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2125?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2125. ---------------------------------- Resolution: Done FORGE-2257 should fix this > Frequent errors like this "java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon." > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-2125 > URL: https://issues.jboss.org/browse/FORGE-2125 > Project: Forge > Issue Type: Bug > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 2.14.1.Final > > > These happen in frequently within the Windup tests and appear to relate to some startup problem in Forge: > Full stack: > {code} > java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon. > at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:234) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > 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.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:294) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:269) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2257) Introduce initial (NEW) status for newly deployed addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2257?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2257: -------------------------------------- Summary: Introduce initial (NEW) status for newly deployed addons (was: Introduce initial status for newly deployed addons) > Introduce initial (NEW) status for newly deployed addons > -------------------------------------------------------- > > Key: FORGE-2257 > URL: https://issues.jboss.org/browse/FORGE-2257 > Project: Forge > Issue Type: Enhancement > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Environment: Fedora 20 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.14.1.Final > > > Right now Furnace has experienced some race conditions while loading addons, mainly because {{MISSING}} is the initial state. This behavior is ambiguous, because the same state is used for addons that were loaded but had missing dependencies > We should introduce a {{NEW}} state that should be used as the initial state. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2257) Introduce initial status for newly deployed addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2257?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2257: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/furnace/pull/23 > Introduce initial status for newly deployed addons > -------------------------------------------------- > > Key: FORGE-2257 > URL: https://issues.jboss.org/browse/FORGE-2257 > Project: Forge > Issue Type: Enhancement > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Environment: Fedora 20 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.14.1.Final > > > Right now Furnace has experienced some race conditions while loading addons, mainly because {{MISSING}} is the initial state. This behavior is ambiguous, because the same state is used for addons that were loaded but had missing dependencies > We should introduce a {{NEW}} state that should be used as the initial state. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2257) Introduce AddonStatus.NEW

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2257: -------------------------------------- Summary: Introduce AddonStatus.NEW Key: FORGE-2257 URL: https://issues.jboss.org/browse/FORGE-2257 Project: Forge Issue Type: Enhancement Components: Furnace (Container), Test Harness Affects Versions: 2.14.0.Final Environment: Fedora 20 Reporter: George Gastaldi Assignee: George Gastaldi Priority: Critical Fix For: 2.14.1.Final Right now Furnace has experienced some race conditions while loading addons, mainly because {{MISSING}} is the initial state. This behavior is ambiguous, because the same state is used for addons that were loaded but had missing dependencies We should introduce a {{NEW}} state that should be used as the initial state. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2257) Introduce initial status for newly deployed addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2257?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2257: ----------------------------------- Summary: Introduce initial status for newly deployed addons (was: Introduce AddonStatus.NEW) > Introduce initial status for newly deployed addons > -------------------------------------------------- > > Key: FORGE-2257 > URL: https://issues.jboss.org/browse/FORGE-2257 > Project: Forge > Issue Type: Enhancement > Components: Furnace (Container), Test Harness > Affects Versions: 2.14.0.Final > Environment: Fedora 20 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.14.1.Final > > > Right now Furnace has experienced some race conditions while loading addons, mainly because {{MISSING}} is the initial state. This behavior is ambiguous, because the same state is used for addons that were loaded but had missing dependencies > We should introduce a {{NEW}} state that should be used as the initial state. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2248) Support InputComponent.getNote() in Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2248?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2248. ---------------------------------- Resolution: Done > Support InputComponent.getNote() in Eclipse > ------------------------------------------- > > Key: FORGE-2248 > URL: https://issues.jboss.org/browse/FORGE-2248 > Project: Forge > Issue Type: Sub-task > Components: UI - Eclipse > Affects Versions: 2.14.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.14.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2015