November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1244) Types.isJavaLang() returns true for types in java.lang subpackages

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1244?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1244: -------------------------------------- Fix Version/s: 2.x Future > Types.isJavaLang() returns true for types in java.lang subpackages > ------------------------------------------------------------------ > > Key: FORGE-1244 > URL: https://issues.jboss.org/browse/FORGE-1244 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > > Since this method is used to implement Importer#requiresImport(), it leads to incorrect results. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1240) Add resolveArtifact() to MavenAddonDependencyResolver

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1240?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1240. ------------------------------------- Resolution: Rejected This is unnecessary due to the fact that Shrinkwrap resolvers already provides such a feature. The intent of this issue was for tests, so I am comfortable recommending this API instead: https://github.com/shrinkwrap/resolver#resolution-of-artifacts-specified-... > Add resolveArtifact() to MavenAddonDependencyResolver > ----------------------------------------------------- > > Key: FORGE-1240 > URL: https://issues.jboss.org/browse/FORGE-1240 > Project: Forge > Issue Type: Enhancement > Reporter: Koen Aers > Assignee: Koen Aers > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1218) Maven*ResourcesFacet implementations should support property resolution of resource directory paths

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1218?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1218: -------------------------------------- Fix Version/s: 2.x Future > Maven*ResourcesFacet implementations should support property resolution of resource directory paths > --------------------------------------------------------------------------------------------------- > > Key: FORGE-1218 > URL: https://issues.jboss.org/browse/FORGE-1218 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha12 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Currently, if a user users a property such as ${project.basedir} in their configuration, the properties will not be expanded, resulting in incorrect source dir configurations. > MavenResourcesFacet > MavenJavaResourcesFacet > MavenWebResourcesFacet > All suffer from this problem. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1234) Offer the possibility to add Maven dependencies to a forge archive

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1234?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1234. ------------------------------------- Resolution: Rejected This already exists: forgeArchive.addAsLibrary(...) Then use the shrinkwrap `Resolvers` API. > Offer the possibility to add Maven dependencies to a forge archive > ------------------------------------------------------------------ > > Key: FORGE-1234 > URL: https://issues.jboss.org/browse/FORGE-1234 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 2.0.0.Alpha12 > Reporter: Koen Aers > > It would be nice to do something along these lines: > {code} > ForgeArchive archive = ShrinkWrap > .create(ForgeArchive.class) > .addBeansXML() > .addAsAddonDependencies( > ...) > .addAsMavenDependencies( > MavenDependency.create("com.h2database:h2:1.3.167")); > {code} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1248) Redesign parser generics API: permit management of type variable bounds

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1248?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1248: -------------------------------------- Fix Version/s: 2.x Future > Redesign parser generics API: permit management of type variable bounds > ----------------------------------------------------------------------- > > Key: FORGE-1248 > URL: https://issues.jboss.org/browse/FORGE-1248 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1250) All Java types are not necessarily MemberHolders

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1250?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1250: -------------------------------------- Fix Version/s: 2.x Future > All Java types are not necessarily MemberHolders > ------------------------------------------------ > > Key: FORGE-1250 > URL: https://issues.jboss.org/browse/FORGE-1250 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1250) All Java types are not necessarily MemberHolders

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1250?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1250: ------------------------------------------- Hey Matt! Just checking in. How is the JavaParser stuff going? > All Java types are not necessarily MemberHolders > ------------------------------------------------ > > Key: FORGE-1250 > URL: https://issues.jboss.org/browse/FORGE-1250 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1249?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1249: -------------------------------------- Fix Version/s: 2.x Future > JavaAnnotationImpl should not implement InterfaceCapable > -------------------------------------------------------- > > Key: FORGE-1249 > URL: https://issues.jboss.org/browse/FORGE-1249 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.x Future > > -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1130) Implement a REST resource generation strategy for supporting links in the resource representations

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1130?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1130: -------------------------------------- Fix Version/s: 2.x Future > Implement a REST resource generation strategy for supporting links in the resource representations > -------------------------------------------------------------------------------------------------- > > Key: FORGE-1130 > URL: https://issues.jboss.org/browse/FORGE-1130 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Based on FORGE-1060 that introduces a strategy for creating two-level resource representations, it would also be useful to generate JAX-RS resources whose representations contain links to other resources. Note that this should support Java EE 6 (necessarily) and Java EE 7. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1139) Document the tag/branch naming scheme for Forge plugins

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1139?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1139. ------------------------------------- Resolution: Won't Fix Forge 2 will be released before this happens. So I'm closing this. > Document the tag/branch naming scheme for Forge plugins > ------------------------------------------------------- > > Key: FORGE-1139 > URL: https://issues.jboss.org/browse/FORGE-1139 > Project: Forge > Issue Type: Task > Components: Documentation > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The current documentation about the naming scheme for tags/branches for Forge plugins is confusing. This needs to be expanded with examples and with recommendations on when to choose a tag vs branch. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013