June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1903) Stale values are displayed in the property dropdown for the "Constraint: Add" command in Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1903?page=com.atlassian.jira.plugin... ] George Gastaldi moved JBIDE-17629 to FORGE-1903: ------------------------------------------------ Project: Forge (was: Tools (JBoss Tools)) Key: FORGE-1903 (was: JBIDE-17629) Affects Version/s: 2.6.0.Final (was: 4.2.0.Beta2) Component/s: Java EE UI - Eclipse (was: forge) Security: Public > Stale values are displayed in the property dropdown for the "Constraint: Add" command in Forge > ---------------------------------------------------------------------------------------------- > > Key: FORGE-1903 > URL: https://issues.jboss.org/browse/FORGE-1903 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE, UI - Eclipse > Affects Versions: 2.6.0.Final > Environment: Mac OS X Mavericks, JBDS 8 Beta2, Oracle JDK 7u60, Oracle JDK 8u5 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Attachments: Constraint-Add-ChooseProperty.png, Constraint-Add-First_Step.png, Constraint-Add-SelectDifferentClass.png > > > Stale values are displayed in the "Constraint: Add" wizard if the selected class is modified to a different one in the first step. > The properties of the original class are displayed when choosing the property and the constraint to add to that property in the next step. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1902) Initial context in Forge Console appears to be incorrect

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1902?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1902. ---------------------------------- Fix Version/s: 2.7.0.Final Resolution: Done > Initial context in Forge Console appears to be incorrect > -------------------------------------------------------- > > Key: FORGE-1902 > URL: https://issues.jboss.org/browse/FORGE-1902 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.6.0.Final > Environment: Mac OS X Mavericks 10.9.3, JBDS 8 Beta 2, Oracle JDK 7u60 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 2.7.0.Final > > > When I launch the Forge console for the first time (or restart it), the initial context appears to be incorrectly set. Although the console shows that, Forge does not seem to recognize it. > As an example, the following console output shows different responses to the {{ls}} command without changing the current working directory: > {noformat} > [JDF]$ cd <TAB> > hs_err_pid1248.log jbdevstudio.ini > hs_err_pid1372.log org.jboss.tools.vpe.browsersim/ > jbdevstudio > [JDF]$ pwd > /Users/vineet/workspaces/JDF > [JDF]$ cd <TAB> > .metadata/ RemoteSystemsTempFiles/ > {noformat} > This seems to affect path autocompletion mainly, but is also likely to affect Forge command execution that relies on the current working directory, since paths seem to be computed from JBDS root instead of the current workspace root for the very first time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1902) Initial context in Forge Console appears to be incorrect

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1902?page=com.atlassian.jira.plugin... ] George Gastaldi moved JBIDE-17645 to FORGE-1902: ------------------------------------------------ Project: Forge (was: Tools (JBoss Tools)) Key: FORGE-1902 (was: JBIDE-17645) Affects Version/s: 2.6.0.Final (was: 4.2.0.Beta2) Component/s: UI - Shell (was: forge) Security: Public > Initial context in Forge Console appears to be incorrect > -------------------------------------------------------- > > Key: FORGE-1902 > URL: https://issues.jboss.org/browse/FORGE-1902 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.6.0.Final > Environment: Mac OS X Mavericks 10.9.3, JBDS 8 Beta 2, Oracle JDK 7u60 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > > When I launch the Forge console for the first time (or restart it), the initial context appears to be incorrectly set. Although the console shows that, Forge does not seem to recognize it. > As an example, the following console output shows different responses to the {{ls}} command without changing the current working directory: > {noformat} > [JDF]$ cd <TAB> > hs_err_pid1248.log jbdevstudio.ini > hs_err_pid1372.log org.jboss.tools.vpe.browsersim/ > jbdevstudio > [JDF]$ pwd > /Users/vineet/workspaces/JDF > [JDF]$ cd <TAB> > .metadata/ RemoteSystemsTempFiles/ > {noformat} > This seems to affect path autocompletion mainly, but is also likely to affect Forge command execution that relies on the current working directory, since paths seem to be computed from JBDS root instead of the current workspace root for the very first time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1901) JAX-RS Endpoints should be automatically selected based on the selected JPA Entities

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1901: -------------------------------------- Summary: JAX-RS Endpoints should be automatically selected based on the selected JPA Entities Key: FORGE-1901 URL: https://issues.jboss.org/browse/FORGE-1901 Project: Forge Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Java EE Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1900) JSON should be the default content type when generating JAXRS Endpoints

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1900: -------------------------------------- Summary: JSON should be the default content type when generating JAXRS Endpoints Key: FORGE-1900 URL: https://issues.jboss.org/browse/FORGE-1900 Project: Forge Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Java EE Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1899) EJB Version should be condensed in the JAX-RS Endpoint from Entity wizard

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1899: -------------------------------------- Summary: EJB Version should be condensed in the JAX-RS Endpoint from Entity wizard Key: FORGE-1899 URL: https://issues.jboss.org/browse/FORGE-1899 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Java EE Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future There is a separate page for the EJB Version only. This should be merged into one of the available wizard pages. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1898: -------------------------------------- Summary: Dashes in the project name makes jpa-new-entity execution to fail Key: FORGE-1898 URL: https://issues.jboss.org/browse/FORGE-1898 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Java EE Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1897) Show the file extension of a project type when creating a new project

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1897: -------------------------------------- Summary: Show the file extension of a project type when creating a new project Key: FORGE-1897 URL: https://issues.jboss.org/browse/FORGE-1897 Project: Forge Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Projects Affects Versions: 2.6.0.Final Reporter: George Gastaldi Fix For: 2.x Future When {{Project:New}} wizard is run, it would be nice to show next to each Project Type entry the file extension that is targeted to (WAR. POM, JAR, etc..). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-161) Create a PicketLink addon

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-161?page=com.atlassian.jira.... ] Shane Bryzak updated FORGEPLUGINS-161: -------------------------------------- Summary: Create a PicketLink addon (was: Create a PicketLink plugin) > Create a PicketLink addon > ------------------------- > > Key: FORGEPLUGINS-161 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-161 > Project: Forge Plugins > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Shane Bryzak > Assignee: Shane Bryzak > > George has currently implemented this: > https://github.com/forge/plugin-picketlink > We need a Forge plugin that will create a working security configuration for PicketLink. It should allow the developer to configure one or more identity stores, and optionally create the entity beans for a simple database schema. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1398) Being able to create embeddables

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-1398?page=com.atlassian.jira.plugin... ] Matej Briskar reassigned FORGE-1398: ------------------------------------ Assignee: Matej Briskar > Being able to create embeddables > -------------------------------- > > Key: FORGE-1398 > URL: https://issues.jboss.org/browse/FORGE-1398 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: Matej Briskar > Fix For: 2.x Future > > > As per [FORGE-797] it would be good to have a new command to create an embeddable : > {code} > jpa-new-embeddable --named Address ; > jpa-new-field --named street1 --length 50 ; > jpa-new-field --named street2 ; > jpa-new-field --named city --length 50 ; > jpa-new-field --named state ; > {code} > Then, how do we embed it into a entity ? We could have a new {{--relationshipType}} : > {code} > jpa-new-entity --named Customer ; > jpa-new-field --named address --entity org.agoncal.application.petstore.model.Address --relationshipType Embedded ; > {code} > Except {{Address}} is not an entity. So having {{--entity}} pointing to an embeddable looks strange -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014