8:11 a.m.
[
https://issues.jboss.org/browse/FORGE-1098?page=com.atlassian.jira.plugin...
]
Vineet Reynolds updated FORGE-1098:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/342
Added checks to determine if the scaffold type to use is being determined during the
{{setup}} command execution or not.
Additionally, in the PR, should the {{setup}} command be executed, project attributes are
modified to ensure that scaffold providers can verify a smaller set of constraints for
activating the provider. This is necessary, since the {{setup}} command requires the
Scaffold provider facet to be installed first, before it proceeds to invoke the actual
setup logic. Without installing the facet, the setup logic will fail since the
project-facet linkage will not be established.
Therefore Scaffold providers that are facets, should allow for themselves to be installed
with just the required facets and dependencies, and then later setup completely through
the setup command.
Once set up the more stringent conditions can be used to detect if they are installed or
not, otherwise the scaffold plugin commands will be activated irrespective of compliance
with the more stringent conditions.
Scaffold setup command does not setup the chosen scaffold
---------------------------------------------------------
Key: FORGE-1098
URL: https://issues.jboss.org/browse/FORGE-1098
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.3.3.Final
Reporter: Vineet Reynolds
Priority: Blocker
On running the {{scaffold setup}} or {{scaffold-x setup}} commands, the default Faces
scaffolding provider is chosen even though a different provider was to be installed.
As an example, instead of setting up the AngularJS provider the Faces provider is
installed:
{noformat}
[ticket-monster] demo $ scaffold-x setup --scaffoldType angularjs
***INFO*** Using currently installed scaffold [faces]
? [/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html] File exists,
overwrite? [Y/n]
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/favicon.ico
Wrote
/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/paginator.xhtml
Wrote
/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.xhtml
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/error.xhtml
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/add.png
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/bootstrap.css
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/false.png
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/favicon.ico
Wrote
/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-logo.png
Wrote
/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-style.css
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/remove.png
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/search.png
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/true.png
Wrote
/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/jboss-community.png
Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/WEB-INF/web.xml
{noformat}
--
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