May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1852) Parameter --beanValidationVersion missing in constraint-setup

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1852: ---------------------------------------- Summary: Parameter --beanValidationVersion missing in constraint-setup Key: FORGE-1852 URL: https://issues.jboss.org/browse/FORGE-1852 Project: Forge Issue Type: Feature Request Components: Java EE Affects Versions: 2.6.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future Most {{setup}} commands have a version parameter to choose which version you want to use : {code} cdi-setup --cdiVersion ejb-setup --ejbVersion faces-setup --facesVersion jms-setup --jmsVersion jpa-setup --jpaVersion rest-setup --jaxrsVersion websocket-setup --webSocketVersion {code} At the moment, the only Java EE component that misses this parameter is Bean Validation. The {{constraint-setup}} command has the following parameters : {code} [test]$ constraint-setup TAB --providers --providedScope {code} A parameter {{beanValidationVersion}} parameter should be added. The values would be 1.0 or 1.1. That will have an impact on the XSD of the generated {{validation.xml}} file and the dependencies in the {{pom.xml}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1848: -------------------------------------- Same behavior in 1.3.0.Beta3-v20140524-0705-B627 > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1848: ------------------------------------------- Yeah, the fix wouldn't have been in the build at 5am today. I was just finishing the release at 5:15 :) > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-451) Warn a user if generating relationship CRUD screens and HashCode/Equals are missing

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-451?page=com.atlassian.jira.plugin.... ] Matej Briskar commented on FORGE-451: ------------------------------------- I already created the _GenerateHashCodeEqualsCommand_ in the _parser-java_. However, I am not sure which way to go to finish the issue. Possible solution that I would rather discuss is: Adding a new _FacesEntityValidationWizard_ in the _FacesScaffoldProvider.getGenerationFlow()_ just after _ScaffoldableEntitySelectionWizard_ that will take care of the validation of the selected entites and if some checkbox selected, generate the HashCode/Equals for each entity. Could/Shouldn't this be somehow implemented in _ScaffoldableEntitySelectionWizard_ to provide a more general option for each ScaffoldImpl to provide an EntityValidationWizard? > Warn a user if generating relationship CRUD screens and HashCode/Equals are missing > ----------------------------------------------------------------------------------- > > Key: FORGE-451 > URL: https://issues.jboss.org/browse/FORGE-451 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Assignee: Matej Briskar > Labels: Starter > Fix For: 2.x Future > > > It's necessary to provide these on the entities in order for drop downs to work. If not provided, there should be a WARN message. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1848: -------------------------------------- I'm on 1.3.0.Beta2-v20140523 now.. wait for next nightly? > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1848: ------------------------------------------- Not sure then. Just try rebuilding or using the next nightly. > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1848: -------------------------------------- I can only see Aether Download messages in the console.. > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1848: ------------------------------------------- Hmmm.... start eclipse from a console and you should be able to see it. Otherwise I think it goes to /dev/null > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1848) IDE loose defaultValue on dependent field update

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1848?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1848: -------------------------------------- Where are the IDE forge logs stored? > IDE loose defaultValue on dependent field update > ------------------------------------------------ > > Key: FORGE-1848 > URL: https://issues.jboss.org/browse/FORGE-1848 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Reporter: Aslak Knutsen > Assignee: Lincoln Baxter III > Fix For: 2.6.0.Final > > > Setup: > 2 DropDown lists, where the second DropDown's value depend on the value of the first DropDown. > Steps: > 1. Select a value from DropDown 1 > 2. DropDown 2 now has the defaultValue selected > 3. Select a new value from DropDown 1 > Step 4 - Expected: > DropDown 2 should now have the new defaultValue selected > Step 4 - Behavior: > DropDown 2's valueChoices are updated, but no defaultSelection is done > Example command: > https://github.com/aslakknutsen/plugin-arquillian/blob/8e3dfd162126cada80... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1276) Upgrade Furnace-CDI to Weld 2.2.0

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1276?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1276. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.6.0.Final (was: 2.x Future) Resolution: Done Done. > Upgrade Furnace-CDI to Weld 2.2.0 > --------------------------------- > > Key: FORGE-1276 > URL: https://issues.jboss.org/browse/FORGE-1276 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 2.6.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014