October 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1260) Upgrade to Maven 3.1.1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1260?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1260. ---------------------------------- Resolution: Done > Upgrade to Maven 3.1.1 > ---------------------- > > Key: FORGE-1260 > URL: https://issues.jboss.org/browse/FORGE-1260 > Project: Forge > Issue Type: Component Upgrade > Components: Addon Manager, Build Tools - Maven, Maven Plugin > Affects Versions: 2.0.0.Alpha13 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha14 > > > Upgrade to Maven 3.1.1 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1260) Upgrade to Maven 3.1.1

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1260: -------------------------------------- Summary: Upgrade to Maven 3.1.1 Key: FORGE-1260 URL: https://issues.jboss.org/browse/FORGE-1260 Project: Forge Issue Type: Component Upgrade Components: Addon Manager, Build Tools - Maven, Maven Plugin Affects Versions: 2.0.0.Alpha13 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha14 Upgrade to Maven 3.1.1 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1259) Forge should allow output from UICommands

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1259: -------------------------------------- Summary: Forge should allow output from UICommands Key: FORGE-1259 URL: https://issues.jboss.org/browse/FORGE-1259 Project: Forge Issue Type: Feature Request Components: UI - API Affects Versions: 2.0.0.Alpha13 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha14 UIOutput should be introduced with hooks for the out and err stream of the current UIProvider -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1155) Migrate the shell implementation to the newest Aesh API (0.41+)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1155?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1155. ---------------------------------- Fix Version/s: 2.0.0.Alpha14 (was: 2.x Future) Resolution: Done Migrated to 0.42-SNAPSHOT > Migrate the shell implementation to the newest Aesh API (0.41+) > --------------------------------------------------------------- > > Key: FORGE-1155 > URL: https://issues.jboss.org/browse/FORGE-1155 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha14 > > > The shell addon should be implemented on top of the newest Aesh API. Check AeshExample for a sample of how it should be handled. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1257) Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1257?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1257. ------------------------------------- Resolution: Won't Fix No performance gains, so no point to use this approach. > Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete > ----------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1257 > URL: https://issues.jboss.org/browse/FORGE-1257 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container), Test Harness > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > This could occur in ForgeDeployableContainer, and ForgeTestMethodExecutor, as an alternate DeploymentStrategy (need to introduce a design pattern to simplify the code, and introduce parallel behavior for this type of bulk deployment). > This is an alternate solution to FORGE-1208. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1258) CLONE - Support mid-line completion of shell buffer (editing previously entered command)

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1258: -------------------------------------- Summary: CLONE - Support mid-line completion of shell buffer (editing previously entered command) Key: FORGE-1258 URL: https://issues.jboss.org/browse/FORGE-1258 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Alpha11 Reporter: Lincoln Baxter III Fix For: 2.x Future It is currently not possible for users to edit parts of a command-line that they have typed, without deleting all characters following the piece they wish to complete. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1201) getSearchPredicates should use case insensitive search

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1201?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1201: ----------------------------------- Fix Version/s: 2.x Future > getSearchPredicates should use case insensitive search > ------------------------------------------------------ > > Key: FORGE-1201 > URL: https://issues.jboss.org/browse/FORGE-1201 > Project: Forge > Issue Type: Feature Request > Affects Versions: 1.4.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Hi, > When you do JSF scaffolding, the generated code for research is as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(root.<String>get("title"), '%' + title + '%')); > } > {code} > The problem with that is the search is case sensitive and searching for "java" or "Java" doesn't bring the same results. It would be more natural to have case insensitive search as follow : > {code} > private Predicate[] getSearchPredicates(Root<Talk> root) { > CriteriaBuilder builder = this.entityManager.getCriteriaBuilder(); > List<Predicate> predicatesList = new ArrayList<>(); > String title = this.example.getTitle(); > if (title != null && !"".equals(title)) { > predicatesList.add(builder.like(builder.lower(root.<String>get("title")), "%" + title.toLowerCase() + "%")); > } > {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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-838) RestPlugin should support the right semantics for entities with non auto-generated Ids

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-838?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-838: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > RestPlugin should support the right semantics for entities with non auto-generated Ids > -------------------------------------------------------------------------------------- > > Key: FORGE-838 > URL: https://issues.jboss.org/browse/FORGE-838 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Currently, the generated REST resources contain a {{@POST}} method for creating new entities and a {{@PUT}} method for updating an existing entity. > This set of semantics is appropriate for auto-generated Ids where the Ids would be created by the server, and cannot be specified by the client. > However, for JPA entities that do not contain a {{@GeneratedValue}} annotation, these semantics may not be unsuitable. It would be preferable to use only a {{@PUT}} method that is used to create and update the entities. This is primarily because the client gets to decide the resource/entity identifier, and hence, also the location of the resource. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1257) Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1257?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1257: ------------------------------------------- These issues are not exactly a 1:1 replacement. There are reasons for both approaches, and each will cause different test behavior. > Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete > ----------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1257 > URL: https://issues.jboss.org/browse/FORGE-1257 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container), Test Harness > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > This could occur in ForgeDeployableContainer, and ForgeTestMethodExecutor, as an alternate DeploymentStrategy (need to introduce a design pattern to simplify the code, and introduce parallel behavior for this type of bulk deployment). > This is an alternate solution to FORGE-1208. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1257) Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1257: ----------------------------------------- Summary: Furnace Test Harness should be able to perform all deployments, then enable addons after deployments are complete Key: FORGE-1257 URL: https://issues.jboss.org/browse/FORGE-1257 Project: Forge Issue Type: Feature Request Components: Furnace (Container), Test Harness Affects Versions: 2.0.0.Alpha13 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 2.x Future This could occur in ForgeDeployableContainer, and ForgeTestMethodExecutor, as an alternate DeploymentStrategy (need to introduce a design pattern to simplify the code, and introduce parallel behavior for this type of bulk deployment). This is an alternate solution to FORGE-1208. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2013