[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22151:
------------------------------------------
[~cathat] you were trying to install from JBoss Tools 4.4.x Nightly with http://download.jboss.org/jbosstools/neon/snapshots/updates/ update site, didnt you?
> Failed to install JBT in Eclipse
> --------------------------------
>
> Key: JBIDE-22151
> URL: https://issues.jboss.org/browse/JBIDE-22151
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: Operating System: have tried Fedora 17 and 22
> jbt version: 3.2.0.Alpha1-v20160409-1043-B1241
> eclipse:
> Version: Neon Milestone 6 (4.6.0M6)
> Build id: 20160329-0659
> Reporter: Chunyun Chen
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt44alpha1-os3-1.png, jbt44alpha1-os3.png, jbt_installation_1.png, jbt_installation_2.png
>
>
> Will meet below dependency errors when installing jbt in eclipse:
> "
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found
> Cannot satisfy dependency:
> From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241]
> "
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22187:
-------------------------------------
Priority: Minor (was: Major)
> Connection wizard: Should not be able to create duplicate Openshift connections
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22187:
-------------------------------------
Summary: Connection wizard: Should not be able to create duplicate Openshift connections (was: Connection wizard: Duplicate Openshift connections)
> Connection wizard: Should not be able to create duplicate Openshift connections
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22187) Connection wizard: Duplicate Openshift connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22187:
-------------------------------------
Labels: connection_wizard openshift_v3 (was: )
> Connection wizard: Duplicate Openshift connections
> --------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22187) Connection wizard: Duplicate Openshift connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22187:
-------------------------------------
Summary: Connection wizard: Duplicate Openshift connections (was: Duplicate Openshift connections)
> Connection wizard: Duplicate Openshift connections
> --------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-679) Add UDF Test
by Matus Makovy (JIRA)
Matus Makovy created JBTIS-679:
----------------------------------
Summary: Add UDF Test
Key: JBTIS-679
URL: https://issues.jboss.org/browse/JBTIS-679
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.3.0.CR1
Reporter: Matus Makovy
Assignee: Matus Makovy
Fix For: 4.3.0.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-21621 at 4/22/16 4:22 AM:
----------------------------------------------------------------
[~rawagner], what is the course of action now? RedDeer master is now 1.1.0-SNAPSHOT? Shall I create a milestone and give it to Nick to put to TP for 4.4.0.Alpha1? Or shall we release 1.1.0 now and use that and move master to 1.2.0-SNAPSHOT? We still have a few days for that - deadline is April 27.
Another option would be to keep using master for now and postpone this for Alpha2 or the next milestone. But I think it's desirable to have the right version of RedDeer in the TP for 4.4.0.Alpha1 release. What do you think?
Please reassign back to me when we know what we want and I will take it from there.
was (Author: mmalina):
[~rawagner], what is the course of action now? RedDeer master is now 1.1.0-SNAPSHOT? Shall I create a milestone and give it to Nick to put to TP for 4.4.0.Alpha1? We still have a few days for that - deadline is April 27.
Another option would be to keep using master for now and postpone this for Alpha2 or the next milestone. But I think it's desirable to have the right version of RedDeer in the TP for 4.4.0.Alpha1 release. What do you think?
Please reassign back to me when we know what we want and I will take it from there.
> Include proper version of RedDeer to TP
> ---------------------------------------
>
> Key: JBIDE-21621
> URL: https://issues.jboss.org/browse/JBIDE-21621
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Vlado Pakan
> Assignee: Rastislav Wagner
> Fix For: 4.4.0.Alpha1
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months