May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1805) Addon add dependency command should show list of addons currently installed for tab completion

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1805: ----------------------------------------- Summary: Addon add dependency command should show list of addons currently installed for tab completion Key: FORGE-1805 URL: https://issues.jboss.org/browse/FORGE-1805 Project: Forge Issue Type: Feature Request Components: Addon Development Affects Versions: 2.5.0.Final Environment: CLI Reporter: Lincoln Baxter III See $title -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-14) JavaClassSource should provide hasSuperClass()

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created ROASTER-14: ----------------------------------------- Summary: JavaClassSource should provide hasSuperClass() Key: ROASTER-14 URL: https://issues.jboss.org/browse/ROASTER-14 Project: Roaster Issue Type: Feature Request Components: API Affects Versions: 2.4.0.Final Reporter: Lincoln Baxter III {code} source.hasSuperClass(Class<?> type) source.hasSuperClass(JavaClass<?> type) source.hasSuperClass(String type) {code} This should probably attempt to use an ImportResolver API (to be added) to recurse up the chain of superclass types. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1804) Generated code is not properly indented

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1804?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1804: ---------------------------------------- I can't seem to reproduce this. > Generated code is not properly indented > --------------------------------------- > > Key: FORGE-1804 > URL: https://issues.jboss.org/browse/FORGE-1804 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > *The affected version is 2.5.1-SNAPSHOT*. I noticed a regression in 2.5.1-SNAPSHOT. > I create an Entity and an EJB : > {code} > [temp]$ project-new --named proj251 > [proj251]$ jpa-new-entity --named MyEntity > [MyEntity.java]$ ejb-new-bean --named MyService > {code} > If I run this script in 2.5.0 the generated code is well indented. Here for the entity : > {code} > import java.lang.Override; > @Entity > public class MyEntity implements Serializable > {code} > And for the EJB : > {code} > import java.io.Serializable; > @Stateless > @LocalBean > public class MyService implements Serializable > {code} > But when I do that with 2.5.1-SNAPSHOT, the class annotation is not right : > {code} > import java.lang.Override;@Entity > public class MyEntity implements Serializable { > {code} > And > {code} > import java.io.Serializable;@Stateless > @LocalBean > public class MyService implements Serializable { > {code} > I haven't tried with all the other artifacts, I'm wondering if it's on all the generated code or not -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1803) Created EJB goes into the view package

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1803?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1803: ------------------------------------------ Cool, it's working ! > Created EJB goes into the view package > -------------------------------------- > > Key: FORGE-1803 > URL: https://issues.jboss.org/browse/FORGE-1803 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > If I create a new project from scratch and add an EJB, the EJB is created under the {{service}} package. But if I am on an already created project and do the same, the EJB is created under the {{view}} package. > The example below show how I create a new EJB under the newly created {{test}} project which ends up in {{service}} package. And then, I {{cd}} an already created project ({{cdbookstore}}) and the EJB is created under {{view}} : > {code} > [temp]$ project-new --named test > ***SUCCESS*** Project named 'test' has been created. > [test]$ ejb-new-bean --named MyService > ***SUCCESS*** EJB has been installed. > ***SUCCESS*** EJB org.test.service.MyService created. > [MyService.java]$ cd ~~ > [test]$ cd ../cdbookstore/ > [cdbookstore]$ ejb-new-bean --named MyService > ***SUCCESS*** EJB org.agoncal.training.javaee6adv.view.MyService created. > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1804) Generated code is not properly indented

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1804: ---------------------------------------- Summary: Generated code is not properly indented Key: FORGE-1804 URL: https://issues.jboss.org/browse/FORGE-1804 Project: Forge Issue Type: Enhancement Components: Java EE Affects Versions: 2.5.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future *The affected version is 2.5.1-SNAPSHOT*. I noticed a regression in 2.5.1-SNAPSHOT. I create an Entity and an EJB : {code} [temp]$ project-new --named proj251 [proj251]$ jpa-new-entity --named MyEntity [MyEntity.java]$ ejb-new-bean --named MyService {code} If I run this script in 2.5.0 the generated code is well indented. Here for the entity : {code} import java.lang.Override; @Entity public class MyEntity implements Serializable {code} And for the EJB : {code} import java.io.Serializable; @Stateless @LocalBean public class MyService implements Serializable {code} But when I do that with 2.5.1-SNAPSHOT, the class annotation is not right : {code} import java.lang.Override;@Entity public class MyEntity implements Serializable { {code} And {code} import java.io.Serializable;@Stateless @LocalBean public class MyService implements Serializable { {code} I haven't tried with all the other artifacts, I'm wondering if it's on all the generated code or not -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1803) Created EJB goes into the view package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1803?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1803. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done EJBs are now created under .service package by default > Created EJB goes into the view package > -------------------------------------- > > Key: FORGE-1803 > URL: https://issues.jboss.org/browse/FORGE-1803 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.5.1.Final > > > If I create a new project from scratch and add an EJB, the EJB is created under the {{service}} package. But if I am on an already created project and do the same, the EJB is created under the {{view}} package. > The example below show how I create a new EJB under the newly created {{test}} project which ends up in {{service}} package. And then, I {{cd}} an already created project ({{cdbookstore}}) and the EJB is created under {{view}} : > {code} > [temp]$ project-new --named test > ***SUCCESS*** Project named 'test' has been created. > [test]$ ejb-new-bean --named MyService > ***SUCCESS*** EJB has been installed. > ***SUCCESS*** EJB org.test.service.MyService created. > [MyService.java]$ cd ~~ > [test]$ cd ../cdbookstore/ > [cdbookstore]$ ejb-new-bean --named MyService > ***SUCCESS*** EJB org.agoncal.training.javaee6adv.view.MyService created. > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1803) Created EJB goes into the view package

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1803: ---------------------------------------- Summary: Created EJB goes into the view package Key: FORGE-1803 URL: https://issues.jboss.org/browse/FORGE-1803 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.5.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future If I create a new project from scratch and add an EJB, the EJB is created under the {{service}} package. But if I am on an already created project and do the same, the EJB is created under the {{view}} package. The example below show how I create a new EJB under the newly created {{test}} project which ends up in {{service}} package. And then, I {{cd}} an already created project ({{cdbookstore}}) and the EJB is created under {{view}} : {code} [temp]$ project-new --named test ***SUCCESS*** Project named 'test' has been created. [test]$ ejb-new-bean --named MyService ***SUCCESS*** EJB has been installed. ***SUCCESS*** EJB org.test.service.MyService created. [MyService.java]$ cd ~~ [test]$ cd ../cdbookstore/ [cdbookstore]$ ejb-new-bean --named MyService ***SUCCESS*** EJB org.agoncal.training.javaee6adv.view.MyService created. {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1764) Forge Eclipse does not seem to be properly syncing with the workspace selection

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1764?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1764. ---------------------------------- Fix Version/s: 2.5.1.Final (was: 2.x Future) Resolution: Done Fixed in https://github.com/jbosstools/jbosstools-forge/commit/3a7700ce16811d807b8... > Forge Eclipse does not seem to be properly syncing with the workspace selection > ------------------------------------------------------------------------------- > > Key: FORGE-1764 > URL: https://issues.jboss.org/browse/FORGE-1764 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.4.1.Final > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.5.1.Final > > > When generating new classes, and setting them as the UISelection, Eclipse does not appear to be A. refreshing the project to show the changes in the project, and B. selecting the appropriate resource. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 2 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 edited comment on FORGE-1787 at 5/9/14 8:11 AM: ------------------------------------------------------------------ Agrh.... there is also a bug in {{pageTemplate.xhtml}}. The link to the home page should not have {{admin}}. So instead of : {code} <h:link id="brandLink" outcome="/admin/index.xhtml" styleClass="brand">Cdbookstore</h:link> ... <h:link id="homeLink" outcome="/admin/index.xhtml"> <img src='#{resource["forge-logo.png"]}' alt="Forge... get hammered" border="0" /> </h:link> {code} It should be (because there {{index.xhtml}} is at the root of the webapp) : {code} <h:link id="brandLink" outcome="/index.xhtml" styleClass="brand">Cdbookstore</h:link> ... <h:link id="homeLink" outcome="/index.xhtml"> <img src='#{resource["forge-logo.png"]}' alt="Forge... get hammered" border="0" /> </h:link> {code} was (Author: agoncal): Agrh.... there is also a bug in {{pageTemplate.xhtml}}. The link to the home page should not have {{admin}}. So instead of : {code} <h:link id="brandLink" outcome="/admin/index.xhtml" styleClass="brand">Cdbookstore</h:link> {code} It should be (because there {{index.xhtml}} is at the root of the webapp) : {code} <h:link id="brandLink" outcome="/index.xhtml" styleClass="brand">Cdbookstore</h:link> {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 > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.5.1.Final > > > 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, 2 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 commented on FORGE-1787: ------------------------------------------ Agrh.... there is also a bug in {{pageTemplate.xhtml}}. The link to the home page should not have {{admin}}. So instead of : {code} <h:link id="brandLink" outcome="/admin/index.xhtml" styleClass="brand">Cdbookstore</h:link> {code} It should be (because there {{index.xhtml}} is at the root of the webapp) : {code} <h:link id="brandLink" outcome="/index.xhtml" styleClass="brand">Cdbookstore</h:link> {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 > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.5.1.Final > > > 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014