[JBoss JIRA] (FORGE-212) Classload dependencies of current project when performing certain operations
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-212?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-212:
----------------------------------
Fix Version/s: 2.x Future
(was: 2.0.0.Alpha5)
> Classload dependencies of current project when performing certain operations
> -----------------------------------------------------------------------------
>
> Key: FORGE-212
> URL: https://issues.jboss.org/browse/FORGE-212
> Project: Forge
> Issue Type: Feature Request
> Components: Maven Integration, Parsers / File Manipulation, Plugin API
> Affects Versions: 1.0.0.Alpha3
> Reporter: wiktorowski maximilien
> Priority: Minor
> Fix For: 2.x Future
>
>
> "Generating crud views for entities located into an external jar is a use case i'd like to see implemented in forge.
> In my case i have a model.jar containing my entities and an admin.war generated with seam forge. I'd like to use from-entity to generate scaffolding views in admin.war for the entities located in model.jar"
> This means that Forge will need to classload dependencies of the target project in order to perform reflection-based generation. This may also require a reflection-based meta-model such as what was done with Errai/GWT.
--
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
[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.x Future
(was: 2.0.0.Alpha5)
> 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.x Future
>
>
> 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
[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.x Future
(was: 2.0.0.Alpha5)
> 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.x Future
>
>
> 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
11 years
[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.x Future
(was: 2.0.0.Alpha5)
> 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.x Future
>
>
> 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
11 years