May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1786) Generated index.html is broken in 2.5.1-SNAPSHOT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1786?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1786. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done Fixed. We still need to add tests to the generated scaffold stuff > Generated index.html is broken in 2.5.1-SNAPSHOT > ------------------------------------------------ > > Key: FORGE-1786 > URL: https://issues.jboss.org/browse/FORGE-1786 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 2.5.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.5.1.Final > > > I'm scaffolding a simple JSF application with the latest 2.5.1-SNAPSHOT and I realized that the generated {{index.html}} is broken. Until 2.5.0-FINAL the page looks like this : > {code} > <meta http-equiv="refresh" content="0;url=./faces/index.xhtml" /> > {code} > And in 2.5.1-SNAPSHOT the {{index.html}} has exactly the same content than the {{index.xhtml}} : > {code} > <?xml version='1.0' encoding='UTF-8' ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > template="/resources/scaffold/pageTemplate.xhtml"> > <ui:param name="pageTitle" value="Welcome to Forge" /> > <ui:define name="header"> > Welcome to Forge > </ui:define> > <ui:define name="main"> > <h2 class="success"> > Your application is running. > </h2> > <p> > <a target="_blank" > href="http://forge.jboss.org/docs/index.html">Documentation</a> > | <a target="_blank" > href="http://twitter.com/intent/tweet?text=I+just+built+and+deployed+a+webapp+u...">Get > Excited!</a><br /> <a target="_blank" href="http://jboss.org/forge"><br /> > Forge Project</a> | <a target="_blank" > href="https://community.jboss.org/en/forge">User > Forums</a> | <a target="_blank" > href="https://issues.jboss.org/browse/FORGE">Report an issue</a> > </p> > </ui:define> > </ui:composition> > {code} > Something is broken (and a test is missing ;o) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1788) DOT generation should be part of the release process

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1788?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1788: ----------------------------------- Priority: Trivial (was: Major) > DOT generation should be part of the release process > ----------------------------------------------------- > > Key: FORGE-1788 > URL: https://issues.jboss.org/browse/FORGE-1788 > Project: Forge > Issue Type: Enhancement > Components: Maven > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Priority: Trivial > Fix For: 2.x Future > > > The furnace-maven-plugin DOT generation is not used at all during an addon development. We should move it to a release profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1788) DOT generation should be part of the release process

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1788: -------------------------------------- Summary: DOT generation should be part of the release process Key: FORGE-1788 URL: https://issues.jboss.org/browse/FORGE-1788 Project: Forge Issue Type: Enhancement Components: Maven Affects Versions: 2.5.0.Final Reporter: George Gastaldi Fix For: 2.x Future The furnace-maven-plugin DOT generation is not used at all during an addon development. We should move it to a release profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ] Daniel Cunha updated FORGE-1780: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/451 > "Addon: New UI Command" should default commandName based on type name camelcase > ------------------------------------------------------------------------------- > > Key: FORGE-1780 > URL: https://issues.jboss.org/browse/FORGE-1780 > Project: Forge > Issue Type: Enhancement > Components: Addon Development, Builtin Plugins > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Daniel Cunha > Labels: starter > Fix For: 2.x Future > > > addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx > This should be the default commandName value for this scenario: > addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ] Daniel Cunha commented on FORGE-1780: ------------------------------------- Sorry, the NewUICommandWizard doesn't use Strings of the roaster. But, I created the UIString into util package of the ui-api module. > "Addon: New UI Command" should default commandName based on type name camelcase > ------------------------------------------------------------------------------- > > Key: FORGE-1780 > URL: https://issues.jboss.org/browse/FORGE-1780 > Project: Forge > Issue Type: Enhancement > Components: Addon Development, Builtin Plugins > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Daniel Cunha > Labels: starter > Fix For: 2.x Future > > > addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx > This should be the default commandName value for this scenario: > addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ] Daniel Cunha commented on FORGE-1780: ------------------------------------- I saw that NewUICommandWizard class use the Strings of the roaster. I created the method there. :-) > "Addon: New UI Command" should default commandName based on type name camelcase > ------------------------------------------------------------------------------- > > Key: FORGE-1780 > URL: https://issues.jboss.org/browse/FORGE-1780 > Project: Forge > Issue Type: Enhancement > Components: Addon Development, Builtin Plugins > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Daniel Cunha > Labels: starter > Fix For: 2.x Future > > > addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx > This should be the default commandName value for this scenario: > addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ] Daniel Cunha reassigned FORGE-1780: ----------------------------------- Assignee: Daniel Cunha > "Addon: New UI Command" should default commandName based on type name camelcase > ------------------------------------------------------------------------------- > > Key: FORGE-1780 > URL: https://issues.jboss.org/browse/FORGE-1780 > Project: Forge > Issue Type: Enhancement > Components: Addon Development, Builtin Plugins > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Assignee: Daniel Cunha > Labels: starter > Fix For: 2.x Future > > > addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx > This should be the default commandName value for this scenario: > addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1780) "Addon: New UI Command" should default commandName based on type name camelcase

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1780?page=com.atlassian.jira.plugin... ] Daniel Cunha commented on FORGE-1780: ------------------------------------- Hi, I did this issue, but I have a problem. I created a method to do this task, but I don't know where put my code, into Strings class of the roaster or furnace. What the better place? > "Addon: New UI Command" should default commandName based on type name camelcase > ------------------------------------------------------------------------------- > > Key: FORGE-1780 > URL: https://issues.jboss.org/browse/FORGE-1780 > Project: Forge > Issue Type: Enhancement > Components: Addon Development, Builtin Plugins > Affects Versions: 2.5.0.Final > Reporter: Lincoln Baxter III > Labels: starter > Fix For: 2.x Future > > > addon-new-ui-command --named TechNewPropertyCommand --commandName xxxxxxx > This should be the default commandName value for this scenario: > addon-new-ui-command --named TechNewPropertyCommand --commandName tech-new-property -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1787: ------------------------------------- Description: When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected : {code} scaffold-setup ; scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ; {code} The template navigation looks like : {code} <ul> <li> <h:link outcome="/CD/search" value="CD"/> </li> <li> <h:link outcome="/author/search" value="Author"/> </li> </ul> {code} But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing : {code} scaffold-setup ; scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ; {code} The template : {code} <ul> <li> <h:link outcome="admin/CD/search" value="CD"/> </li> <li> <h:link outcome="admin/author/search" value="Author"/> </li> </ul> {code} The correct navigation would be : {code} <ul> <li> <h:link outcome="/admin/CD/search" value="CD"/> </li> <li> <h:link outcome="/admin/author/search" value="Author"/> </li> </ul> {code} The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive : {code} scaffold-setup ; scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ; {code} But this trick doesn't work for the {{search.xhtml}} page. The generated code is : {code} <h:link outcome="/genre/view"> <f:param name="id" value="#{_item.id}"/> <h:outputText id="itemName" value="#{_item.name}"/> </h:link> {code} The {{outcome}} is not right, and should contain a {{/admin}} {code} <h:link outcome="/admin/genre/view"> <f:param name="id" value="#{_item.id}"/> <h:outputText id="itemName" value="#{_item.name}"/> </h:link> {code} was: When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected : {code} scaffold-setup ; scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ; {code} The template navigation looks like : {code} <ul> <li> <h:link outcome="/CD/search" value="CD"/> </li> <li> <h:link outcome="/author/search" value="Author"/> </li> </ul> {code} But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing : {code} scaffold-setup ; scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ; {code} The template : {code} <ul> <li> <h:link outcome="admin/CD/search" value="CD"/> </li> <li> <h:link outcome="admin/author/search" value="Author"/> </li> </ul> {code} The correct navigation would be : {code} <ul> <li> <h:link outcome="/admin/CD/search" value="CD"/> </li> <li> <h:link outcome="/admin/author/search" value="Author"/> </li> </ul> {code} The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive : {code} scaffold-setup ; scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ; scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ; {code} > When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right > -------------------------------------------------------------------------------------------- > > Key: FORGE-1787 > URL: https://issues.jboss.org/browse/FORGE-1787 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Priority: Blocker > > When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected : > {code} > scaffold-setup ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template navigation looks like : > {code} > <ul> > <li> > <h:link outcome="/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/author/search" value="Author"/> > </li> > </ul> > {code} > But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing : > {code} > scaffold-setup ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template : > {code} > <ul> > <li> > <h:link outcome="admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="admin/author/search" value="Author"/> > </li> > </ul> > {code} > The correct navigation would be : > {code} > <ul> > <li> > <h:link outcome="/admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/admin/author/search" value="Author"/> > </li> > </ul> > {code} > The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive : > {code} > scaffold-setup ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > But this trick doesn't work for the {{search.xhtml}} page. The generated code is : > {code} > <h:link outcome="/genre/view"> > <f:param name="id" value="#{_item.id}"/> > <h:outputText id="itemName" value="#{_item.name}"/> > </h:link> > {code} > The {{outcome}} is not right, and should contain a {{/admin}} > {code} > <h:link outcome="/admin/genre/view"> > <f:param name="id" value="#{_item.id}"/> > <h:outputText id="itemName" value="#{_item.name}"/> > </h:link> > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1787) When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1787?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1787: ------------------------------------- Summary: When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right (was: When scaffolding with --webRoot parameter, pageTemplate.xhtml is not right) > When scaffolding with --webRoot parameter, pageTemplate.xhtml and search.xhtml are not right > -------------------------------------------------------------------------------------------- > > Key: FORGE-1787 > URL: https://issues.jboss.org/browse/FORGE-1787 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Priority: Blocker > > When scaffolding a JSF application, without using a {{--webRoot}} parameter, the navigation in the {{pageTemplate.xhtml}} works as expected : > {code} > scaffold-setup ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template navigation looks like : > {code} > <ul> > <li> > <h:link outcome="/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/author/search" value="Author"/> > </li> > </ul> > {code} > But if I specify the {{--webRoot}} parameter, then the navigation does not work as there is a {{/}} missing : > {code} > scaffold-setup ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} > The template : > {code} > <ul> > <li> > <h:link outcome="admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="admin/author/search" value="Author"/> > </li> > </ul> > {code} > The correct navigation would be : > {code} > <ul> > <li> > <h:link outcome="/admin/CD/search" value="CD"/> > </li> > <li> > <h:link outcome="/admin/author/search" value="Author"/> > </li> > </ul> > {code} > The only way to make it work is to add a {{/}} to the {{webroot}}, which is not very intuitive : > {code} > scaffold-setup ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.Author ; > scaffold-generate --webRoot /admin --targets org.agoncal.training.javaee6adv.model.CD ; > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014