[JBoss JIRA] (TOOLSDOC-719) JBDS 9.1 GA: Document known issue with some linux versions and GTK3: export SWT_GTK3=0
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-719?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-719:
------------------------------------
This should appear in the query for the release notes since we only list customer issues.
> JBDS 9.1 GA: Document known issue with some linux versions and GTK3: export SWT_GTK3=0
> --------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-719
> URL: https://issues.jboss.org/browse/TOOLSDOC-719
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: Installation Guide
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Supriya Bharadwaj
> Fix For: 9.1 GA
>
>
> See JBIDE-21038 re: workaround required on some linux distros.
> ---
> Before launching Eclipse or JBDS on linux, ensure your console has run this command:
> {code}export SWT_GTK3=0{code}
> Then start Eclipse or JBDS as you would normally, eg.,
> {code}./eclipse
> or
> ./studio/jbdevstudio
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Misha Ali resolved TOOLSDOC-696.
--------------------------------
Resolution: Won't Fix
CDK is released and supported, so I'm closing this as won't fix because not necessary.
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.1 GA
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: CDK
> Fix For: 9.1 GA
>
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3282:
-----------------------------------
Let's start with starting the cdk and openshift https://www.youtube.com/watch?v=h_FACXXl94g
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: screencast
> Fix For: 9.1.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22218?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22218:
-------------------------------------
So all version changes except one false positive : https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79... vs https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07...
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22218
> URL: https://issues.jboss.org/browse/JBIDE-22218
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Central]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
> 5e1220 is 41 commits ago in branch master
> 5e1220 is 35 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599... version change
> - https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79... false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07...
> - https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d... version change
> - https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392... version change
> - https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a... version change
> - https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483... version change
> - https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777... version change
> - https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c... version change
> - https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee... version change
> - https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0... version change
> - https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728... version change
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22218?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-22218.
-------------------------------
Resolution: Rejected
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22218
> URL: https://issues.jboss.org/browse/JBIDE-22218
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Central]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
> 5e1220 is 41 commits ago in branch master
> 5e1220 is 35 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599... version change
> - https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79... false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07...
> - https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d... version change
> - https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392... version change
> - https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a... version change
> - https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483... version change
> - https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777... version change
> - https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c... version change
> - https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee... version change
> - https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0... version change
> - https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728... version change
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22218) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22218?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22218:
--------------------------------
Description:
For JBIDE 4.4.0.Alpha1 [Central]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
If there are no commits listed below, please close (do not resolve) this issue.
Otherwise:
1) Click on each link below.
2) Evaluate whether the given commit *should* be in master
3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
6) When all complete, please close (do not resolve) this issue.
Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
5e1220 is 41 commits ago in branch master
5e1220 is 35 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599... version change
- https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79... false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07...
- https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d... version change
- https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392... version change
- https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a... version change
- https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483... version change
- https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777... version change
- https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c... version change
- https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee... version change
- https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0... version change
- https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728... version change
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
was:
For JBIDE 4.4.0.Alpha1 [Central]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
If there are no commits listed below, please close (do not resolve) this issue.
Otherwise:
1) Click on each link below.
2) Evaluate whether the given commit *should* be in master
3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
6) When all complete, please close (do not resolve) this issue.
Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central/
Searching for commits present in jbosstools-4.3.x and missing from master
Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
5e1220 is 41 commits ago in branch master
5e1220 is 35 commits ago in branch jbosstools-4.3.x
Commits missing from master that are in jbosstools-4.3.x:
- https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599...
- https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79...
- https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d...
- https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392...
- https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a...
- https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483...
- https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777...
- https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c...
- https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee...
- https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0...
- https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728...
[Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Central]
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22218
> URL: https://issues.jboss.org/browse/JBIDE-22218
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Rob Stryker
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Central]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "5e1220" is the last common ancestor of jbosstools-4.3.x and master
> 5e1220 is 41 commits ago in branch master
> 5e1220 is 35 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-central//commit/52703f5ff4059599... version change
> - https://github.com/jbosstools/jbosstools-central//commit/ffa08cbe26125e79... false positive over https://github.com/jbosstools/jbosstools-central/commit/8c73f3e46437b5f07...
> - https://github.com/jbosstools/jbosstools-central//commit/222d14b4e2eae58d... version change
> - https://github.com/jbosstools/jbosstools-central//commit/a0e37ef2cace9392... version change
> - https://github.com/jbosstools/jbosstools-central//commit/aca1bd3d2fbf797a... version change
> - https://github.com/jbosstools/jbosstools-central//commit/108814bd8268a483... version change
> - https://github.com/jbosstools/jbosstools-central//commit/2e1704cc6f010777... version change
> - https://github.com/jbosstools/jbosstools-central//commit/e6a5fcb2080fb83c... version change
> - https://github.com/jbosstools/jbosstools-central//commit/0524f8f8ac0debee... version change
> - https://github.com/jbosstools/jbosstools-central//commit/5489e0c40c3703f0... version change
> - https://github.com/jbosstools/jbosstools-central//commit/68ab08d23b6fe728... version change
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months