January 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-731) API support for nested annotations as annotation element values

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-731?page=com.atlassian.jira.plugin.... ] Matt Benson resolved FORGE-731. ------------------------------- Resolution: Done https://github.com/forge/core/commit/61df93a3684a33388dcc5568829c31c022a1... > API support for nested annotations as annotation element values > --------------------------------------------------------------- > > Key: FORGE-731 > URL: https://issues.jboss.org/browse/FORGE-731 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 1.1.4.Final > > -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-729) re-adding a named element to a "normal" annotation should replace rather than accumulate

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-729?page=com.atlassian.jira.plugin.... ] Matt Benson commented on FORGE-729: ----------------------------------- This issue is resolved, only I delimited the issue number with brackets in the commit message so it wasn't detected properly. > re-adding a named element to a "normal" annotation should replace rather than accumulate > ---------------------------------------------------------------------------------------- > > Key: FORGE-729 > URL: https://issues.jboss.org/browse/FORGE-729 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: Matt Benson > Fix For: 1.1.4.Final > > -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-729) re-adding a named element to a "normal" annotation should replace rather than accumulate

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-729?page=com.atlassian.jira.plugin.... ] Matt Benson reassigned FORGE-729: --------------------------------- Assignee: Matt Benson > re-adding a named element to a "normal" annotation should replace rather than accumulate > ---------------------------------------------------------------------------------------- > > Key: FORGE-729 > URL: https://issues.jboss.org/browse/FORGE-729 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 1.1.4.Final > > -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-436) JavaSource needs a way to parse nested annotations

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-436?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-436. ------------------------------------ Assignee: Matt Benson Resolution: Done > JavaSource needs a way to parse nested annotations > -------------------------------------------------- > > Key: FORGE-436 > URL: https://issues.jboss.org/browse/FORGE-436 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.0.6.Final > Reporter: Richard Kennard > Assignee: Matt Benson > Fix For: 1.1.4.Final > > > Currently, if presented with a Java file like this: > public class MockAnnotatedMethod { > @MockAnnotation( anAnnotation = @AnotherMockAnnotation(43)), > public MockAnnotatedMethod() { > } > } > JavaSource can easily parse @MockAnnotation into org.jboss.forge.parser.java.Annotation. But then calling... > annotationSource.getLiteralValue("anAnnotation") > ...results in the String... > "@AnotherMockAnnotation(43)" > There doesn't appear to be a good way to parse this String into another org.jboss.forge.parser.java.Annotation, complete with initializing its value to be '43'. > This is needed for Metawidget. Metawidget's inspectors can be written to inspect arbitrary metadata. It is feasible (though not currently required) that someone might want to parse: > @AttributeOverride( name = "name", column = @Column( name = "name", nullable = false ) ) > public class Person { > ... > } > This is a JPA annotation that makes the 'name' field a 'required' field, but to do so it uses nested annotations. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-730) annotation order enhancements

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-730?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-730. ------------------------------------ Assignee: Matt Benson Resolution: Done > annotation order enhancements > ----------------------------- > > Key: FORGE-730 > URL: https://issues.jboss.org/browse/FORGE-730 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 1.1.4.Final > > > Added annotations should be added as the last element before the first modifier. When an annotation is promoted from marker to single-value, to "normal" type, it should stay in the same position. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-728) Documentation for Getting Started omits crucial details

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-728?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-728: ------------------------------------------ Hmmm, sorry again that you had trouble. TAB is documented, but perhaps not "loudly" enough :) Will see what we can do. > Documentation for Getting Started omits crucial details > ------------------------------------------------------- > > Key: FORGE-728 > URL: https://issues.jboss.org/browse/FORGE-728 > Project: Forge > Issue Type: Bug > Components: Documentation > Reporter: Robert Dalgleish > > The documentation in http://forge.jboss.org/docs/using/basic-javaee-app.html omits critical details. > 1) In section "Set up persistence (JPA)", useful values for "{your JPA implementation}" and "{your container}" are not provided. From slopping around, I found that "HIBERNATE" and "JBOSS" worked. > 2) While trying to follow section "Deploy/undeploy to AS7", issuing the command "forge install-plugin jboss-as-7" yields the error: > ***ERROR*** Exception encountered: no default repository set: (to set, type: set DEFAULT_PLUGIN_REPO <repository>) (type "set VERBOSE true" to enable stack traces) > At one point in the documentation, I founnd what the value of <repository> should be, namely https://raw.github.com/forge/plugin-repository/master/repository.yaml -- however, I don't think this is the correct value, as the command then proceeded to mangle the value, changing the .yaml to yaml.yaml -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-728) Documentation for Getting Started omits crucial details

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-728?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-728. ------------------------------------ Fix Version/s: 1.1.3.Final Resolution: Out of Date > Documentation for Getting Started omits crucial details > ------------------------------------------------------- > > Key: FORGE-728 > URL: https://issues.jboss.org/browse/FORGE-728 > Project: Forge > Issue Type: Bug > Components: Documentation > Reporter: Robert Dalgleish > Fix For: 1.1.3.Final > > > The documentation in http://forge.jboss.org/docs/using/basic-javaee-app.html omits critical details. > 1) In section "Set up persistence (JPA)", useful values for "{your JPA implementation}" and "{your container}" are not provided. From slopping around, I found that "HIBERNATE" and "JBOSS" worked. > 2) While trying to follow section "Deploy/undeploy to AS7", issuing the command "forge install-plugin jboss-as-7" yields the error: > ***ERROR*** Exception encountered: no default repository set: (to set, type: set DEFAULT_PLUGIN_REPO <repository>) (type "set VERBOSE true" to enable stack traces) > At one point in the documentation, I founnd what the value of <repository> should be, namely https://raw.github.com/forge/plugin-repository/master/repository.yaml -- however, I don't think this is the correct value, as the command then proceeded to mangle the value, changing the .yaml to yaml.yaml -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-731) API support for nested annotations as annotation element values

by Matt Benson (JIRA)

Matt Benson created FORGE-731: --------------------------------- Summary: API support for nested annotations as annotation element values Key: FORGE-731 URL: https://issues.jboss.org/browse/FORGE-731 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 1.1.3.Final Reporter: Matt Benson Fix For: 1.1.4.Final -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-728) Documentation for Getting Started omits crucial details

by Robert Dalgleish (JIRA)

[ https://issues.jboss.org/browse/FORGE-728?page=com.atlassian.jira.plugin.... ] Robert Dalgleish edited comment on FORGE-728 at 1/2/13 9:39 PM: ---------------------------------------------------------------- I googled the value for the persistence provider. I entered an incorrect value for the container ("JBOSS") and it prompted me for one of several JBOSS instances. The TAB technique I also found mentioned in a google result. I had started with Forge 1.1.1, and that may have been the problem. I upgraded to 1.1.3 with no success. Removing ~/.forge directory seems to have fixed the problem. Thank you. No proxy. I despair at software that is completely missing documentation, meaning that google is my only recourse. Try doing "help persistence" and see what I mean. There is nothing the least bit obvious about the commands and the arguments unless you were, perhaps, a Maven maven or a Seam-stress or a JBoss boss. :) I am only trying out the software because, in a year, I have to consider how to upgrade a Seam 2 project to run in a JBoss AS7/Seam 3/JBoss Forge world. So far, my trepidations have not been allayed. Thank you for your answer though. My next steps will be slightly easier as a result. was (Author: bobdalgleish): I googled the value for the persistence provider. I entered an incorrect value for the container ("JBOSS") and it prompted me for one of several JBOSS instances. The TAB technique I also found mentioned in a google result. I had started with Forge 1.1.1, and that may have been the problem. I upgraded to 1.1.3 with no success. Removing ~/.forge directory seems to have fixed the problem. Thank you. No proxy. I despair at software that is completely missing documentation, meaning that google is my only recourse. Try doing "help persistence" and see what I mean. I am only trying out the software because in a year, I have to consider how to upgrade a Seam 2 project to run in a JBoss AS7/Seam 3/JBoss Forge world. So far, my trepidations have not been allayed. > Documentation for Getting Started omits crucial details > ------------------------------------------------------- > > Key: FORGE-728 > URL: https://issues.jboss.org/browse/FORGE-728 > Project: Forge > Issue Type: Bug > Components: Documentation > Reporter: Robert Dalgleish > > The documentation in http://forge.jboss.org/docs/using/basic-javaee-app.html omits critical details. > 1) In section "Set up persistence (JPA)", useful values for "{your JPA implementation}" and "{your container}" are not provided. From slopping around, I found that "HIBERNATE" and "JBOSS" worked. > 2) While trying to follow section "Deploy/undeploy to AS7", issuing the command "forge install-plugin jboss-as-7" yields the error: > ***ERROR*** Exception encountered: no default repository set: (to set, type: set DEFAULT_PLUGIN_REPO <repository>) (type "set VERBOSE true" to enable stack traces) > At one point in the documentation, I founnd what the value of <repository> should be, namely https://raw.github.com/forge/plugin-repository/master/repository.yaml -- however, I don't think this is the correct value, as the command then proceeded to mangle the value, changing the .yaml to yaml.yaml -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-730) annotation order enhancements

by Matt Benson (JIRA)

Matt Benson created FORGE-730: --------------------------------- Summary: annotation order enhancements Key: FORGE-730 URL: https://issues.jboss.org/browse/FORGE-730 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 1.1.3.Final Reporter: Matt Benson Fix For: 1.1.4.Final Added annotations should be added as the last element before the first modifier. When an annotation is promoted from marker to single-value, to "normal" type, it should stay in the same position. -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2013