[JBoss JIRA] (FORGE-1629) Being able to add comments to a script
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1629:
----------------------------------------
Summary: Being able to add comments to a script
Key: FORGE-1629
URL: https://issues.jboss.org/browse/FORGE-1629
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.1.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
In Forge 1 we could add comments to a script, which was very handy. It had this syntax :
{code}
@/* Forge 2.x Script */ ;
@/* Generates the draft of the application */ ;
clear ;
export ACCEPT_DEFAULTS=true ;
track-changes ;
@/* ========================== */;
@/* == Creating the project == */;
@/* ========================== */;
project-new --named pluralsight-persistence --topLevelPackage com.pluralsight.persistence.module07 --type war --finalName module07 ;
@/* ========================= */;
@/* == Setting up the model == */;
@/* ========================== */;
jpa-setup ;
constraint-setup ;
{code}
It would be nice to be able to add comments. Either with this syntax, or a more Java syntax :
{code}
/** == Setting up the model == */
{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, 1 month
[JBoss JIRA] (FORGE-1628) Support a facet for templates that are provided by the project
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1628:
--------------------------------------
Summary: Support a facet for templates that are provided by the project
Key: FORGE-1628
URL: https://issues.jboss.org/browse/FORGE-1628
Project: Forge
Issue Type: Feature Request
Components: Projects
Affects Versions: 2.1.1.Final
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Introduce a new Facet {{TemplateFacet}} for supporting project-provided templates. This facet should be enabled when a {{src/main/templates}} directory is present in a Maven project structure (and other directories for other project types).
This facet is meant to be used to provide templates that will override Forge-supplied templates.
--
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, 1 month
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1432:
-------------------------------------
Parent Issue: FORGE-1627 (was: FORGE-1491)
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.1.0.Final
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {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, 1 month
[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1625?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1625:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Assignee: Vineet Reynolds
Fix Version/s: 2.1.2.Final
Resolution: Done
> Prevent UIWizards from being merged into dialogs
> ------------------------------------------------
>
> Key: FORGE-1625
> URL: https://issues.jboss.org/browse/FORGE-1625
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 2.1.1.Final
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
> Priority: Minor
> Fix For: 2.1.2.Final
>
>
> When I add multiple UICommand and UIWizard instances to create a single dialog page, like so:
> {noformat}
> NavigationResultBuilder builder = NavigationResultBuilder.create();
> builder.add(getMetadata(uiContext), setupFlow);
> return builder.build();
> {noformat}
> the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution).
> Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page.
--
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, 1 month
[JBoss JIRA] (FORGE-1625) Prevent UIWizards from being merged into dialogs
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/FORGE-1625?page=com.atlassian.jira.plugin... ]
Vineet Reynolds updated FORGE-1625:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/394
An IllegalArgumentException is thrown when it is detected that a UIWizard instance is present in the list of arguments when creating a NavigationResultEntry.
> Prevent UIWizards from being merged into dialogs
> ------------------------------------------------
>
> Key: FORGE-1625
> URL: https://issues.jboss.org/browse/FORGE-1625
> Project: Forge
> Issue Type: Feature Request
> Components: UI - API
> Affects Versions: 2.1.1.Final
> Reporter: Vineet Reynolds
> Priority: Minor
>
> When I add multiple UICommand and UIWizard instances to create a single dialog page, like so:
> {noformat}
> NavigationResultBuilder builder = NavigationResultBuilder.create();
> builder.add(getMetadata(uiContext), setupFlow);
> return builder.build();
> {noformat}
> the wizard pages are also added to the dialog page. This results in erroneous behavior since only the first page of the wizard is added and displayed. The second and subsequent pages of a wizard are omitted (even from execution).
> Since it is obvious that the next page in a wizard cannot be determined statically, and should determined at runtime, we must prevent wizards from being merged into a single page.
--
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, 1 month
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1432:
-------------------------------------------
So, I figured out what this issue is. It has to do with the fact that "export" is a native Aesh command and not a forge one, so we are never notified when the command completes. Will need to think about how to fix this :) But good news is that I can reproduce and I know "why" if not yet "how to fix."
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.1.0.Final
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {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, 1 month
[JBoss JIRA] (FORGE-1626) Install addon from git repository
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGE-1626:
--------------------------------------
Summary: Install addon from git repository
Key: FORGE-1626
URL: https://issues.jboss.org/browse/FORGE-1626
Project: Forge
Issue Type: Feature Request
Components: Addon Manager
Affects Versions: 2.x Future
Reporter: Ivan St. Ivanov
Forge should be able to install addons from a remote [git] repository.
In order to do that, Forge will have to first download the addon sources, then build it and finally install the built artifact.
Remark: There is already git-tools addon that can be used for pulling the sources.
--
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, 1 month
[JBoss JIRA] (FORGE-1599) Introduce a cache addon
by Adam Wyłuda (JIRA)
[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ]
Adam Wyłuda commented on FORGE-1599:
------------------------------------
I think we could make our custom cache builder with additional options, and in case user wants to use it then he could create his own Cache producer which would use this extension.
I don't know if that will work with many addons at the same time, is there some kind of addon scope in Forge CDI? Otherwise it will be necessary to use own custom annotations (or @Named) for caches other than default.
> Introduce a cache addon
> -----------------------
>
> Key: FORGE-1599
> URL: https://issues.jboss.org/browse/FORGE-1599
> Project: Forge
> Issue Type: Feature Request
> Components: Blessed Plugins
> Reporter: George Gastaldi
> Assignee: Adam Wyłuda
> Fix For: 2.x Future
>
>
> This would allow other addons to cache state. It should allow individual configurations of each cache.
> There should also have a CacheFactory, to allow creation of caches on-demand.
--
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, 1 month