January 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/forge/roaster/pull/50 (was: https://github.com/forge/roaster/pull/49) > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-103) Upgrade to Maven 3.3.9

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-103?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-103. ----------------------------------- Resolution: Done > Upgrade to Maven 3.3.9 > ---------------------- > > Key: FURNACE-103 > URL: https://issues.jboss.org/browse/FURNACE-103 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Maven > Affects Versions: 2.22.10.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.23.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-103) Upgrade to Maven 3.3.9

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-103: --------------------------------------- Summary: Upgrade to Maven 3.3.9 Key: FURNACE-103 URL: https://issues.jboss.org/browse/FURNACE-103 Project: Forge: Furnace Issue Type: Component Upgrade Components: Maven Affects Versions: 2.22.10.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.23.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Work on ROASTER-91 started by Nicolas Challut. ---------------------------------------------- > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Open (was: Pull Request Sent) > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/roaster/pull/49 (was: https://github.com/forge/roaster/pull/48) > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) implementInterface doesn't work for JavaInterfaceSource

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/ROASTER-91?page=com.atlassian.jira.plugin... ] Nicolas Challut updated ROASTER-91: ----------------------------------- Status: Open (was: Pull Request Sent) > implementInterface doesn't work for JavaInterfaceSource > ------------------------------------------------------- > > Key: ROASTER-91 > URL: https://issues.jboss.org/browse/ROASTER-91 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.0.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > method "bar" should be overrided in javaClass but it is empty. > While searching in the code, I found that : > {code} > for (Method method : source.getMethods()) > { > if (method.isAbstract() && !target.hasMethod(method)) > { > {code} > It seems that in JavaInterfaceSource the method aren't abstract by default (in the standars, interface method is abstract, key word is redundant). > So, I see 2 ways to resolve this : > # Change JavaInterface implementation to set all method abstract without add the key word > # Change Methods#implementAbstractMethod() to handle JavaInterfaceSource type (if source instance of JavaInterfaceSource, addAll() ) > What do you guys think about it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-102) Upgrade to Weld 2.3.2.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-102?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-102. ----------------------------------- Resolution: Done > Upgrade to Weld 2.3.2.Final > --------------------------- > > Key: FURNACE-102 > URL: https://issues.jboss.org/browse/FURNACE-102 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Container - CDI > Affects Versions: 2.22.10.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.23.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-102) Upgrade to Weld 2.3.2.Final

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-102: --------------------------------------- Summary: Upgrade to Weld 2.3.2.Final Key: FURNACE-102 URL: https://issues.jboss.org/browse/FURNACE-102 Project: Forge: Furnace Issue Type: Component Upgrade Components: Container - CDI Affects Versions: 2.22.10.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.23.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2580) Stack field should be disabled for certain project types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2580?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2580: ----------------------------------- Issue Type: Enhancement (was: Task) > Stack field should be disabled for certain project types > -------------------------------------------------------- > > Key: FORGE-2580 > URL: https://issues.jboss.org/browse/FORGE-2580 > Project: Forge > Issue Type: Enhancement > Affects Versions: 3.0.0.Beta2 > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 3.0.0.Beta3 > > > In beta2 the project-new command now asks about build system (see below). > Because its JEE related asking about JEE6 and JEE7 what does it do? And is there a way to turn it off. Its IMHO important for forge to be "neutral" and not impose something like JEE on users that do not want this. > As I chose from archetype / archetype-catalog. I just want project-new to create the maven project 100% from the maven archetype and not do "extra stuff" about JEE. > {code} > [workspace]$ project-new > ***INFO*** Required inputs not satisfied, entering interactive mode > * Project name: foo > ? Top level package [org.foo]: > ? Version [1.0.0-SNAPSHOT]: > ? Final name: > ? Project location [/Users/davsclaus/Documents/workspace]: > [0] (x) war > [1] ( ) jar > [2] ( ) parent > [3] ( ) addon > [4] ( ) resource-jar > [5] ( ) ear > [6] ( ) from-archetype > [7] ( ) from-archetype-catalog > [8] ( ) generic > Press <ENTER> to confirm, or <CTRL>+C to cancel. > * Project type: [0-8] 7 > [0] (x) Maven > Press <ENTER> to confirm, or <CTRL>+C to cancel. > * Build system: [0] 0 > [0] ( ) JAVA_EE_7 > [1] ( ) JAVA_EE_6 > [2] ( ) NONE > Press <ENTER> to confirm, or <CTRL>+C to cancel. > ? Stack (The technology stack to be used in this project): [0-2] 2 > [0] ( ) camel > [1] ( ) fabric8 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2016