May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] Daniel Cunha updated FORGE-1622: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/467 > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.x Future > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] Daniel Cunha reassigned FORGE-1622: ----------------------------------- Assignee: Daniel Cunha > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.x Future > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1860) Writing files with content

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1860?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1860: ------------------------------------- Description: I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : {code} # Creates a project project-new --named test # Adds a few extra files and directories mkdir src/main/script ; touch src/main/resources/insert.sql ; // This creates an empty file touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file version # #################### # # System Properties # #################### /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) # #################### # # Datasource # #################### /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource )))) {code} And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) George mentioned on the mailing list : ??I think piping to a file would be more intuitive and it should work now:?? {code} echo Hi > a.txt {code} The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. {code} [Devoxx]$ ls [Devoxx]$ project-new --named testecho ***SUCCESS*** Project named 'testecho' has been created. [testecho]$ ls pom.xml src [testecho]$ echo Text to add to this new file > newfile.txt [testecho]$ ls pom.xml src [testecho]$ cd .. [Devoxx]$ ls newfile.txt testecho [Devoxx]$ [testecho]$ echo One test again > ./file.txt [testecho]$ ls pom.xml src {code} was: I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : {code} # Creates a project project-new --named test # Adds a few extra files and directories mkdir src/main/script ; touch src/main/resources/insert.sql ; // This creates an empty file touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file version # #################### # # System Properties # #################### /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) # #################### # # Datasource # #################### /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource {code} And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) George mentioned on the mailing list : ??I think piping to a file would be more intuitive and it should work now:?? {code} echo Hi > a.txt {code} The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. {code} [Devoxx]$ ls [Devoxx]$ project-new --named testecho ***SUCCESS*** Project named 'testecho' has been created. [testecho]$ ls pom.xml src [testecho]$ echo Text to add to this new file > newfile.txt [testecho]$ ls pom.xml src [testecho]$ cd .. [Devoxx]$ ls newfile.txt testecho [Devoxx]$ [testecho]$ echo One test again > ./file.txt [testecho]$ ls pom.xml src {code} > Writing files with content > -------------------------- > > Key: FORGE-1860 > URL: https://issues.jboss.org/browse/FORGE-1860 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : > {code} > # Creates a project > project-new --named test > # Adds a few extra files and directories > mkdir src/main/script ; > touch src/main/resources/insert.sql ; // This creates an empty file > touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file > version > # #################### > # # System Properties > # #################### > /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) > # #################### > # # Datasource > # #################### > /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource > )))) > {code} > And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) > George mentioned on the mailing list : > ??I think piping to a file would be more intuitive and it should work now:?? > {code} > echo Hi > a.txt > {code} > The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. > {code} > [Devoxx]$ ls > [Devoxx]$ project-new --named testecho > ***SUCCESS*** Project named 'testecho' has been created. > [testecho]$ ls > pom.xml src > [testecho]$ echo Text to add to this new file > newfile.txt > [testecho]$ ls > pom.xml src > [testecho]$ cd .. > [Devoxx]$ ls > newfile.txt testecho > [Devoxx]$ > [testecho]$ echo One test again > ./file.txt > [testecho]$ ls > pom.xml src > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1860) Writing files with content

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1860: ---------------------------------------- Summary: Writing files with content Key: FORGE-1860 URL: https://issues.jboss.org/browse/FORGE-1860 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.6.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future I see myself adding files here and there on my projects (JBoss cli commands, shell scripts, SQL scripts...) and I use the touch command in Forge extensively. But how could I add content to these files ? I mostly write Forge scripts, so I would love to do something like that in my script : {code} # Creates a project project-new --named test # Adds a few extra files and directories mkdir src/main/script ; touch src/main/resources/insert.sql ; // This creates an empty file touch src/main/script/wildfly-show.cli --content (((( // This adds content to the file version # #################### # # System Properties # #################### /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties) # #################### # # Datasource # #################### /subsystem=datasources/data-source=ApplicationBlancheH2DS:read-resource {code} And this command would just create a file with the previous content in it. As you can see, this can be tricky : when to end the content of a file (something similar to <![CDATA[]]>) George mentioned on the mailing list : ??I think piping to a file would be more intuitive and it should work now:?? {code} echo Hi > a.txt {code} The problem with this, is I can't make it work the way I want. In fact, each time I do a {{echo text > file.txt}}, the {{file.txt}} is created in the directory below, not the current one. As I can't create a file in another directory. {code} [Devoxx]$ ls [Devoxx]$ project-new --named testecho ***SUCCESS*** Project named 'testecho' has been created. [testecho]$ ls pom.xml src [testecho]$ echo Text to add to this new file > newfile.txt [testecho]$ ls pom.xml src [testecho]$ cd .. [Devoxx]$ ls newfile.txt testecho [Devoxx]$ [testecho]$ echo One test again > ./file.txt [testecho]$ ls pom.xml src {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1785) Explicitly setup in scaffolding, not in Bean Validation nor in JPA

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1785?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1785: ------------------------------------------ Looks like this has been fixed. > Explicitly setup in scaffolding, not in Bean Validation nor in JPA > ------------------------------------------------------------------ > > Key: FORGE-1785 > URL: https://issues.jboss.org/browse/FORGE-1785 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > By now, most of the {{setup}} commands are optional (see [FORGE-1686] or [FORGE-1479]). Forge takes the setup by default if not specified. Same should happen with scaffolding. Today, to scaffold a JSF application, we need to execute : > {code} > scaffold-setup > scaffold-generate --targets org.test.model.* ; > {code} > It would be better if, following the same principals, the setup command would run as a default, and only this would be needed : > {code} > scaffold-generate --targets org.test.model.* ; > {code} > If we want to explicitelly scaffold an AngularJS app, then we would go : > {code} > scaffold-setup --provider AngularJS ; > scaffold-generate --targets org.test.model.* ; > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1859) New Addon Test should add current project's addon dependencies as options in test dependencies list

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1859: ----------------------------------------- Summary: New Addon Test should add current project's addon dependencies as options in test dependencies list Key: FORGE-1859 URL: https://issues.jboss.org/browse/FORGE-1859 Project: Forge Issue Type: Feature Request Components: Addon Development Affects Versions: 2.6.0.Final Reporter: Lincoln Baxter III Fix For: 2.x Future When using the new Addon Test command, the list of addons the test case should deploy does not include addons that the project has specified in its pom.xml (which should probably be selected by default as well.) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1858) Furnace should provide API for classpath scanning without need to know implementation details

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1858: ----------------------------------------- Summary: Furnace should provide API for classpath scanning without need to know implementation details Key: FORGE-1858 URL: https://issues.jboss.org/browse/FORGE-1858 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.6.0.Final Reporter: Lincoln Baxter III Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1670) JPA Setup Command should allow explicitly overwriting existing persistence units

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1670?page=com.atlassian.jira.plugin... ] Matej Briskar updated FORGE-1670: --------------------------------- Git Pull Request: https://github.com/forge/core/pull/465 > JPA Setup Command should allow explicitly overwriting existing persistence units > --------------------------------------------------------------------------------- > > Key: FORGE-1670 > URL: https://issues.jboss.org/browse/FORGE-1670 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > Labels: Starter > Fix For: 2.x Future > > > JPA Setup should have an "Overwrite" check-box that is enabled only when a name conflict is detected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1832) Upgrade to Roaster 2.5.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1832?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1832. ---------------------------------- Fix Version/s: 2.6.1.Final (was: 2.x Future) Resolution: Done > Upgrade to Roaster 2.5.0.Final > ------------------------------ > > Key: FORGE-1832 > URL: https://issues.jboss.org/browse/FORGE-1832 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: Daniel Cunha > Fix For: 2.6.1.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1832) Upgrade to Roaster 2.5.0.Final

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1832?page=com.atlassian.jira.plugin... ] Daniel Cunha reassigned FORGE-1832: ----------------------------------- Assignee: Daniel Cunha > Upgrade to Roaster 2.5.0.Final > ------------------------------ > > Key: FORGE-1832 > URL: https://issues.jboss.org/browse/FORGE-1832 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: Daniel Cunha > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014