April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-792) Forge should support a cleaner way to install a plugin from a binary

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-792?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-792. ------------------------------------ Fix Version/s: 2.0.0.Alpha1 Resolution: Done Won't fix for Forge 1. This is implemented in Forge 2. > Forge should support a cleaner way to install a plugin from a binary > -------------------------------------------------------------------- > > Key: FORGE-792 > URL: https://issues.jboss.org/browse/FORGE-792 > Project: Forge > Issue Type: Story > Reporter: John Ament > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > Say that I am working on a closed source plugin, or not publicly available. It should be possible to point to a pre-built JAR, either URL or local path, and install that JAR locally. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-792) Forge should support a cleaner way to install a plugin from a binary

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-792?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-792: ---------------------------------------- Assignee: Lincoln Baxter III > Forge should support a cleaner way to install a plugin from a binary > -------------------------------------------------------------------- > > Key: FORGE-792 > URL: https://issues.jboss.org/browse/FORGE-792 > Project: Forge > Issue Type: Story > Reporter: John Ament > Assignee: Lincoln Baxter III > > Say that I am working on a closed source plugin, or not publicly available. It should be possible to point to a pre-built JAR, either URL or local path, and install that JAR locally. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-754) @Inject Instance<ExportedServiceBlah> instances; does not work. Infinite recursion.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-754?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-754: ---------------------------------------- Assignee: Lincoln Baxter III > @Inject Instance<ExportedServiceBlah> instances; does not work. Infinite recursion. > ----------------------------------------------------------------------------------- > > Key: FORGE-754 > URL: https://issues.jboss.org/browse/FORGE-754 > Project: Forge > Issue Type: Bug > Components: Container > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > Infinite recursion results from > {code} > @Inject > private Instance<Converter> converterInstances; > ... > for( Converter c : converterInstances ) { > // etc > } > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-758) In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-758?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-758: ------------------------------------------ Right you are! We'll be taking care of this soon, as we are doing a documentation overhaul. > In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty > ---------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-758 > URL: https://issues.jboss.org/browse/FORGE-758 > Project: Forge > Issue Type: Task > Components: Documentation > Environment: Firefox. > Reporter: Alceu Medeiros > Priority: Blocker > Labels: documentation_consistency > > In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty: > http://forge.jboss.org/docs/plugin_development/important-apis.html > Write plugins that reads and writes resources and java classes is the most complex functionality that Forge provides. Thus, this is the section that documentation is most necessary. Just to justify why I flagged this issue as "Blocker". My learning curve not even made a curve because of this. > By the way, congratulations for the team. Very nice project! > Thanks in advance. > Best regards. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-758) In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-758?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-758: ------------------------------------------ BUT. If you'd like to help out! - http://forge.jboss.org/docs/get_involved/write-docs.html#content Code templates are just .jv files that have java syntax and can be passed to the javaparser to use as a basic starting point :) > In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty > ---------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-758 > URL: https://issues.jboss.org/browse/FORGE-758 > Project: Forge > Issue Type: Task > Components: Documentation > Environment: Firefox. > Reporter: Alceu Medeiros > Priority: Blocker > Labels: documentation_consistency > > In Documentation, the "Code templates" topic in the "Important APIs" page of the section "Developing Plugins" is empty: > http://forge.jboss.org/docs/plugin_development/important-apis.html > Write plugins that reads and writes resources and java classes is the most complex functionality that Forge provides. Thus, this is the section that documentation is most necessary. Just to justify why I flagged this issue as "Blocker". My learning curve not even made a curve because of this. > By the way, congratulations for the team. Very nice project! > Thanks in advance. > Best regards. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-841) Add Forge as a container in the Servers tab

by George Gastaldi (JIRA)

George Gastaldi created FORGE-841: ------------------------------------- Summary: Add Forge as a container in the Servers tab Key: FORGE-841 URL: https://issues.jboss.org/browse/FORGE-841 Project: Forge Issue Type: Feature Request Components: Eclipse UI Affects Versions: 2.0.0.Alpha1 Reporter: George Gastaldi Assignee: Koen Aers Fix For: 2.0.0.Alpha2 Installing of addons could be made as dragging-drop a forge addon project in this server. Startup and Shutdown are also easily managed this way. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-835: --------------------------------------- Yes, I think this is the way to go. > Forge field plugin doesn't support lobs / byte arrays > ----------------------------------------------------- > > Key: FORGE-835 > URL: https://issues.jboss.org/browse/FORGE-835 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > Fix For: 1.2.3.Final > > > Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database. > In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob. > Forge should be able to generate such fields when the command: > {code:java} > field lob --named <field-name> > {code} > is issued > The exact name of the command (lob or bytearray or anything) is subject to discussion. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov commented on FORGE-835: --------------------------------------- Hey George, Thanks for mentioning that! I did a quick research and found that on some databases JPA creates the column with different type based on the 'length' attribute of the @Column annotation. Should we always set it to MAX_VALUE or we should let the user configure it with an option (defaulting to MAX_VALUE)? Something like: field lob --named <field-name> [--length <length>] Cheers, Ivan > Forge field plugin doesn't support lobs / byte arrays > ----------------------------------------------------- > > Key: FORGE-835 > URL: https://issues.jboss.org/browse/FORGE-835 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: Ivan St. Ivanov > Assignee: Ivan St. Ivanov > Fix For: 1.2.3.Final > > > Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database. > In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob. > Forge should be able to generate such fields when the command: > {code:java} > field lob --named <field-name> > {code} > is issued > The exact name of the command (lob or bytearray or anything) is subject to discussion. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-583) Include Forge JavaDoc in Distribution download.

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-583?page=com.atlassian.jira.plugin.... ] Ivan St. Ivanov updated FORGE-583: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/forge/core/pull/235, https://github.com/forge/core/pull/240, https://github.com/forge/core/pull/282, https://github.com/forge/core/pull/304 (was: https://github.com/forge/core/pull/235, https://github.com/forge/core/pull/240, https://github.com/forge/core/pull/282) > Include Forge JavaDoc in Distribution download. > ----------------------------------------------- > > Key: FORGE-583 > URL: https://issues.jboss.org/browse/FORGE-583 > Project: Forge > Issue Type: Task > Components: Documentation, Forge Build > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Assignee: Ivan St. Ivanov > Labels: starter > Fix For: 1.2.3.Final > > > The Forge API JavaDocs should be included in the Forge Distribution. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-840) Provide a dependency information repository for the current project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-840?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-840: ------------------------------------- Assignee: George Gastaldi > Provide a dependency information repository for the current project > ------------------------------------------------------------------- > > Key: FORGE-840 > URL: https://issues.jboss.org/browse/FORGE-840 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.2.2.Final, 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.2.3.Final, 2.0.0.Alpha2 > > > It would be nice if Forge could provide a query-able mechanism for a project so it would be possible to retrieve information like: > - All available @Entity mapped classes; > - Classes that implement a specific interface; > - Is a specific class present in the configured pom.xml? > That would enrich user experience and also allow the writing of smarter plugins. -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013