[JBoss JIRA] (JBIDE-19000) As a user I want to browse the resources for my projects
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19000?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19000:
----------------------------------
Description:
* Raw view of OpenShift project resources (e.g. services, pods, build configs).
* Resources will display the relevant labels and selectors to allow a user to infer associations between resources
> As a user I want to browse the resources for my projects
> --------------------------------------------------------
>
> Key: JBIDE-19000
> URL: https://issues.jboss.org/browse/JBIDE-19000
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Labels: openshift_v3
> Attachments: 2015-01-06 22.13.bmml, 2015-01-06 22.13.png, OpenShift console.pdf
>
>
> * Raw view of OpenShift project resources (e.g. services, pods, build configs).
> * Resources will display the relevant labels and selectors to allow a user to infer associations between resources
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBTIS-3) Clarify versioning process with respect to jbds releases
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-3?page=com.atlassian.jira.plugin.sy... ]
Paul Leacu closed JBTIS-3.
--------------------------
Resolution: Won't Fix
Housekeeping JBTIS Jira.
JBTIS follows JBT and JBDSIS follows JBDS. WIth Luna that corresponds to JBDSIS 8.0.0/ JBTIS 4.2.0. We'll bump the micro version as each product goes GA (JDV - 8.0.0, B*MS - 8.0.1, FSW - 8.0.2). If an incompatible component update occurs then we'd bump the minor version to 8.1.0.
> Clarify versioning process with respect to jbds releases
> --------------------------------------------------------
>
> Key: JBTIS-3
> URL: https://issues.jboss.org/browse/JBTIS-3
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Reporter: Rob Cernich
> Assignee: Rob Cernich
>
> Clarify the versioning process for the integration stack itself. Specifically, patch releases should not add new features. For example, say a 4.0.0 stack release contains a 1.0.0 component release. If the component is updated to 2.0, that component release would not be a candidate for inclusion in a 4.0.x release. However, an update to 1.0.x would be acceptable.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3289:
-----------------------------------
[~lhein] : you'll have to add <proxyWizard ... category="earlyaccess"> to your Fuse proxy wizard
> JBoss Central proxy wizards need to recognize early access.
> -----------------------------------------------------------
>
> Key: JBDS-3289
> URL: https://issues.jboss.org/browse/JBDS-3289
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.2.GA
> Reporter: Paul Leacu
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months