February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-368?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-368: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Return list of properties based on higher-level understanding > ------------------------------------------------------------- > > Key: FORGE-368 > URL: https://issues.jboss.org/browse/FORGE-368 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Richard Kennard > Fix For: 2.0.0.Alpha2 > > > Hi guys, > As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say... > field string --named foo > ...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do... > org.jboss.forge.parser.java.JavaClass.getMethods() > ...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do... > org.jboss.forge.parser.java.JavaClass.getFields() > ...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored). > Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter? > If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-479) Implement @CommandScoped to enable Plugin - Facet communication

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-479?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-479: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Implement @CommandScoped to enable Plugin - Facet communication > --------------------------------------------------------------- > > Key: FORGE-479 > URL: https://issues.jboss.org/browse/FORGE-479 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.CR2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > (05:04:44 PM) Lincoln: i want to implement @CommandScoped > (05:04:46 PM) Lincoln: that would be nice > (05:04:49 PM) Lincoln: and not hard to do actually > (05:05:00 PM) Lincoln: actually, is that there? > (05:05:13 PM) Paul Bakker: no > (05:05:17 PM) Paul Bakker: but good idea > (05:05:54 PM) Lincoln: easy to tie into the command execution lifecycle > (05:06:01 PM) Lincoln: would be nice to add extension points there as well > (05:06:04 PM) Lincoln: could be helpful for plugins > (05:06:09 PM) Lincoln: before/after command > (05:06:47 PM) Paul Bakker: yes should really do this, very helpful I think for plugin/facet communication > (05:07:03 PM) Lincoln: yeah that could be a recommended pattern actually > (05:07:11 PM) Lincoln: if it works well > (05:07:21 PM) Paul Bakker: yep -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-510: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > Fix For: 2.0.0.Alpha2 > > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-563) Create a class lookup index

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-563: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Create a class lookup index > --------------------------- > > Key: FORGE-563 > URL: https://issues.jboss.org/browse/FORGE-563 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > Fix For: 2.0.0.Alpha2 > > > We need to support an index of classes and dependencies which contain them. > This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc. > We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-675) Testing under Weblogic 12c

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-675?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-675: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Testing under Weblogic 12c > -------------------------- > > Key: FORGE-675 > URL: https://issues.jboss.org/browse/FORGE-675 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha2 > > > It could be a nice thing if the Forge tests could run also in Weblogic 12c, maybe in a different profile. We must be aware of the licensing issues this may bring before doing it. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-598) CommandCompleter should permit the highlight of some candidate items (for use then as recommended candidate)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-598?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-598: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > CommandCompleter should permit the highlight of some candidate items (for use then as recommended candidate) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-598 > URL: https://issues.jboss.org/browse/FORGE-598 > Project: Forge > Issue Type: Feature Request > Components: Shell, Usability > Affects Versions: 1.0.5.Final > Reporter: Rafael Benevides > Labels: commandcompleter, shell, > Fix For: 2.0.0.Alpha2 > > > For example: > {code} > someplugin --option <TAB> > **CANDIDATE3** (show in WHITE and as first item) CANDIDATE1 CANDIDATE2 > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-424) JavaParser does not understand wildcard imports like "javax.persistence.*"

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-424?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-424: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > JavaParser does not understand wildcard imports like "javax.persistence.*" > -------------------------------------------------------------------------- > > Key: FORGE-424 > URL: https://issues.jboss.org/browse/FORGE-424 > Project: Forge > Issue Type: Technical task > Components: Parsers / File Manipulation > Affects Versions: 1.1.0.Final > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata: > {code}package demo.entities; > import javax.persistence.*; > @Entity > public class Contact implements java.io.Serializable { > @Id > private @GeneratedValue(strategy = GenerationType.AUTO) > @Column(name = "id", updatable = false, nullable = false) > Long id = null; > @Version > private @Column(name = "version") > int version = 0; > public Long getId() { > return this.id; > } > public void setId(final Long id) { > this.id = id; > } > public int getVersion() { > return this.version; > } > public void setVersion(final int version) { > this.version = version; > } > @Override > public boolean equals(Object that) { > if (this == that) { > return true; > } > if (that == null) { > return false; > } > if (getClass() != that.getClass()) { > return false; > } > if (id != null) { > return id.equals(((Contact) that).id); > } > return super.equals(that); > } > @Override > public int hashCode() { > if (id != null) { > return id.hashCode(); > } > return super.hashCode(); > } > private String name; > public String getName() { > return this.name; > } > public void setName(final String name) { > this.name = name; > } > public String toString() { > return "" + name; > } > }{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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-628) CommandInterceptor design issues

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-628?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-628: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > CommandInterceptor design issues > -------------------------------- > > Key: FORGE-628 > URL: https://issues.jboss.org/browse/FORGE-628 > Project: Forge > Issue Type: Story > Components: Plugin API > Affects Versions: 1.0.5.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha2 > > > The design of the org.jboss.forge.shell.spi.CommandInterceptor class seems misleading. Actually it's not possible to intercept a command execution. It only transforms the input before executing. > Maybe it should be called CommandTransformer. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-379) Add user profiles

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-379?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-379: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Add user profiles > ----------------- > > Key: FORGE-379 > URL: https://issues.jboss.org/browse/FORGE-379 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.0.0.Beta3 > Reporter: Pete Muir > Fix For: 2.0.0.Alpha2 > > > At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-440) A pom.xml which contains comments loses all of them after Forge operates on it.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-440?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-440: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > A pom.xml which contains comments loses all of them after Forge operates on it. > ------------------------------------------------------------------------------- > > Key: FORGE-440 > URL: https://issues.jboss.org/browse/FORGE-440 > Project: Forge > Issue Type: Bug > Components: Maven Integration > Affects Versions: 1.0.6.Final > Environment: HEAD > Reporter: Pete Muir > Priority: Critical > Fix For: 2.0.0.Alpha2 > > > Also looses formatting, but this is less of an issue. -- 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013