August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1139) Document the tag/branch naming scheme for Forge plugins

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1139: -------------------------------------- Summary: Document the tag/branch naming scheme for Forge plugins Key: FORGE-1139 URL: https://issues.jboss.org/browse/FORGE-1139 Project: Forge Issue Type: Task Components: Documentation Reporter: Vineet Reynolds Assignee: Vineet Reynolds The current documentation about the naming scheme for tags/branches for Forge plugins is confusing. This needs to be expanded with examples and with recommendations on when to choose a tag vs branch. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-957: ------------------------------------------ Something like this would work in Forge2: https://github.com/forge/core/blob/2.0/projects/api/src/main/java/org/jbo... This is used in the new-project command like so: `new-project --named "blah" --type javaee-7 --version 1.0 --topLevelPackage org.blah` Now, the interesting thing is that depending on the project type, we can also specify additional parameters that will become activated: `new-project --named "blah" --type javaee-7 --version 1.0 --topLevelPackage org.blah --profile web/full` So we can do web profile selection as part of the javaee7 project type, or we could just have multiple project types for each profile. It could go either way. > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.0.0.Final > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-378: ------------------------------------------ What would happen if someone starts working with a specific version of EE, then sets the "environment" to a different version? While I agree with this concept in principal, I don't think that this should be the primary method of exposing it. As I explained in an email to Forge-Dev: Our current plan is this - https://github.com/forge/core/blob/2.0/projects/api/src/main/java/org/jbo... This is used in the new-project command like so: `new-project --named "blah" --type javaee-7 --version 1.0 --topLevelPackage org.blah` Now, the interesting thing is that depending on the project type, we can also specify additional parameters that will become activated: `new-project --named "blah" --type javaee-7 --version 1.0 --topLevelPackage org.blah --profile web/full` So we can do web profile selection as part of the javaee7 project type, or we could just have multiple project types for each profile. It could go either way. > 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 > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1067) Adopt WebJars as encapsulation for Bootstrap and JQuery resources

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1067?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1067: ------------------------------------------ @Lincoln, I see your point. With WebJars, the direct inclusion of CSS/JS feels like the good old days of inclusion of all external libraries. Plus there is no easy way to upgrade a new version of Bootstrap except manually @Burr I like the multi-step wizards that makes sense in one provider but not in an other one @Max The WebJars Bootstrap is in Maven Central, so you shouldn't have to add an external repository http://mvnrepository.com/artifact/org.webjars/bootstrap. And yes, you need to have the exact version number in your css/js reference. But that is referenced once in your template. The good thing, though, is that you easily know which version of Boostrap/JQuery your are using. > 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 JQuery) into the war file. > For this to happen you just need to add the following Maven dependencies to the {{pom.xml}} : > {code} > <dependency> > <groupId>org.webjars</groupId> > <artifactId>bootstrap</artifactId> > <version>2.3.2</version> > </dependency> > <dependency> > <groupId>org.webjars</groupId> > <artifactId>jquery</artifactId> > <version>2.0.3</version> > </dependency> > {code} > Then, change the {{pageTemplate.xhtml}} so it looks like this : > {code} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title> > <link rel="icon" href="#{resource['favicon.ico']}"/> > <h:outputStylesheet library="webjars/bootstrap/2.3.2/css" name="bootstrap.min.css"/> > <h:outputStylesheet name="forge-style.css"/> > </h:head> > <h:body> > ... > ... > ... >  >  > <h:outputScript name="webjars/jquery/2.0.3/jquery.min.js"/> > <h:outputScript library="webjars/bootstrap/2.3.2/js" name="bootstrap.min.js"/> > </h:body> > </html> > {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 administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1138) "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1138?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1138. ---------------------------------- Fix Version/s: 1.4.1.Final Resolution: Done > "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar) > ----------------------------------------------------------------------------------------- > > Key: FORGE-1138 > URL: https://issues.jboss.org/browse/FORGE-1138 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 1.4.1.Final > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1138) "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1138?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1138: ---------------------------------------- How about: {code} 'forge update' only works when it is run outside from the IDE. The embedded Forge versions are automatically updated when there is a new version of the JBoss Tools Forge Plugin. If you want to use the latest version without waiting for a new plugin release, do the following: 1. Download the latest Forge version from http://forge.jboss.org and unzip in any place you may find convenient; 2. In Window->Preferences, look for Forge->Installed Forge Runtimes and add the path to your installation and make it the default runtime choice; 3. Start the forge console. You should see it is running the latest version. {code} > "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar) > ----------------------------------------------------------------------------------------- > > Key: FORGE-1138 > URL: https://issues.jboss.org/browse/FORGE-1138 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1138) "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1138?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1138: -------------------------------------- Assignee: George Gastaldi > "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar) > ----------------------------------------------------------------------------------------- > > Key: FORGE-1138 > URL: https://issues.jboss.org/browse/FORGE-1138 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1138) "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1138?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1138: ---------------------------------------- Any suggestions for the warning message to be displayed? > "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar) > ----------------------------------------------------------------------------------------- > > Key: FORGE-1138 > URL: https://issues.jboss.org/browse/FORGE-1138 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.4.0.Final > Reporter: Lincoln Baxter III > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1138) "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar)

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1138: ----------------------------------------- Summary: "forge update" should be disabled in the IDE (using -Pforge.compatability.ide or similar) Key: FORGE-1138 URL: https://issues.jboss.org/browse/FORGE-1138 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.4.0.Final Reporter: Lincoln Baxter III -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1067) Adopt WebJars as encapsulation for Bootstrap and JQuery resources

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1067?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on FORGE-1067: -------------------------------------------- I like the idea but I do have my concerns since: A) this would require webjar to have the exact version we support available. i.e. we would need to somehow QE that the official bootstrap.* files we support is actually the ones explicitly included into the files... B) initial blog says you need to add additional repositories to your project: <repositories> <repository> <id>webjars</id> <url>http://webjars.github.com/m2</url> </repository> </repositories> That is not good if true. B) looks like users would have to update all their specific version references of css/js in all their html pages when updates are made ? C) how does it work in m2e/eclipse and other IDE integrations ? If I read it right the actual javascript and css is not actually available in the filesystem making file:// viewing and things like livereload not working out of the box. D) Is this is only for serverside processed html (i.e. JSF) since the resources are on the classpath, not your project ? E) Since the resources are on the classpath my assumption is you won't see changes to these before restarting the module - this is probably not a big deal since it is just for a dependendent library but debugging/tweaking does becomes harder with this on first look at least. ...on the other hand I really like it since it does make dependency fetching much saner...but is it worth the loss of livereload, incremental updates, ide tooling ? > 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 JQuery) into the war file. > For this to happen you just need to add the following Maven dependencies to the {{pom.xml}} : > {code} > <dependency> > <groupId>org.webjars</groupId> > <artifactId>bootstrap</artifactId> > <version>2.3.2</version> > </dependency> > <dependency> > <groupId>org.webjars</groupId> > <artifactId>jquery</artifactId> > <version>2.0.3</version> > </dependency> > {code} > Then, change the {{pageTemplate.xhtml}} so it looks like this : > {code} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > <h:head> > <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title> > <link rel="icon" href="#{resource['favicon.ico']}"/> > <h:outputStylesheet library="webjars/bootstrap/2.3.2/css" name="bootstrap.min.css"/> > <h:outputStylesheet name="forge-style.css"/> > </h:head> > <h:body> > ... > ... > ... >  >  > <h:outputScript name="webjars/jquery/2.0.3/jquery.min.js"/> > <h:outputScript library="webjars/bootstrap/2.3.2/js" name="bootstrap.min.js"/> > </h:body> > </html> > {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 administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013