February 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2256) Strengthen test harness on JPA Commands

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2256?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2256: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.14.1.Final (was: 2.x Future) (was: 3.x Future) Resolution: Done > Strengthen test harness on JPA Commands > --------------------------------------- > > Key: FORGE-2256 > URL: https://issues.jboss.org/browse/FORGE-2256 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.14.1.Final > > > Before doing some refactoring it would be safer to add more "technical" tests, such as controlling the command metadata to make sure the refactoring doesn't break anything -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2256) Strengthen test harness on JPA Commands

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2256?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2256: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/536 > Strengthen test harness on JPA Commands > --------------------------------------- > > Key: FORGE-2256 > URL: https://issues.jboss.org/browse/FORGE-2256 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future, 3.x Future > > > Before doing some refactoring it would be safer to add more "technical" tests, such as controlling the command metadata to make sure the refactoring doesn't break anything -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2256) Strengthen test harness on JPA Commands

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2256?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2256: ---------------------------------------- Assignee: Antonio Goncalves > Strengthen test harness on JPA Commands > --------------------------------------- > > Key: FORGE-2256 > URL: https://issues.jboss.org/browse/FORGE-2256 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future, 3.x Future > > > Before doing some refactoring it would be safer to add more "technical" tests, such as controlling the command metadata to make sure the refactoring doesn't break anything -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2256) Strengthen test harness on JPA Commands

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2256: ---------------------------------------- Summary: Strengthen test harness on JPA Commands Key: FORGE-2256 URL: https://issues.jboss.org/browse/FORGE-2256 Project: Forge Issue Type: Sub-task Components: UI - API Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Before doing some refactoring it would be safer to add more "technical" tests, such as controlling the command metadata to make sure the refactoring doesn't break anything -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2184) GenerateDot fails with Maven 3.2.5: NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2184?page=com.atlassian.jira.plugin... ] Claus Ibsen commented on FORGE-2184: ------------------------------------ We just added a maven enforcer rule to check for maven version. Maybe do the same for forge https://github.com/apache/camel/commit/91a052ce56b6d9dc9caf9515dc8e65c52f... > GenerateDot fails with Maven 3.2.5: NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State > --------------------------------------------------------------------------------------------------------- > > Key: FORGE-2184 > URL: https://issues.jboss.org/browse/FORGE-2184 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > Assignee: George Gastaldi > Fix For: 2.14.0.Final > > > STR: > Use Maven 3.2.5 and run the generate-dot goal on anything. > Should give you: > {code} > --- furnace-maven-plugin:2.12.1.Final:generate-dot (generate-dot) @ windup-victims --- > Generating /home/ondra/work/Migration/WindupQuickstarts/victi.ms/target/classes/META-INF/resources/windup-victims-2.0.0-SNAPSHOT.dot > Exception in thread "pool-5-thread-1" Exception in thread "pool-6-thread-1" Exception in thread "DefaultMetadataResolver-3-1" Exception in thread "DefaultMetadataResolver-3-0" java.lang.NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State > at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > 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:745) > java.lang.NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State > at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > 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:745) > Caused by: java.lang.ClassNotFoundException: org.eclipse.aether.spi.connector.Transfer$State > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 5 more > java.lang.NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State > at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > 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:745) > Caused by: java.lang.ClassNotFoundException: org.eclipse.aether.spi.connector.Transfer$State > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 5 more > java.lang.NoClassDefFoundError: org/eclipse/aether/spi/connector/Transfer$State > at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:608) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > 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:745) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2255) Adding helper methods in CommandController

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2255?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2255: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.14.1.Final (was: 2.x Future) Resolution: Done > Adding helper methods in CommandController > ------------------------------------------ > > Key: FORGE-2255 > URL: https://issues.jboss.org/browse/FORGE-2255 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.14.1.Final > > > CommandController has a method that list of the command inputs : > {code} > Map<String, InputComponent<?, ?>> getInputs(); > {code} > It would be good to add a few helper methods (like in Roaster) : > {code} > InputComponent<?, ?> getInput(String input); // returns one input > boolean hasInput(String input); // checks if the input is present > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2255) Adding helper methods in CommandController

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2255?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2255: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/535 > Adding helper methods in CommandController > ------------------------------------------ > > Key: FORGE-2255 > URL: https://issues.jboss.org/browse/FORGE-2255 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > CommandController has a method that list of the command inputs : > {code} > Map<String, InputComponent<?, ?>> getInputs(); > {code} > It would be good to add a few helper methods (like in Roaster) : > {code} > InputComponent<?, ?> getInput(String input); // returns one input > boolean hasInput(String input); // checks if the input is present > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2255) Adding helper methods in CommandController

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2255?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2255: ---------------------------------------- Assignee: Antonio Goncalves > Adding helper methods in CommandController > ------------------------------------------ > > Key: FORGE-2255 > URL: https://issues.jboss.org/browse/FORGE-2255 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > CommandController has a method that list of the command inputs : > {code} > Map<String, InputComponent<?, ?>> getInputs(); > {code} > It would be good to add a few helper methods (like in Roaster) : > {code} > InputComponent<?, ?> getInput(String input); // returns one input > boolean hasInput(String input); // checks if the input is present > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2224) Rename attribute methodName in command java-new-method

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2224?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2224: ---------------------------------------- Yes, moving to Forge 3 is a better idea. > Rename attribute methodName in command java-new-method > ------------------------------------------------------ > > Key: FORGE-2224 > URL: https://issues.jboss.org/browse/FORGE-2224 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > The {{java-new-method}} has the following attributes : > {code} > $ java-new-method > --targetClass --returnType --parameters --accessType --methodName > {code} > The attribute {{methodName}} should be renamed to {{named}} to follow the Forge naming convention. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2224) Rename attribute methodName in command java-new-method

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2224?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2224: ----------------------------------- Fix Version/s: 3.x Future (was: 2.x Future) > Rename attribute methodName in command java-new-method > ------------------------------------------------------ > > Key: FORGE-2224 > URL: https://issues.jboss.org/browse/FORGE-2224 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > The {{java-new-method}} has the following attributes : > {code} > $ java-new-method > --targetClass --returnType --parameters --accessType --methodName > {code} > The attribute {{methodName}} should be renamed to {{named}} to follow the Forge naming convention. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2015