From jira-events at lists.jboss.org Mon Aug 26 12:56:26 2013 Content-Type: multipart/mixed; boundary="===============3022235312439238535==" MIME-Version: 1.0 From: Vineet Reynolds (JIRA) To: forge-issues at lists.jboss.org Subject: [forge-issues] [JBoss JIRA] (FORGE-1067) Adopt WebJars as encapsulation for Bootstrap and JQuery resources Date: Mon, 26 Aug 2013 12:56:26 -0400 Message-ID: In-Reply-To: JIRA.12497775.1375367421000@jira02.app.mwc.hst.phx2.redhat.com --===============3022235312439238535== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/FORGE-1067?page=3Dcom.atlassian.jira.= plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12799287#c= omment-12799287 ] = Vineet Reynolds commented on FORGE-1067: ---------------------------------------- I spoke just half of my mind there as always :) As you may notice, any parameter for the scaffold command will have to be c= onsidered by all scaffold providers, and it may not make sense for some of = them. One of the things I intend to do in Forge 2 is to investigate whether= scaffold providers can acquire more control over the parameters they are s= upplied via multi-step wizards that are tailored towards the providers. A F= aces scaffold provider could therefore have an option to use WebJars to man= age dependencies, while a HTML5 scaffold provider could have an option to u= se Bower. Given that I'm shortly beginning work on Forge 2, I'd prefer investigating = the feasibility of doing this at the earliest and may it ready if possible = in Sept, instead of bringing this in Forge 1 and then porting or rewriting = it for Forge 2. = > Adopt WebJars as encapsulation for Bootstrap and JQuery resources > ----------------------------------------------------------------- > > Key: FORGE-1067 > URL: https://issues.jboss.org/browse/FORGE-1067 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Antonio Goncalves > Fix For: 1.x Future > > > At the moment JBoss Forge copies the {{bootstrap.css}} into the resources= directory. It would be nice to use WebJar [1] to package Bootstrap (and JQ= uery) into the war file. = > For this to happen you just need to add the following Maven dependencies = to the {{pom.xml}} : > {code} > > org.webjars > bootstrap > 2.3.2 > > > org.webjars > jquery > 2.0.3 > > {code} > Then, change the {{pageTemplate.xhtml}} so it looks like this : = > {code} > > xmlns:h=3D"http://java.sun.com/jsf/html" > xmlns:ui=3D"http://java.sun.com/jsf/facelets"> > > #{empty pageTitle ? '{#pageTitle}' : pageTitle} > > > > > > ... > ... > ... > > > > > > > {code} > And of course, get rid of the {{bootstrap.css}} file ;o) > [1] http://www.webjars.org/ > [1] http://www.jamesward.com/2012/10/31/webjars-officially-launched > See also : https://issues.jboss.org/browse/RF-12584 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira --===============3022235312439238535==--