August 2013 - forge-issues - Jboss List Archives

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1067?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1067: ------------------------------------------- I would love to do this, but in the default faces scaffold we can't depend on any non-EE libraries, unfortunately. So we could do this in an enhanced scaffold or an extension, just not the built in one. > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-286) Forge needs a de-centralized plugin distribution and repository system

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-286?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-286: ---------------------------------------- Assignee: (was: Lincoln Baxter III) > Forge needs a de-centralized plugin distribution and repository system > ---------------------------------------------------------------------- > > Key: FORGE-286 > URL: https://issues.jboss.org/browse/FORGE-286 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Plugin API > Affects Versions: 1.0.0.Alpha1 > Environment: All > Reporter: Lincoln Baxter III > Priority: Critical > Labels: Maven > Fix For: 1.x Future > > > There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven. > Features Forge would need to provide: > 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity > ------------------------------------------------------------------------------------------ > $ forge plugin-find prettyfaces > Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts. > * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1] > * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0 > $ forge plugin-install prettyfaces --version 3.1.0 > ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes. > $ forge plugin-list > Listing installed plugins: > * prettyfaces [3.1.0] > * forge-scaffold [1.0.0.Alpha1] > * forge-javaee6 [1.0.0.Alpha1] > * home-control [1.0.0.Alpha1] > $ forge plugin-remove prettyfaces > Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y > ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes. > ------------------------------------------------------------------------------------------ > 2) Plugin repository management (add/remove/edit/list current plugin repository targets.) > ------------------------------------------------------------------------------------------ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen > $ forge repo-add http://javaee.org/forge/repository/ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > * 4. http://jboss.org/forge/repository/ > * 5. http://javaee.org/forge/repository/ > $ forge repo-del 5 > ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}] > ------------------------------------------------------------------------------------------ > 3) Auto-update functionality > Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins. > 4) A meta-data system of identifying compatible versions of plugins w/running version of forge. > Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1065) Furnace container extension API should provide an EventManager for handling cross-container events portably

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1065?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1065. ------------------------------------- Resolution: Done > Furnace container extension API should provide an EventManager for handling cross-container events portably > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-1065 > URL: https://issues.jboss.org/browse/FORGE-1065 > Project: Forge > Issue Type: Feature Request > Components: Event Bus, Furnace (Container) > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > Currently the CDI addon is the only container type that supports events, and they will not be compatible with each other, so in order for this to work, furnace must provide an `EventManager` API for addon containers to implement, then handle the event propagation itself. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-124) AngularJS scaffold is activated even though it was not setup

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-124: -------------------------------------------- Summary: AngularJS scaffold is activated even though it was not setup Key: FORGEPLUGINS-124 URL: https://issues.jboss.org/browse/FORGEPLUGINS-124 Project: Forge Plugins Issue Type: Bug Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds On opening the TicketMonster sources and executing project list-facets, the AngularJS scaffolding facet is shown as installed. This is even though {{scaffold-x setup}] was not executed previously, and also despite the lack of artifacts required by the AngularJS scaffold. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1083) Faces scaffold is activated even though it was not setup

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1083?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1083: ----------------------------------- Affects Version/s: 1.3.3.Final > Faces scaffold is activated even though it was not setup > -------------------------------------------------------- > > Key: FORGE-1083 > URL: https://issues.jboss.org/browse/FORGE-1083 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > > On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}] was not executed previously, and also despite the lack of artifacts required by the Faces scaffold. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1083) Faces scaffold is activated even though it was not setup

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1083: -------------------------------------- Summary: Faces scaffold is activated even though it was not setup Key: FORGE-1083 URL: https://issues.jboss.org/browse/FORGE-1083 Project: Forge Issue Type: Bug Components: Scaffold Reporter: Vineet Reynolds On opening the TicketMonster sources and executing {{project list-facets}}, the Faces scaffolding facet is shown as installed. This is even though {{scaffold setup}] was not executed previously, and also despite the lack of artifacts required by the Faces scaffold. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1081) REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1081?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1081. ---------------------------------- Assignee: Vineet Reynolds Resolution: Done Pushed upstream: https://github.com/forge/core/commit/2a8c58ce99e62ba79a6c08a39490ea14c189... > REST plugin should create the REST resources in the same package as the @ApplicationPath annotated class > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-1081 > URL: https://issues.jboss.org/browse/FORGE-1081 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > When REST is setup in a project and activated through the {{@ApplicationPath}} annotated class, it would be preferable to generate all the REST resources in the same package instead of using the computed package from the project's group Id. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1082) Implementation of JavaEnum#addEnumConstant() does not properly add the generated element

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1082?page=com.atlassian.jira.plugin... ] Work on FORGE-1082 started by Matt Benson. > Implementation of JavaEnum#addEnumConstant() does not properly add the generated element > ---------------------------------------------------------------------------------------- > > Key: FORGE-1082 > URL: https://issues.jboss.org/browse/FORGE-1082 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha9 > Reporter: Matt Benson > Assignee: Matt Benson > > Instead the new constant is improperly dropped into the end of the file. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1082) Implementation of JavaEnum#addEnumConstant() does not properly add the generated element

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1082?page=com.atlassian.jira.plugin... ] Matt Benson resolved FORGE-1082. -------------------------------- Fix Version/s: 2.0.0.Alpha10 Resolution: Done Fixed on {{master}} branch with commits {{7ec717c5b6bebf7b586446c79e7455175752bfa9}}/{{4e581a5171e5329c79da116541f7e82599a74d39}} > Implementation of JavaEnum#addEnumConstant() does not properly add the generated element > ---------------------------------------------------------------------------------------- > > Key: FORGE-1082 > URL: https://issues.jboss.org/browse/FORGE-1082 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha9 > Reporter: Matt Benson > Assignee: Matt Benson > Fix For: 2.0.0.Alpha10 > > > Instead the new constant is improperly dropped into the end of the file. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1082) Implementation of JavaEnum#addEnumConstant() does not properly add the generated element

by Matt Benson (JIRA)

Matt Benson created FORGE-1082: ---------------------------------- Summary: Implementation of JavaEnum#addEnumConstant() does not properly add the generated element Key: FORGE-1082 URL: https://issues.jboss.org/browse/FORGE-1082 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 2.0.0.Alpha9 Reporter: Matt Benson Instead the new constant is improperly dropped into the end of the file. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013