[JBoss JIRA] (JBIDE-22275) oc version is not recognized
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:33 AM:
-------------------------------------------------------------------------
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two hyphens, like in oc v1.2.0--rc2
was (Author: scabanovich):
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two --, like in oc v1.2.0--rc2
> oc version is not recognized
> ----------------------------
>
> Key: JBIDE-22275
> URL: https://issues.jboss.org/browse/JBIDE-22275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: oc_warning.png
>
>
> Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0.
> !oc_warning.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-503) Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-503?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-503.
-----------------------------------
Closed as obsolete. Current JBTIS TP which is 4.3.1.Final contains JBT TP 4.52.0.FInal and Locus 1.6.0.Final
> Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final
> -----------------------------------------------------------------
>
> Key: JBTIS-503
> URL: https://issues.jboss.org/browse/JBTIS-503
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.0.Final-TP, 4.3.0.Alpha2
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Update JBTIS TP JBT core TP to 4.51.0.Final/ Locus to 1.3.0.Final
> *Project page/sources:*
> *Version:* 4.51.0.Final
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBDSIS/ JBTIS
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22275) oc version is not recognized
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22275:
-----------------------------------------------
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two '-', like in oc v1.2.0--rc2
> oc version is not recognized
> ----------------------------
>
> Key: JBIDE-22275
> URL: https://issues.jboss.org/browse/JBIDE-22275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: oc_warning.png
>
>
> Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0.
> !oc_warning.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22275) oc version is not recognized
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22275 at 4/29/16 10:31 AM:
-------------------------------------------------------------------------
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two --, like in oc v1.2.0--rc2
was (Author: scabanovich):
OCBinaryValidator.OC_VERSION_LINE_PATTERN expects now two '-', like in oc v1.2.0--rc2
> oc version is not recognized
> ----------------------------
>
> Key: JBIDE-22275
> URL: https://issues.jboss.org/browse/JBIDE-22275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: oc_warning.png
>
>
> Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0.
> !oc_warning.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22276) Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22276?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22276:
-----------------------------------------------
Eclipse prefers 'Browse...' when it is evident what is going to be selected.
> Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22276
> URL: https://issues.jboss.org/browse/JBIDE-22276
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3, server_adapter_wizard
>
> In New OpenShift Server Adapter wizard there is a text widget for Eclipse project. Next to it there is a Browse... button which allow to select an eclipse project from workspace.
> IN New OpenShift Application Wizard there is a text widget for Eclipse project to be used for a new application. Next to it there is a Browse... button which allow to select an eclipse project from workspace. (On the same wizard page user can select a template from local file system/workspace and there we use correct buttons.)
> Earlier we were using Browse... button for real browsing using native file browser/chooser. Now we use it for selecting a project from workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3872) rename JBoss perspective?
by Todd Mancini (JIRA)
[ https://issues.jboss.org/browse/JBDS-3872?page=com.atlassian.jira.plugin.... ]
Todd Mancini commented on JBDS-3872:
------------------------------------
Is this perspective specifically tied to JBoss? When I read this: http://docs.jboss.org/tools/3.3.0.Final/en/as/html/perspective.html, it sounds like a major feature is that it gives you a server explorer for JBoss servers.
If this perspective is intimately tied to JBoss, then I would not necessarily rename it. However, in that case, I may suggest that we need a new default perspective. I'd love to hear some opinions on this.
> rename JBoss perspective?
> -------------------------
>
> Key: JBDS-3872
> URL: https://issues.jboss.org/browse/JBDS-3872
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.0.0.Alpha2
>
> Attachments: icon-titlebar-jbds10.png
>
>
> Should we rename the default perspective that opens OOTB in devstudio so it's not the "JBoss Perspective? Reason I ask is that it's the first word you see in the titlebar when you fire up DS for the first time:
> !icon-titlebar-jbds10.png!
> We're rebranding Central, the product, and everything in Devstudio. Should we also rename the JBoss perspective?
> cc: [~fbricon] [~akazakov]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months