October 2017 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2765) DependencyFacet miss a method addDependency or addManagedDependency should be add Dependncy and ManagedDependency

by Charles Heidemann (JIRA)

Charles Heidemann created FORGE-2765: ---------------------------------------- Summary: DependencyFacet miss a method addDependency or addManagedDependency should be add Dependncy and ManagedDependency Key: FORGE-2765 URL: https://issues.jboss.org/browse/FORGE-2765 Project: Forge Issue Type: Feature Request Components: Facets Affects Versions: 3.7.2.Final Reporter: Charles Heidemann Priority: Minor DependencyFacet.addManagedDependency(POM_DEPENDENCY); Should be adding a pair of ManagedDependency/Dependency not just a ManagedDependency. OR DependencyFacet should be have a method like this DependencyFacet.addDependency(POM_DEPENDENCY) to add a Dependency based on a ManagedDependency -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-147) API report for Furnace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-147?page=com.atlassian.jira.plugi... ] George Gastaldi closed FURNACE-147. ----------------------------------- Resolution: Rejected > API report for Furnace > ---------------------- > > Key: FURNACE-147 > URL: https://issues.jboss.org/browse/FURNACE-147 > Project: Forge: Furnace > Issue Type: Enhancement > Reporter: Andrey V. Ponomarenko > Attachments: furnace-api-1.png, furnace-api-2.png > > > Hi, > Here is the report on API changes and backward binary compatibility for the Furnace library: https://abi-laboratory.pro/java/tracker/timeline/furnace-api/ > The report is generated by the https://github.com/lvc/japi-compliance-checker tool for jars at http://central.maven.org/maven2/org/jboss/forge/furnace/furnace-api/ according to https://wiki.eclipse.org/Evolving_Java-based_APIs_2. > Hope it will be helpful for users and maintainers of the library to be aware of past and future API changes. > The tool checks all public API methods and classes. Please let me know if it should not check some parts of the API. > Thank you. > !furnace-api-1.png|API symbols timeline! > !furnace-api-2.png|API changes review! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-147) API report for Furnace

by Andrey V. Ponomarenko (JIRA)

Andrey V. Ponomarenko created FURNACE-147: --------------------------------------------- Summary: API report for Furnace Key: FURNACE-147 URL: https://issues.jboss.org/browse/FURNACE-147 Project: Forge: Furnace Issue Type: Enhancement Reporter: Andrey V. Ponomarenko Attachments: furnace-api-1.png, furnace-api-2.png Hi, Here is the report on API changes and backward binary compatibility for the Furnace library: https://abi-laboratory.pro/java/tracker/timeline/furnace-api/ The report is generated by the https://github.com/lvc/japi-compliance-checker tool for jars at http://central.maven.org/maven2/org/jboss/forge/furnace/furnace-api/ according to https://wiki.eclipse.org/Evolving_Java-based_APIs_2. Hope it will be helpful for users and maintainers of the library to be aware of past and future API changes. The tool checks all public API methods and classes. Please let me know if it should not check some parts of the API. Thank you. !furnace-api-1.png|API symbols timeline! !furnace-api-2.png|API changes review! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-146) Test fails on test methods with injected parameters

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-146?page=com.atlassian.jira.plugi... ] George Gastaldi updated FURNACE-146: ------------------------------------ Priority: Minor (was: Critical) You can inject those as attributes instead. Does not look critical to me. Marking as minor > Test fails on test methods with injected parameters > --------------------------------------------------- > > Key: FURNACE-146 > URL: https://issues.jboss.org/browse/FURNACE-146 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.26.2.Final > Reporter: Charles Heidemann > Priority: Minor > Labels: FurnaceTestMethodExecutor > > Furnance fails on test methods with parameters, like: > @Test > public void checkProjectUISetupCommand(final ProjectFactory projectFactory) throws Exception > Arquillian test approach: > https://docs.jboss.org/author/display/ARQ/Dependency+injection > Arquillian have inject parameters correctly. > The main issue is that FurnaceTestMethodExecutor don't care about method parameters. > FurnaceTestMethodExecutor.java:116 > Method method = testInstance.getClass().getMethod(testMethodExecutor.getMethod().getName()); > > java.lang.NoSuchMethodException: org.jboss.forge.addon.lombok.commands.LombokProjectSetupTest_$$_javassist_82a59b41-50a4-4336-b400-0898822d8514.checkProjectShellSetupCommand() > at java.lang.Class.getMethod(Class.java:1786) > at org.jboss.forge.arquillian.impl.FurnaceTestMethodExecutor.invoke(FurnaceTestMethodExecutor.java:116) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-146) Test fails on test methods with injected parameters

by Charles Heidemann (JIRA)

Charles Heidemann created FURNACE-146: ----------------------------------------- Summary: Test fails on test methods with injected parameters Key: FURNACE-146 URL: https://issues.jboss.org/browse/FURNACE-146 Project: Forge: Furnace Issue Type: Feature Request Components: Test Harness Affects Versions: 2.26.2.Final Reporter: Charles Heidemann Priority: Critical Furnance fails on test methods with parameters, like: @Test public void checkProjectUISetupCommand(final ProjectFactory projectFactory) throws Exception Arquillian test approach: https://docs.jboss.org/author/display/ARQ/Dependency+injection Arquillian have inject parameters correctly. The main issue is that FurnaceTestMethodExecutor don't care about method parameters. FurnaceTestMethodExecutor.java:116 Method method = testInstance.getClass().getMethod(testMethodExecutor.getMethod().getName()); java.lang.NoSuchMethodException: org.jboss.forge.addon.lombok.commands.LombokProjectSetupTest_$$_javassist_82a59b41-50a4-4336-b400-0898822d8514.checkProjectShellSetupCommand() at java.lang.Class.getMethod(Class.java:1786) at org.jboss.forge.arquillian.impl.FurnaceTestMethodExecutor.invoke(FurnaceTestMethodExecutor.java:116) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2225) Being able to add a new CDI producer method to an existing class

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2225?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2225. ---------------------------------- Fix Version/s: 3.7.3.Final (was: 3.x Future) Resolution: Done > Being able to add a new CDI producer method to an existing class > ---------------------------------------------------------------- > > Key: FORGE-2225 > URL: https://issues.jboss.org/browse/FORGE-2225 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Martin Kouba > Fix For: 3.7.3.Final > > > It would be good to have a command to add a CDI producer method to an existing class. A simple command such as : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > The method is by default private, but we could change this : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --accessType private > {code} > We can also have a parameter to add the injection point > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --injectionPoint > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger(InjectionPoint injectionPoint) { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > Then, we can have more attributes : > {code} > cdi-new-producer-method --named produceLogger --returnType org.apache.logging.log4j.Logger --accessType private --injectionPoint --qualifier Production --alternative=true --scoped Request --atNamed=true > {code} > {code} > public class LoggingProducer > { > @Produces > @Production > @Alternative > @RequestScoped > @Named > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2225) Being able to add a new CDI producer method to an existing class

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/FORGE-2225?page=com.atlassian.jira.plugin... ] Martin Kouba updated FORGE-2225: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/616 > Being able to add a new CDI producer method to an existing class > ---------------------------------------------------------------- > > Key: FORGE-2225 > URL: https://issues.jboss.org/browse/FORGE-2225 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Martin Kouba > Fix For: 3.x Future > > > It would be good to have a command to add a CDI producer method to an existing class. A simple command such as : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > The method is by default private, but we could change this : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --accessType private > {code} > We can also have a parameter to add the injection point > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --injectionPoint > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger(InjectionPoint injectionPoint) { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > Then, we can have more attributes : > {code} > cdi-new-producer-method --named produceLogger --returnType org.apache.logging.log4j.Logger --accessType private --injectionPoint --qualifier Production --alternative=true --scoped Request --atNamed=true > {code} > {code} > public class LoggingProducer > { > @Produces > @Production > @Alternative > @RequestScoped > @Named > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2225) Being able to add a new CDI producer method to an existing class

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/FORGE-2225?page=com.atlassian.jira.plugin... ] Martin Kouba reassigned FORGE-2225: ----------------------------------- Assignee: Martin Kouba > Being able to add a new CDI producer method to an existing class > ---------------------------------------------------------------- > > Key: FORGE-2225 > URL: https://issues.jboss.org/browse/FORGE-2225 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: Martin Kouba > Fix For: 3.x Future > > > It would be good to have a command to add a CDI producer method to an existing class. A simple command such as : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > The method is by default private, but we could change this : > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --accessType private > {code} > We can also have a parameter to add the injection point > {code} > cdi-add-producer-method --named produceLogger --type org.apache.logging.log4j.Logger --targetClass LoggingProducer --injectionPoint > {code} > Would generate : > {code} > public class LoggingProducer > { > @Produces > public Logger produceLogger(InjectionPoint injectionPoint) { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} > Then, we can have more attributes : > {code} > cdi-new-producer-method --named produceLogger --returnType org.apache.logging.log4j.Logger --accessType private --injectionPoint --qualifier Production --alternative=true --scoped Request --atNamed=true > {code} > {code} > public class LoggingProducer > { > @Produces > @Production > @Alternative > @RequestScoped > @Named > public Logger produceLogger() { > throw new UnsupportedOperationException("Not supported yet."); > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2764) Allow to enable interceptors/decorators/alternatives globally using @javax.annotation.Priority

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2764?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2764. ---------------------------------- Fix Version/s: 3.7.3.Final Resolution: Done > Allow to enable interceptors/decorators/alternatives globally using @javax.annotation.Priority > ---------------------------------------------------------------------------------------------- > > Key: FORGE-2764 > URL: https://issues.jboss.org/browse/FORGE-2764 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Reporter: Martin Kouba > Assignee: Martin Kouba > Priority: Minor > Fix For: 3.7.3.Final > > > Enhance {{CDINewInterceptorCommand}}, {{CDINewDecoratorCommand}} and {{CDINewBeanCommand}}. Only for CDI 1.1+. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2764) Allow to enable interceptors/decorators/alternatives globally using @javax.annotation.Priority

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/FORGE-2764?page=com.atlassian.jira.plugin... ] Martin Kouba updated FORGE-2764: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/615 > Allow to enable interceptors/decorators/alternatives globally using @javax.annotation.Priority > ---------------------------------------------------------------------------------------------- > > Key: FORGE-2764 > URL: https://issues.jboss.org/browse/FORGE-2764 > Project: Forge > Issue Type: Feature Request > Components: Java EE > Reporter: Martin Kouba > Assignee: Martin Kouba > Priority: Minor > > Enhance {{CDINewInterceptorCommand}}, {{CDINewDecoratorCommand}} and {{CDINewBeanCommand}}. Only for CDI 1.1+. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2017