January 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2589) Throw when AddonRegistry().getServices(Class) finds nothing

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2589?page=com.atlassian.jira.plugin... ] Ondrej Zizka updated FORGE-2589: -------------------------------- Description: This is just a suggestion to strenghten the contract of {code} furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); {code} was: {code} furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); {code} > Throw when AddonRegistry().getServices(Class) finds nothing > ----------------------------------------------------------- > > Key: FORGE-2589 > URL: https://issues.jboss.org/browse/FORGE-2589 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager, Furnace (Container) > Affects Versions: 2.20.1.Final > Reporter: Ondrej Zizka > > This is just a suggestion to strenghten the contract of > {code} > furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2589) Throw when AddonRegistry().getServices(Class) finds nothing

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2589?page=com.atlassian.jira.plugin... ] Ondrej Zizka updated FORGE-2589: -------------------------------- Summary: Throw when AddonRegistry().getServices(Class) finds nothing (was: furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get();) > Throw when AddonRegistry().getServices(Class) finds nothing > ----------------------------------------------------------- > > Key: FORGE-2589 > URL: https://issues.jboss.org/browse/FORGE-2589 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager, Furnace (Container) > Affects Versions: 2.20.1.Final > Reporter: Ondrej Zizka > > {code} > furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2589) furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get();

by Ondrej Zizka (JIRA)

Ondrej Zizka created FORGE-2589: ----------------------------------- Summary: furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); Key: FORGE-2589 URL: https://issues.jboss.org/browse/FORGE-2589 Project: Forge Issue Type: Feature Request Components: Addon Manager, Furnace (Container) Affects Versions: 2.20.1.Final Reporter: Ondrej Zizka {code} furnace.getAddonRegistry().getServices(GraphApiCompositeClassLoaderProvider.class).get(); {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2588) support creating projects from archetypes which don't use maven

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/FORGE-2588?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when James Strachan created pull request #594 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > support creating projects from archetypes which don't use maven > --------------------------------------------------------------- > > Key: FORGE-2588 > URL: https://issues.jboss.org/browse/FORGE-2588 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > we've a bunch of archetypes for projects like nodejs, golang, swift, python, ruby; we're also hoping to add archetypes for things like Gradle / SBT etc. > It'd be nice to allow the project-new wizard to not always create a pom.xml and src/main/* src/test/* folders if the archetype does not contain a pom.xml file. > PR on the way shortly... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2588) support creating projects from archetypes which don't use maven

by James Strachan (JIRA)

[ https://issues.jboss.org/browse/FORGE-2588?page=com.atlassian.jira.plugin... ] James Strachan commented on FORGE-2588: --------------------------------------- here's the first PR which only creates the src\main|test folders if the pom.xml is inside the archetype: https://github.com/forge/core/pull/594 still need to figure out why a pom.xml gets generated for nodejs/golang projects... > support creating projects from archetypes which don't use maven > --------------------------------------------------------------- > > Key: FORGE-2588 > URL: https://issues.jboss.org/browse/FORGE-2588 > Project: Forge > Issue Type: Feature Request > Reporter: James Strachan > > we've a bunch of archetypes for projects like nodejs, golang, swift, python, ruby; we're also hoping to add archetypes for things like Gradle / SBT etc. > It'd be nice to allow the project-new wizard to not always create a pom.xml and src/main/* src/test/* folders if the archetype does not contain a pom.xml file. > PR on the way shortly... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2588) support creating projects from archetypes which don't use maven

by James Strachan (JIRA)

James Strachan created FORGE-2588: ------------------------------------- Summary: support creating projects from archetypes which don't use maven Key: FORGE-2588 URL: https://issues.jboss.org/browse/FORGE-2588 Project: Forge Issue Type: Feature Request Reporter: James Strachan we've a bunch of archetypes for projects like nodejs, golang, swift, python, ruby; we're also hoping to add archetypes for things like Gradle / SBT etc. It'd be nice to allow the project-new wizard to not always create a pom.xml and src/main/* src/test/* folders if the archetype does not contain a pom.xml file. PR on the way shortly... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-92. ---------------------------------- > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > Fix For: 2.18.1.Final > > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] George Gastaldi commented on ROASTER-92: ---------------------------------------- Good job! Thank you > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > Fix For: 2.18.1.Final > > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-92) implementInterface shouldn't copy annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-92?page=com.atlassian.jira.plugin... ] George Gastaldi updated ROASTER-92: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.18.1.Final Resolution: Done > implementInterface shouldn't copy annotation > -------------------------------------------- > > Key: ROASTER-92 > URL: https://issues.jboss.org/browse/ROASTER-92 > Project: Roaster > Issue Type: Bug > Reporter: Nicolas Challut > Assignee: Nicolas Challut > Fix For: 2.18.1.Final > > > When I implements inherited method, annotations aren't needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-91) Add JavaInterfaceMethodImpl class

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/54 (was: https://github.com/forge/roaster/pull/52) > Add JavaInterfaceMethodImpl class > --------------------------------- > > 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 ? > UPDATE 21/01 : We could add a new class which extend MethodImpl to handle special behavior of interface. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2016