January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1480) Mulitple --value parameters for Min constraint

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1480?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1480. ------------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done Fixed in Aesh 0.48 > Mulitple --value parameters for Min constraint > ---------------------------------------------- > > Key: FORGE-1480 > URL: https://issues.jboss.org/browse/FORGE-1480 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > When you create a {{Min}} constraint (it's ok for {{Max}}), you can add as many {{--value}} attributes you want. You should only have *one* {{--value}} : > {code} > [Item.java]$ constraint-add --onProperty description --constraint Min -- > --message --onAccessor --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value -- > --message --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value -- > --message --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- > --message --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1480) Mulitple --value parameters for Min constraint

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1480?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1480: ----------------------------------------- Assignee: Lincoln Baxter III > Mulitple --value parameters for Min constraint > ---------------------------------------------- > > Key: FORGE-1480 > URL: https://issues.jboss.org/browse/FORGE-1480 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > When you create a {{Min}} constraint (it's ok for {{Max}}), you can add as many {{--value}} attributes you want. You should only have *one* {{--value}} : > {code} > [Item.java]$ constraint-add --onProperty description --constraint Min -- > --message --onAccessor --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value -- > --message --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value -- > --message --value --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- > --message --payload --groups > [Item.java]$ constraint-add --onProperty description --constraint Min --value 12 --value 13 -- > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1489) Remove addon removes incorrect addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1489?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1489: -------------------------------------- Assignee: George Gastaldi > Remove addon removes incorrect addon > ------------------------------------ > > Key: FORGE-1489 > URL: https://issues.jboss.org/browse/FORGE-1489 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 2.0.0.CR1 > Reporter: Tom Cunningham > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > Attachments: Graphic1.jpg, Graphic2.jpg > > > I've been installing two addons off and on and noticed that when I choose "Remove Addon" in the forge menu, one of my addons is selected for removal by default (see Graphic1). I unselect it, select my other addon (see Graphic2), but the first addon that was selected by default is removed and the addon that I selected is kept. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1437) project-new --type jar-resources is confusing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1437?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1437: ----------------------------------------- Assignee: Lincoln Baxter III > project-new --type jar-resources is confusing > --------------------------------------------- > > Key: FORGE-1437 > URL: https://issues.jboss.org/browse/FORGE-1437 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > I was used to {{jar}} so {{jar-resources}} is confusing. Is it a different thing ? > {code} > [Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type > jar war addon jar-resources > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1437) project-new --type jar-resources is confusing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1437?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1437. ------------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > project-new --type jar-resources is confusing > --------------------------------------------- > > Key: FORGE-1437 > URL: https://issues.jboss.org/browse/FORGE-1437 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > I was used to {{jar}} so {{jar-resources}} is confusing. Is it a different thing ? > {code} > [Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type > jar war addon jar-resources > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1453) Cannot scaffold JSF pages using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1453?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1453: ------------------------------------- Parent Issue: FORGE-1491 (was: FORGE-1505) > Cannot scaffold JSF pages using a * target > ------------------------------------------ > > Key: FORGE-1453 > URL: https://issues.jboss.org/browse/FORGE-1453 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When I want to generate JSF pages for each of my entities, I can write the following in Forge 1.x : > {code} > scaffold from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [TalkEndpoint.java]$ scaffold-generate --targets ~.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.* > Targets must be specified. > [TalkEndpoint.java]$ scaffold-generate --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Scaffold was generated successfully. > [TalkEndpoint.java]$ > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1450) Cannot create an enum attribute on an Entity

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1450?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1450: ------------------------------------- Parent Issue: FORGE-1491 (was: FORGE-1505) > Cannot create an enum attribute on an Entity > -------------------------------------------- > > Key: FORGE-1450 > URL: https://issues.jboss.org/browse/FORGE-1450 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > I've created a {{Language}} enum (with {{java-new-enum}}) and then I want my entity {{Book}} to have an attribute of type {{Language}}. In Forge 1.x I would do : > {code} > field custom --named language --type org.javaone.javaee7.model.Language.java ; > {code} > There is no such {{custom}} attribute in Forge 2.x and the following doesn't work : > {code} > jpa-new-field --named language --typeName org.javaone.javaee7.model.Language.java ; > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1451) Cannot scaffold REST endpoints using a * target

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1451?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1451: ------------------------------------- Parent Issue: FORGE-1491 (was: FORGE-1505) > Cannot scaffold REST endpoints using a * target > ----------------------------------------------- > > Key: FORGE-1451 > URL: https://issues.jboss.org/browse/FORGE-1451 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Priority: Critical > Fix For: 2.x Future > > > When I want to generate REST enpoints for each of my entities, I can write the following in Forge 1.x : > {code} > rest endpoint-from-entity ~.model.* ; > {code} > In Forge 2.CR1 I cannot use the '*' and need to specify each entity : > {code} > [Book.java]$ rest-endpoint-from-entity --targets ~.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.* > Targets must be specified. > [Book.java]$ rest-endpoint-from-entity --targets org.javaone.javaee7.model.Book org.javaone.javaee7.model.Speaker org.javaone.javaee7.model.Talk > ***SUCCESS*** Endpoint created > ***SUCCESS*** EJB has been installed. > {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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1524) Change the JSF preRenderView to fit the new viewAction

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1524?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1524: ------------------------------------- Parent Issue: FORGE-1491 (was: FORGE-1505) > Change the JSF preRenderView to fit the new viewAction > ------------------------------------------------------ > > Key: FORGE-1524 > URL: https://issues.jboss.org/browse/FORGE-1524 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When a JSF page is generated, it uses the old JSF 2.0 {{preRenderView}} : > {code} > <f:event type="preRenderView" listener='#{authorBean.retrieve}'/> > {code} > Instead, it should be using the new Java EE 7 {{viewAction}} : > {code} > <f:viewAction action="#{authorBean.retrieve}"/> > {code} > I've replaced all occurrences in every pages and it works fine. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1523) Change the JSF namespaces to fit new Java EE 7 standard

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1523?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1523: ------------------------------------- Parent Issue: FORGE-1491 (was: FORGE-1505) > Change the JSF namespaces to fit new Java EE 7 standard > ------------------------------------------------------- > > Key: FORGE-1523 > URL: https://issues.jboss.org/browse/FORGE-1523 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > When a JSF page is generated, the namespaces look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:c="http://java.sun.com/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {code} > They use the old {{java.sun.com}} namespace instead of the new {{xmlns.jcp.org}}. They should look like this : > {code} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > template="/resources/scaffold/pageTemplate.xhtml"> > {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

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014