September 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] Updated: (SEAMFORGE-137) Should validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-137?page=com.atlassian.jira.plu... ] Lincoln Baxter III updated SEAMFORGE-137: ----------------------------------------- Fix Version/s: 1.0.0.Beta4 (was: 1.0.0.Beta3) > Should validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur > ---------------------------------------------------------------------------------------- > > Key: SEAMFORGE-137 > URL: https://issues.jboss.org/browse/SEAMFORGE-137 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Shell > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 1.0.0.Beta4 > > > Should be invalid for same resource scopes > @Alias("whee") > @Alias("whee") > Should be invalid in same command: > @Option(name="named") > @Option(name="named") > And so on... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-223) PropertyNotFoundException for entities with camelCased properties

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-223?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-223. ---------------------------------------- Resolution: Done > PropertyNotFoundException for entities with camelCased properties > ----------------------------------------------------------------- > > Key: SEAMFORGE-223 > URL: https://issues.jboss.org/browse/SEAMFORGE-223 > Project: Seam Forge > Issue Type: Bug > Reporter: Michael Schuetz > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Beta3 > > > Getting troubles when using camelCase entity property field names. > javax.el.PropertyNotFoundException: The class 'com.acme.domain.Bernd' does not have the property 'bName > Bernd.java: > @Column private String bName; > public String getBName(){ > return this.bName; > } > public void setBName( final String bName){ > this.bName=bName; > } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-344) Varargs options are not picking up unused command parameters

by Lincoln Baxter III (JIRA)

Varargs options are not picking up unused command parameters ------------------------------------------------------------ Key: SEAMFORGE-344 URL: https://issues.jboss.org/browse/SEAMFORGE-344 Project: Seam Forge Issue Type: Bug Components: Shell Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Beta3 @Test public void testVarargsTakesUnusedParameters() throws Exception { assertNull(plugin.getBooleanOptionOmitted()); getShell().execute("motp varargsOption -Pfoo --bar -ext"); assertEquals(3, plugin.getVarargsOptions().size()); assertTrue(plugin.getVarargsOptions().contains("-Pfoo")); assertTrue(plugin.getVarargsOptions().contains("--bar")); assertTrue(plugin.getVarargsOptions().contains("-ext")); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-341) Support autocd like zsh and bash

by Jonathan Fuerth (JIRA)

Support autocd like zsh and bash -------------------------------- Key: SEAMFORGE-341 URL: https://issues.jboss.org/browse/SEAMFORGE-341 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Jonathan Fuerth Priority: Optional If you just type in a directory name at the prompt (including ".." to go up) then forge should just invoke the cd plugin on it. A handy way to save typing and make everything a little faster. (For the historically astute, it's worth noting that Amiga's shell had this feature long before zsh or bash. Nobody ever typed "cd" on Amiga.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-340) Support "cd ..." to go up to grandparent directory, etc.

by Jonathan Fuerth (JIRA)

Support "cd ..." to go up to grandparent directory, etc. -------------------------------------------------------- Key: SEAMFORGE-340 URL: https://issues.jboss.org/browse/SEAMFORGE-340 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Jonathan Fuerth Priority: Optional Ancient versions of Novell Netware supported arbitrary numbers of dots to specify how far up the directory hierarchy to go. Every dot you added meant one more level up: | Novell Shell | Bourne Shell | | cd .. | cd .. | | cd ... | cd ../.. | | cd .... | cd ../../.. | It was handy, but didn't catch on meaningfully in any other CLI I'm aware of. The only downside I can think of to implementing this is that once you get used to it in Forge, it will be annoying to do without in in bash/zsh/etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-338) Fill data plugin for JPA scaffolding

by Jonathan Fuerth (JIRA)

Fill data plugin for JPA scaffolding ------------------------------------ Key: SEAMFORGE-338 URL: https://issues.jboss.org/browse/SEAMFORGE-338 Project: Seam Forge Issue Type: Feature Request Reporter: Jonathan Fuerth Priority: Minor We (developers) often neglect to test our apps with realistic volumes of data until the product is already in production and starting to experience dataset scalability issues. What I'm proposing is to have a command in Forge that will fill in arbitrarily large amounts of random data which is reasonably appropriate to the fields being populated: random strings, numbers, timestamps, and booleans should suffice. Bonus points if the strings are generated using Markov chains from a given body of text. :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-188) Deploying to OpenShift Flex from Forge

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-188?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-188. ---------------------------------------- Awesome! > Deploying to OpenShift Flex from Forge > -------------------------------------- > > Key: SEAMFORGE-188 > URL: https://issues.jboss.org/browse/SEAMFORGE-188 > Project: Seam Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Krishna Raman > Priority: Minor > > I think it makes a lot of sense to be able to deploy applications from the very tool with which they were created. This will be a compelling argument to get your foot in the door with both Forge and OpenShift. I'd like to start by deploying a Java EE 6 web-application. We can build out more 'rhq' commands from there. > * Register for OpenShift, get a Flex account. > * Download Forge, build an app. > * Deploy to OpenShift. > * Done in 10 minutes. > This would provide an OS-agnostic way to interact with OpenShift. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (SEAMFORGE-188) Deploying to OpenShift Flex from Forge

by Krishna Raman (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-188?page=com.atlassian.jira.plu... ] Krishna Raman resolved SEAMFORGE-188. ------------------------------------- Resolution: Done > Deploying to OpenShift Flex from Forge > -------------------------------------- > > Key: SEAMFORGE-188 > URL: https://issues.jboss.org/browse/SEAMFORGE-188 > Project: Seam Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Krishna Raman > Priority: Minor > > I think it makes a lot of sense to be able to deploy applications from the very tool with which they were created. This will be a compelling argument to get your foot in the door with both Forge and OpenShift. I'd like to start by deploying a Java EE 6 web-application. We can build out more 'rhq' commands from there. > * Register for OpenShift, get a Flex account. > * Download Forge, build an app. > * Deploy to OpenShift. > * Done in 10 minutes. > This would provide an OS-agnostic way to interact with OpenShift. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-188) Deploying to OpenShift Flex from Forge

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-188?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFORGE-188: ---------------------------------------------- Is this issue closeable? > Deploying to OpenShift Flex from Forge > -------------------------------------- > > Key: SEAMFORGE-188 > URL: https://issues.jboss.org/browse/SEAMFORGE-188 > Project: Seam Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Krishna Raman > Priority: Minor > > I think it makes a lot of sense to be able to deploy applications from the very tool with which they were created. This will be a compelling argument to get your foot in the door with both Forge and OpenShift. I'd like to start by deploying a Java EE 6 web-application. We can build out more 'rhq' commands from there. > * Register for OpenShift, get a Flex account. > * Download Forge, build an app. > * Deploy to OpenShift. > * Done in 10 minutes. > This would provide an OS-agnostic way to interact with OpenShift. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-305) Update docs and generated apps to use new forge logos

by Lincoln Baxter III (JIRA)

Update docs and generated apps to use new forge logos ----------------------------------------------------- Key: SEAMFORGE-305 URL: https://issues.jboss.org/browse/SEAMFORGE-305 Project: Seam Forge Issue Type: Task Components: Documentation, Scaffold Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Priority: Trivial -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2011