[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-18650:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Snjezana Peco)
Max,
Could you, please, review this PR?
> Forge wizard window isn't focused after command selection (CTRL-4)
> ------------------------------------------------------------------
>
> Key: JBIDE-18650
> URL: https://issues.jboss.org/browse/JBIDE-18650
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR1
> Environment: jbds 8.0.0.CR1
> [selrahal@fedora20 jbdevstudio]$ uname -a
> Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> [selrahal@fedora20 jbdevstudio]$ java -version
> java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Salem Elrahal
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBDS-3191 at 10/20/14 6:43 AM:
---------------------------------------------------------------------
agreed that we might as well just add the stable site from day one even if just as empty.
Note, exact same concerns exist for jbosstools so would be interesting to bring these mechanisms in sync.
Maybe add a feature to foundation (or similar) that would look for ide.properties for list of updatesites that should be removed/added.
was (Author: maxandersen):
agreed. Note, exact same concerns exist for jbosstools so would be interesting to bring these mechanisms in sync.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associateSites.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------
agreed. Note, exact same concerns exist for jbosstools so would be interesting to bring these mechanisms in sync.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associateSites.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Mickael Istria (JIRA)
Mickael Istria created JBDS-3191:
------------------------------------
Summary: Improve the way we switch between development and GA
Key: JBDS-3191
URL: https://issues.jboss.org/browse/JBDS-3191
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: build
Reporter: Mickael Istria
JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
We need to improve that.
Changes are necessary in:
* features/com.jboss.devstudio.core/feature/p2.inf
* site/associateSites.properties
* results/pom.xml
As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3191:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: ?
CDW qa_ack: ?
CDW release: ?
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associateSites.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months