[JBoss JIRA] (FORGE-1010) Plugin commands remove-plugin and list-plugins
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1010?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III closed FORGE-1010.
-------------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha6
Resolution: Done
Solve in 2.0
> Plugin commands remove-plugin and list-plugins
> ----------------------------------------------
>
> Key: FORGE-1010
> URL: https://issues.jboss.org/browse/FORGE-1010
> Project: Forge
> Issue Type: Enhancement
> Components: Plugin API
> Affects Versions: 1.3.2.Final
> Reporter: Rajmahendra Hegde
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha6
>
>
> Currently the two commands
> 1. remove-plugin
> 2. list-plugins
> Runs mainly on display and consuming plugin as a long string
> org.jrebirth.forge-jrebirth-plugin:1.3.2.Final:1.0.0-SNAPSHOT-0ecc7548-4e2e-47e0-a17a-34c95026568b
> As the install-plugin command comes in the same group of plugins. We can enhance these two commands like...
> list-plugins
> Instead of just displaying a full line of string we can display some info about the plugin like...
> Plugin name (servlet, rest etc. (user defined)) : Maven location(A:G:V) | Author | ... etc
> remove-plugin
> like install-plugin we can provide the plugin name. ( we can also use completer using installed plugins in the system)
--
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
10 years, 10 months
[JBoss JIRA] (FORGE-781) forge install-plugin command fails with cygwin
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-781?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on FORGE-781:
------------------------------------------
Hi. Could you please try this now with Forge 1.4.0? It may be resolved now since we made a lof of file-path changes.
> forge install-plugin command fails with cygwin
> -----------------------------------------------
>
> Key: FORGE-781
> URL: https://issues.jboss.org/browse/FORGE-781
> Project: Forge
> Issue Type: Bug
> Components: Init Scripts, Windows
> Affects Versions: 1.1.2.Final, 1.1.3.Final, 1.2.0.Final
> Environment: cygwin
> Reporter: Andreas Karalus
> Fix For: 1.x Future
>
>
> @See: https://community.jboss.org/message/797250
> forge install-plugin <plugin> command fails if it is called from cygwin.
> I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces)
> I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins
> {code}
> roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\
> {code}
> The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if forge was called from cygwin first time).
> {code}
> 297646@TB01448C ~/workspaces/forge-jbossas-quickstart
> # forge
> Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b
> org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.)
> at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
> at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204)
> at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254)
> at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125)
> at java.lang.Thread.run(Thread.java:662)
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |___/
> JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ]
> [jboss-as-quickstarts-parent] forge-jbossas-quickstart $
> {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
10 years, 10 months
[JBoss JIRA] (FORGE-786) Scaffolds shouldn't be so hard reliant on JPA Entities
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-786?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds commented on FORGE-786:
---------------------------------------
John, could you please take a look at the new Scaffold-X API released in Forge 1.3.0. The Scaffold Provider is no longer required to support only JPA entities, and this constraint has been removed. However, no existing scaffold provider that we support has this feature yet; the individual scaffold providers we support (Faces and AngularJS) require JPA entities due to the nature of the classes they produce or rely on.
New scaffold providers can be written that do not have this constraint. If you consider this API as sufficient we can close this.
> Scaffolds shouldn't be so hard reliant on JPA Entities
> ------------------------------------------------------
>
> Key: FORGE-786
> URL: https://issues.jboss.org/browse/FORGE-786
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.0.Final
> Reporter: John Ament
> Fix For: 1.x Future
>
>
> Scaffolds are really nice, however they all need to work against JPA entities. What if you're not dealing with an entity, and instead have a data transformation layer that occurs first? HTML5/CSS3 type frameworks use rest and as a result the underlying object state may differ. Need to better support a scaffolding for non JPA entity classes.
--
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
10 years, 10 months