[JBoss JIRA] (FORGE-1802) Console hangs when running an invalid script
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1802?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1802:
----------------------------------------
The ClassCastException seen in the logs were fixed. We still need to fix the script execution issue
> Console hangs when running an invalid script
> --------------------------------------------
>
> Key: FORGE-1802
> URL: https://issues.jboss.org/browse/FORGE-1802
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Priority: Critical
> Fix For: 2.x Future
>
>
> I am executing a script (with the {{run}} command) and the console hanged and stopped working completely (I had to kill the process). I realized that there is an error in the script (missing {{;}} at the end of line {{--named ISBN}}).
> Take the following script, and save it on a {{hangs.fsh}} file
> {code}
> # ##################### #
> # Creates a new project #
> # ##################### #
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> # Setup the persistence unit in persistence.xml
> # ############
> jpa-setup --persistenceUnitName cdbookstorePU ;
> # ######################## #
> # Creates the domain model #
> # ######################## #
> # ISBN constraint
> # ############
> constraint-new-annotation --named ISBN
> # Genre entity
> # ############
> jpa-new-entity --named Genre ;
> jpa-new-field --named name --length 100 ;
> {code}
> Now, execute the script, and see the error message :
> {code}
> [temp]$ run hangs.fsh
> project-new --named cdbookstore --topLevelPackage org.agoncal.training.javaee6adv --type war --finalName cdbookstore ;
> ***SUCCESS*** Project named 'cdbookstore' has been created.
> [cdbookstore]$ jpa-setup --persistenceUnitName cdbookstorePU ;
> ***SUCCESS*** Persistence (JPA) is installed.
> [cdbookstore]$ constraint-new-annotation --named ISBN
> ***SUCCESS*** Bean Validation Constraint Annotations org.agoncal.training.javaee6adv.constraints.ISBN was created
> [ISBN.java]$ jpa-new-entity --named Genre ;
> Exception when parsing/running: jpa-new-entity --named Genre , org.jboss.forge.roaster.model.impl.JavaAnnotationImpl cannot be cast to org.jboss.forge.roaster.model.MemberHolder
> [ISBN.java]$
> {code}
> At this point, I can't interact with the console and need to kill the process.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1813) Shall we rename webroot to targetDir or something different ?
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1813:
----------------------------------------
Summary: Shall we rename webroot to targetDir or something different ?
Key: FORGE-1813
URL: https://issues.jboss.org/browse/FORGE-1813
Project: Forge
Issue Type: Task
Components: Brainstorming
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
In [FORGE-1787] the parameter {{webroot}} seems confusing. Maybe we could change it to targetDir like other command, or something different (as it refer to a subdirectory of web app.
Read on #IRC
{code}
agoncal And what about targetPackage ? What I really want is a --webroot (like the scaffold command) no ?
lincolnthree agoncal: targetDir ?
agoncal lincolnthree Hum... it's called --webroot on other places (which is the relative webapp/ directory)
lincolnthree agoncal: but it's not the webroot dir in this case
lincolnthree agoncal: it's the target directory where the file will be generated
gastaldi +1 to targetDir
lincolnthree agoncal: doesn't have to be in the web root, but could default there
lincolnthree or even just target
agoncal lincolnthree But by default it's under /webapp if you don't specify it. If you do (eg. --webroot admin) then the file is generated under /webapp/admin
agoncal I'm refering to webroot because it looks the same as FORGE-1787
lincolnthree agoncal: totally different
agoncal lincolnthree ok
lincolnthree agoncal: well.. maybe not totally :p
lincolnthree agoncal: webroot is a bad name for that
agoncal lincolnthree I'll go for for targetDir
agoncal lincolnthree Do you want me to create a JIRA about renaming webroot to targetDir ?
lincolnthree agoncal: why not skip targetDir entirely and just go for —output
lincolnthree agoncal: yeah we may want to address this
lincolnthree output would be target dir and filename together
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1812) Rename command faces-project-stage to faces-set-project-stage
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1812?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1812.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
> Rename command faces-project-stage to faces-set-project-stage
> -------------------------------------------------------------
>
> Key: FORGE-1812
> URL: https://issues.jboss.org/browse/FORGE-1812
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Shell
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.5.1.Final
>
>
> To follow the Forge 2.x naming convention, the command {{faces-project-stage}} should be renamed {{faces-set-project-stage}} like
> {code}
> ejb-set-class-transaction-attribute
> ejb-set-method-transaction-attribute
> project-set-compiler-version
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1487) Columns do not line up on certain CLI outputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1487?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1487:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.5.1.Final
(was: 2.x Future)
Resolution: Done
Fixed
> Columns do not line up on certain CLI outputs
> ---------------------------------------------
>
> Key: FORGE-1487
> URL: https://issues.jboss.org/browse/FORGE-1487
> Project: Forge
> Issue Type: Enhancement
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Lincoln Baxter III
> Assignee: Robert Balent
> Priority: Minor
> Fix For: 2.5.1.Final
>
>
> {code}
> [core]$ ls
> CONTRIBUTING.md configuration dist maven scaffold
> LICENSE convert eclipse-code-formatter-profile.xml parser-java shell
> README.asciidoc core environment parser-xml templates
> addon-manager database-tools facets pom.xml text
> addons dependencies forge-install.bsh projects ui
> bootstrap dev-tools-java javaee resources
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1594) Being able to create an empty JSF page
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1594?page=com.atlassian.jira.plugin... ]
Antonio Goncalves reassigned FORGE-1594:
----------------------------------------
Assignee: Antonio Goncalves (was: Vineet Reynolds)
> Being able to create an empty JSF page
> --------------------------------------
>
> Key: FORGE-1594
> URL: https://issues.jboss.org/browse/FORGE-1594
> Project: Forge
> Issue Type: Sub-task
> Components: Scaffold
> Affects Versions: 2.0.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Minor
> Fix For: 2.x Future
>
>
> At the moment the only way to generate JSF pages is with scaffolding. When you create an application, you realize that these scaffolded pages are not enough and that you need to create new ones. To save time and help the developer in creating new pages, it would be good to have a command such :
> {code}
> faces-new-view --named mypage
> {code}
> This will create a mypage.xhtml on the root of the webapp directory. You could also give a different directory with :
> {code}
> faces-new-view --named mypage --targetDirectory admin
> {code}
> This will create the page under webapp/admin/mypage.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:h="http://xmlns.jcp.org/jsf/html"
> xmlns:f="http://xmlns.jcp.org/jsf/core"
> xmlns:ui="http://xmlns.jcp.org/jsf/facelets"
> template="/resources/scaffold/pageTemplate.xhtml">
> <ui:param name="pageTitle" value="mypage"/>
> <ui:define name="header">
> mypage
> </ui:define>
> <ui:define name="subheader">
> mypage
> </ui:define>
> <ui:define name="footer"/>
> <ui:define name="main">
> </ui:define>
> </ui:composition>
> {code}
> The name of the page {{mypage}} is used for the title, header, subheader. But we could customize this using optional attributes for title, header, subheader :
> {code}
> faces-new-view --named mypage --targetDirectory admin --title Administration Page --header Admin Header --subheader Admin Sub Header
> {code}
> It would just create a minimum JSF page such as :
> {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:h="http://xmlns.jcp.org/jsf/html"
> xmlns:f="http://xmlns.jcp.org/jsf/core"
> xmlns:ui="http://xmlns.jcp.org/jsf/facelets"
> template="/resources/scaffold/pageTemplate.xhtml">
> <ui:param name="pageTitle" value="Administration Page"/>
> <ui:define name="header">
> Admin Header
> </ui:define>
> <ui:define name="subheader">
> Admin Sub Header
> </ui:define>
> <ui:define name="footer"/>
> <ui:define name="main">
> </ui:define>
> </ui:composition>
> {code}
> If there were several templates, we could do :
> {code}
> faces-new-view --named mypage --template MyTemplate.xhtml
> {code}
> PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1812) Rename command faces-project-stage to faces-set-project-stage
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1812:
----------------------------------------
Summary: Rename command faces-project-stage to faces-set-project-stage
Key: FORGE-1812
URL: https://issues.jboss.org/browse/FORGE-1812
Project: Forge
Issue Type: Enhancement
Components: UI - Shell
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
To follow the Forge 2.x naming convention, the command {{faces-project-stage}} should be renamed {{faces-set-project-stage}} like
{code}
ejb-set-class-transaction-attribute
ejb-set-method-transaction-attribute
project-set-compiler-version
{code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1811) Version ranges from Maven Central cannot be obtained when other repositories are activated
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1811:
--------------------------------------
Summary: Version ranges from Maven Central cannot be obtained when other repositories are activated
Key: FORGE-1811
URL: https://issues.jboss.org/browse/FORGE-1811
Project: Forge
Issue Type: Bug
Components: Maven
Affects Versions: 2.5.0.Final
Reporter: Vineet Reynolds
Given a settings.xml file with profiles that activate remote repositories, like [the one used in WFK development|https://github.com/jboss-developer/jboss-wfk-quickstarts/blob...], the VersionRangeRequest failures are encountered:
{noformat}
WARNING: Could not install Facet of type [class org.jboss.forge.addon.facets.AbstractFacet_$$_javassist_f2834ff7-c2f0-4484-bfb6-80e880fec7c2], due to exception:
java.lang.IllegalStateException: Could not resolve version for dependency [org.jboss.spec.javax.faces:jboss-jsf-api_2.0_spec:::].
at org.jboss.forge.addon.projects.impl.DependencyInstallerImpl.install(DependencyInstallerImpl.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
at org.jboss.forge.addon.projects.impl.DependencyInstallerImpl_$$_javassist_a0a4f4eb-2ac1-410f-8895-a84b9c9fc855.install(DependencyInstallerImpl_$$_javassist_a0a4f4eb-2ac1-410f-8895-a84b9c9fc855.java)
at org.jboss.forge.addon.javaee.AbstractJavaEEFacet.install(AbstractJavaEEFacet.java:81)
at org.jboss.forge.addon.javaee.faces.AbstractFacesFacetImpl.install(AbstractFacesFacetImpl.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
at org.jboss.forge.addon.facets.AbstractFacet_$$_javassist_f2834ff7-c2f0-4484-bfb6-80e880fec7c2.install(AbstractFacet_$$_javassist_f2834ff7-c2f0-4484-bfb6-80e880fec7c2.java)
at org.jboss.forge.addon.facets.AbstractFaceted.install(AbstractFaceted.java:76)
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:212)
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:139)
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
at org.jboss.forge.addon.facets.FacetFactoryImpl_$$_javassist_7c622a44-6b3f-479f-a563-63193e506080.install(FacetFactoryImpl_$$_javassist_7c622a44-6b3f-479f-a563-63193e506080.java)
at org.jboss.forge.addon.javaee.faces.ui.FacesSetupWizard.execute(FacesSetupWizard.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
at org.jboss.forge.addon.javaee.faces.ui.FacesSetupWizard_$$_javassist_4d1a8c08-cf39-4c32-8cd7-7204e27638d5.execute(FacesSetupWizard_$$_javassist_4d1a8c08-cf39-4c32-8cd7-7204e27638d5.java)
at org.jboss.forge.addon.ui.result.navigation.CompositeCommand.execute(CompositeCommand.java:82)
at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.execute(WizardCommandControllerImpl.java:153)
at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.execute(NoUIWizardControllerDecorator.java:152)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:103)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:76)
at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_56d4423c-4ab7-48ed-b8fa-9000898f9d2a.execute(CommandController_$$_javassist_56d4423c-4ab7-48ed-b8fa-9000898f9d2a.java)
at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:86)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
{noformat}
In the above case, the artifact is apparently present in M2 central and it's versions should have been fetched, but this is not the case.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1704) Stale subflow pages are displayed and corresponding commands executed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1704?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1704:
-----------------------------------
Priority: Major (was: Blocker)
> Stale subflow pages are displayed and corresponding commands executed
> ---------------------------------------------------------------------
>
> Key: FORGE-1704
> URL: https://issues.jboss.org/browse/FORGE-1704
> Project: Forge
> Issue Type: Bug
> Components: UI - API
> Affects Versions: 2.3.0.Final
> Reporter: Vineet Reynolds
>
> This happens in scaffolding, but it is very likely an implementation issue with respect to subflows in the UI-API.
> Stale subflow pages are displayed and their corresponding commands are executed even though they pages should not be displayed and are not relevant to the subflow sequence.
> In scaffolding (see steps to reproduce), when I choose a scaffold provider, subflow pages from the originally selected provider are displayed in combination with the currently selected provider. Additionally, UICommands or WizardSteps from the original provider are executed, resulted in a weird scaffold being generated.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1800.
----------------------------------
Resolution: Won't Fix
Closing this as Won't Fix
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months
[JBoss JIRA] (FORGE-1800) Install Forge 2.5.0.Final in JBoss Developer Studio - no run
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/FORGE-1800?page=com.atlassian.jira.plugin... ]
Koen Aers commented on FORGE-1800:
----------------------------------
William,
The Forge 2 plugin only works with Eclipse Luna. Make sure you are NOT using Kepler.
When using a Luna instance with the Forge 1.2.1 plugin installed you will need to update the installation with the Forge 1.3 plugin as indicated on the screenshot you attached.
Cheers,
Koen
> Install Forge 2.5.0.Final in JBoss Developer Studio - no run
> ------------------------------------------------------------
>
> Key: FORGE-1800
> URL: https://issues.jboss.org/browse/FORGE-1800
> Project: Forge
> Issue Type: Bug
> Affects Versions: 2.5.0.Final
> Environment: JBoss Developer Studio 7.1.1.GA
> Reporter: William Diaz Pabón
> Attachments: Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_01.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_02.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_03.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_04.png, Forge-2.5.0.Final-JBoss-Developer-Studio.7.1.1.GA-no running_05.png
>
>
> IDE: JBoss Developer Studio 7.1.1.GA
> Forge: 2.5.0.Final
> S.O: Windows 7
> JDK: C:\Java\32-bit\jdk1.7.0_55
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 7 months