August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1082) Implementation of JavaEnum#addEnumConstant() does not properly add the generated element

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1082?page=com.atlassian.jira.plugin... ] Matt Benson reassigned FORGE-1082: ---------------------------------- Assignee: Matt Benson > Implementation of JavaEnum#addEnumConstant() does not properly add the generated element > ---------------------------------------------------------------------------------------- > > Key: FORGE-1082 > URL: https://issues.jboss.org/browse/FORGE-1082 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha9 > Reporter: Matt Benson > Assignee: Matt Benson > > Instead the new constant is improperly dropped into the end of the file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1081) REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1081?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1081: ---------------------------------------- This would help the cause of consistency, especially in TicketMonster where some existing REST resources are already created along side an already existing {{@ApplicationPath}} activator class. When the current REST plugin creates resources from JPA entities in TicketMonster, they're created in a new package instead of being placed alongside the existing one. > REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-1081 > URL: https://issues.jboss.org/browse/FORGE-1081 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > > When REST is setup in a project and activated through the {{@ApplicationPath}} annotated class, it would be preferable to generate all the REST resources in the same package instead of using the computed package from the project's group Id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1081) REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1081: -------------------------------------- Summary: REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class Key: FORGE-1081 URL: https://issues.jboss.org/browse/FORGE-1081 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds When REST is setup in a project and activated through the {{@ApplicationPath}} annotated class, it would be preferable to generate all the REST resources in the same package instead of using the computed package from the project's group Id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1080) REST plugin setup adds duplicate configuration entries instead of replacing them

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1080?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1080. ---------------------------------- Assignee: Vineet Reynolds Fix Version/s: 1.3.4.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/7947a82e11a4d7f24dc0d415d848520392a2... > REST plugin setup adds duplicate configuration entries instead of replacing them > -------------------------------------------------------------------------------- > > Key: FORGE-1080 > URL: https://issues.jboss.org/browse/FORGE-1080 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > If an existing project already has the RestFacet installed, then running {{rest setup}} creates duplicate entries in the {{.forge}} config file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1080) REST plugin setup adds duplicate configuration entries instead of replacing them

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1080?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1080: ----------------------------------- Summary: REST plugin setup adds duplicate configuration entries instead of replacing them (was: REST plugin setup adds configuration entries instead of replacing them) > REST plugin setup adds duplicate configuration entries instead of replacing them > -------------------------------------------------------------------------------- > > Key: FORGE-1080 > URL: https://issues.jboss.org/browse/FORGE-1080 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > > If an existing project already has the RestFacet installed, then running {{rest setup}} creates duplicate entries in the {{.forge}} config file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1080) REST plugin setup adds configuration entries instead of replacing them

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1080: -------------------------------------- Summary: REST plugin setup adds configuration entries instead of replacing them Key: FORGE-1080 URL: https://issues.jboss.org/browse/FORGE-1080 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds If an existing project already has the RestFacet installed, then running {{rest setup}} creates duplicate entries in the {{.forge}} config file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1045) Unit tests should not have a fixed version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1045?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1045: -------------------------------------- Assignee: George Gastaldi > Unit tests should not have a fixed version > ------------------------------------------ > > Key: FORGE-1045 > URL: https://issues.jboss.org/browse/FORGE-1045 > Project: Forge > Issue Type: Enhancement > Components: Test Harness > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha10 > > > Tests now depend on 2.0.0-SNAPSHOT, which may fail when a new version of the addon dependency is released. > We should find some way to avoid declaring the addon dependencies version directly in the Java class. > Excerpt from IRC: > {quote} > <gastaldi> lincolnthree, about the version in the dependencies > <gastaldi> in the tests > <lincolnthree> yes > <gastaldi> What if we consider that if no @Dependencies annotation were provided it should use the pom's dependencies ? > <lincolnthree> can't do that > <gastaldi> why ? > <lincolnthree> because you should be able to depend on dependencies that don't exist > <lincolnthree> without having to remove them from the pom > <lincolnthree> it's a valid failure scenario (laughs at that wording) > <lincolnthree> so we need to be able to test it > <lincolnthree> gastaldi: i would much prefer setting the version to "POM" > <lincolnthree> or omitting the version entirely > <lincolnthree> from the @AddonDependency annotation > <gastaldi> I think it's already optional, no ? > <lincolnthree> it is > <lincolnthree> and the default is LATEST > <lincolnthree> default should probably be POM, which we should intercept and replace with the pom version > <lincolnthree> or throw a deployment exception if it could not be resolved > <gastaldi> I see > <lincolnthree> thoughts? > <gastaldi> What about the AddonDependencyEntry.create statements ? > <gastaldi> sounds fair so far > <gastaldi> we could introduce a new method in ForgeArchive > <gastaldi> addAddonDependenciesAsDeclaredInPOMForGodsSake() > <lincolnthree> ah… right > <lincolnthree> well > <lincolnthree> the version there doesn't matter, remember? > <lincolnthree> so we could actually make the version optional > <lincolnthree> it could default to "anything" > <gastaldi> so so we need a AnythingGoesVersion implements Version subclass > <gastaldi> an enum > <gastaldi> public enum Anything implements Version { INSTANCE;} > <gastaldi> hum, or the version could be empty, right > <gastaldi> in that case there is already the EmptyVersion class > <lincolnthree> right > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1065) Furnace container extension API should provide an EventManager for handling cross-container events portably

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1065?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1065: ----------------------------------- Assignee: Lincoln Baxter III > Furnace container extension API should provide an EventManager for handling cross-container events portably > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-1065 > URL: https://issues.jboss.org/browse/FORGE-1065 > Project: Forge > Issue Type: Feature Request > Components: Event Bus, Furnace (Container) > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > Currently the CDI addon is the only container type that supports events, and they will not be compatible with each other, so in order for this to work, furnace must provide an `EventManager` API for addon containers to implement, then handle the event propagation itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1045) Unit tests should not have a fixed version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1045?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1045: ----------------------------------- Fix Version/s: (was: 2.x Future) > Unit tests should not have a fixed version > ------------------------------------------ > > Key: FORGE-1045 > URL: https://issues.jboss.org/browse/FORGE-1045 > Project: Forge > Issue Type: Enhancement > Components: Test Harness > Affects Versions: 2.0.0.Alpha7 > Reporter: George Gastaldi > > Tests now depend on 2.0.0-SNAPSHOT, which may fail when a new version of the addon dependency is released. > We should find some way to avoid declaring the addon dependencies version directly in the Java class. > Excerpt from IRC: > {quote} > <gastaldi> lincolnthree, about the version in the dependencies > <gastaldi> in the tests > <lincolnthree> yes > <gastaldi> What if we consider that if no @Dependencies annotation were provided it should use the pom's dependencies ? > <lincolnthree> can't do that > <gastaldi> why ? > <lincolnthree> because you should be able to depend on dependencies that don't exist > <lincolnthree> without having to remove them from the pom > <lincolnthree> it's a valid failure scenario (laughs at that wording) > <lincolnthree> so we need to be able to test it > <lincolnthree> gastaldi: i would much prefer setting the version to "POM" > <lincolnthree> or omitting the version entirely > <lincolnthree> from the @AddonDependency annotation > <gastaldi> I think it's already optional, no ? > <lincolnthree> it is > <lincolnthree> and the default is LATEST > <lincolnthree> default should probably be POM, which we should intercept and replace with the pom version > <lincolnthree> or throw a deployment exception if it could not be resolved > <gastaldi> I see > <lincolnthree> thoughts? > <gastaldi> What about the AddonDependencyEntry.create statements ? > <gastaldi> sounds fair so far > <gastaldi> we could introduce a new method in ForgeArchive > <gastaldi> addAddonDependenciesAsDeclaredInPOMForGodsSake() > <lincolnthree> ah… right > <lincolnthree> well > <lincolnthree> the version there doesn't matter, remember? > <lincolnthree> so we could actually make the version optional > <lincolnthree> it could default to "anything" > <gastaldi> so so we need a AnythingGoesVersion implements Version subclass > <gastaldi> an enum > <gastaldi> public enum Anything implements Version { INSTANCE;} > <gastaldi> hum, or the version could be empty, right > <gastaldi> in that case there is already the EmptyVersion class > <lincolnthree> right > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1065) Furnace container extension API should provide an EventManager for handling cross-container events portably

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1065?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1065: ----------------------------------- Fix Version/s: 2.0.0.Alpha10 (was: 2.x Future) > Furnace container extension API should provide an EventManager for handling cross-container events portably > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-1065 > URL: https://issues.jboss.org/browse/FORGE-1065 > Project: Forge > Issue Type: Feature Request > Components: Event Bus, Furnace (Container) > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > Currently the CDI addon is the only container type that supports events, and they will not be compatible with each other, so in order for this to work, furnace must provide an `EventManager` API for addon containers to implement, then handle the event propagation itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013