[JBoss JIRA] (JBTIS-883) Remove ModeShape tests
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-883?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-883:
------------------------------------
Description: The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA (JBTIS-794) and will be removed in Devstudio IS 10.0.0.Alpha1 (was: The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA and will be removed in Devstudio IS 10.0.0.Alpha1)
> Remove ModeShape tests
> ----------------------
>
> Key: JBTIS-883
> URL: https://issues.jboss.org/browse/JBTIS-883
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: modeshape, QE
> Affects Versions: 4.3.2.CR1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.3.2.CR1
>
>
> The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA (JBTIS-794) and will be removed in Devstudio IS 10.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-883) Remove ModeShape tests
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-883?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-883:
------------------------------------
Description: The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA (JBTIS-794) and won't be included in Devstudio IS 10.0.0.Alpha1 (was: The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA (JBTIS-794) and will be removed in Devstudio IS 10.0.0.Alpha1)
> Remove ModeShape tests
> ----------------------
>
> Key: JBTIS-883
> URL: https://issues.jboss.org/browse/JBTIS-883
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: modeshape, QE
> Affects Versions: 4.3.2.CR1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.3.2.CR1
>
>
> The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA (JBTIS-794) and won't be included in Devstudio IS 10.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-883) Remove ModeShape tests
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-883:
---------------------------------------
Summary: Remove ModeShape tests
Key: JBTIS-883
URL: https://issues.jboss.org/browse/JBTIS-883
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: modeshape, QE
Affects Versions: 4.3.2.CR1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.3.2.CR1
The ModeShape tooling set as deprecated in JBDS-IS 9.0.1.GA and will be removed in Devstudio IS 10.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23150) Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23150?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23150:
-------------------------------------
Description:
If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
!openshift-explorer-and-properties-both-stacked.png!
and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
steps to reproduce:
# ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
# ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
# EXEC: make Properties view visible
# EXEC: make OpenShift explorer visible. Select an entry
# EXEC: switch back to Properties view
Result:
Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
!properties-empty.png!
Only moving Properties view to a different (visual) container helps.
the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
was:
If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
!openshift-explorer-and-properties-both-stacked.png!
and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
steps to reproduce:
# ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
# ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
# EXEC: make Properties view visible
# EXEC: make OpenShift explorer visible. Select an entry
# EXEC: switch back to Properties view
Result:
Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
!properties-empty.png!
Only moving Properties view to a different (visual) container helps.
> Properties: wont show OpenShift properties if stacked in same container as OpenShift explorer
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23150
> URL: https://issues.jboss.org/browse/JBIDE-23150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: openshift-explorer-and-properties-both-stacked.png, properties-empty.png
>
>
> If you have the OpenShift explorer and the Properties view both stacked in the same view like it is shown in the following screenshot:
> !openshift-explorer-and-properties-both-stacked.png!
> and you start up Eclipse with the Properties view visible (not OpenShift explorer) you wont be able to ever see any property of any OpenShift resource. The properties view always stays empty.
> steps to reproduce:
> # ASSERT: have Properties view and OpenShift explorer (stacked) in the same visual container
> # ASSERT: make sure any view (but OpenShift explorer) is visible when you start Eclipse
> # EXEC: make Properties view visible
> # EXEC: make OpenShift explorer visible. Select an entry
> # EXEC: switch back to Properties view
> Result:
> Properties view stays empty. You can switch back and forth, you wont get any content in the properties view.
> !properties-empty.png!
> Only moving Properties view to a different (visual) container helps.
> the steps simply show a reliable way to reproduce it. I think there are more cases where this happens. Root cause could be in platform, not sure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-23092:
------------------------------------
Hi, I've created jbosstools-4.4.1.x branch in jbdevstudio-qa repo.
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months