April 2013 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-479?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-479: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > (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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-378: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Add "environments" as a first class construct > --------------------------------------------- > > Key: FORGE-378 > URL: https://issues.jboss.org/browse/FORGE-378 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell, Usability > Reporter: Pete Muir > Fix For: 2.0.0.Alpha4 > > > For example: > {code} > set environment JBOSS_AS7 --version 7.1.0.Final > {code} > Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. > For example, the persistence plugin could read from this, changing > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS7 > {code} > to > {code} > persistence setup > {code} > Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. > Lot's of other places where this could provide better defaulting, or remove the need to ask questions. > This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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

12 years, 12 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-424?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-424: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-379?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-379: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-297) Should provide ability to specify mutually exclusive command options

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-297?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-297: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Should provide ability to specify mutually exclusive command options > -------------------------------------------------------------------- > > Key: FORGE-297 > URL: https://issues.jboss.org/browse/FORGE-297 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha1 > Reporter: Lincoln Baxter III > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > When developing Plugin @Commands, it is sometimes convenient to specify options from which only one must be selected > For example: > * providing a maven GAV "org.jboss.seam.forge:forge-parent:1.0.0" > * specifying the path to said project "~/projects/forge/" > Both inputs are valid, but only one is required. If one is selected, the other should be hidden from completion. (Or some such interaction.) > If both are missing, Forge should prompt for one to be completed. -- 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

12 years, 12 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-510: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-331) Get online help from plugin's javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-331?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-331: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Get online help from plugin's javadoc > ------------------------------------- > > Key: FORGE-331 > URL: https://issues.jboss.org/browse/FORGE-331 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Reporter: Jonathan Fuerth > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > IDEs already have lots of great tooling to help write good javadoc and keep it neatly formatted and up to date. It would be excellent if forge's source of help text for plugins came straight from the javadoc. This could be done either via a doclet that operates on the Java source code, or by scraping the output of the default doclet (like Eclipse will do if you attach generated JavaDoc rather than library source code). > Lowering the barrier to providing high-quality documentation should help encourage plugin authors to provide good help, and in turn that should help everyone pick up and learn Forge faster. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-734) AnnotationTarget should be renamed to AnnotationCapable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-734?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-734: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > AnnotationTarget should be renamed to AnnotationCapable > ------------------------------------------------------- > > Key: FORGE-734 > URL: https://issues.jboss.org/browse/FORGE-734 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > In order to keep the API consistent, I propose that the interface > {code}org.jboss.forge.parser.java.AnnotationTarget{code} > should be renamed to > {code}org.jboss.forge.parser.java.AnnotationCapable{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

12 years, 12 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 George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-598?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-598: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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: UI - Shell, Usability > Affects Versions: 1.0.5.Final > Reporter: Rafael Benevides > Labels: commandcompleter, shell, > Fix For: 2.0.0.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-657) Missing mime-mapping in web.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-657?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-657: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Missing mime-mapping in web.xml > ------------------------------- > > Key: FORGE-657 > URL: https://issues.jboss.org/browse/FORGE-657 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: George Gastaldi > Labels: starter > Fix For: 2.0.0.Alpha4 > > > To eliminate the annoying log jboss server log: > {code} > 23:59:54,914 AVVERTENZA [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-1) JSF1091: No mime type could be found for file favicon.ico. To resolve this, add a mime-type mapping to the applications web.xml > {code} > you should add on web.xml: > {code:xml} > <mime-mapping> > <extension>ico</extension> > <mime-type>image/x-icon</mime-type> > </mime-mapping> > {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

12 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013