June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19969) JMX plugins have wrong provider?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19969?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19969. --------------------------------- Resolution: Done pushed to b2 > JMX plugins have wrong provider? > -------------------------------- > > Key: JBIDE-19969 > URL: https://issues.jboss.org/browse/JBIDE-19969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: plugins-provider.png > > > Vlado noticed today that some plugins have strange provider. > (All features have "JBoss by Red Hat" as their provider.) > Some JMX plugins have: > JvmMonitor.org > One has: > Jeff Mesnil > [~rob.stryker], can you check if this is correct? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19969) JMX plugins have wrong provider?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19969?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19969: --------------------------------------------- it is our fork - jvmmonitor.org are not providing it so yes we should change it. > JMX plugins have wrong provider? > -------------------------------- > > Key: JBIDE-19969 > URL: https://issues.jboss.org/browse/JBIDE-19969 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: plugins-provider.png > > > Vlado noticed today that some plugins have strange provider. > (All features have "JBoss by Red Hat" as their provider.) > Some JMX plugins have: > JvmMonitor.org > One has: > Jeff Mesnil > [~rob.stryker], can you check if this is correct? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-20100: ------------------------------------------- Summary: how to make users aware of fuse and other tooling only being available from earlyaccess? Key: JBIDE-20100 URL: https://issues.jboss.org/browse/JBIDE-20100 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Max Rydahl Andersen [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. Some comments: "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." Suggestion: "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20097) [jiralint] Update filters so ds_my_next_master_unresolved points to b2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20097?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-20097. --------------------------------------- Resolution: Done This is now fixed, _next_* now don't accept things that are codefrozen. Work on this also revealed that our _maint_ filters been broken for a while since we don't have a 4.2.4 nor 8.1.1 version with a start date set. Thus i've fixed that plus made jiralint builds fail harder if for some reason the jira filters fail to update (just checking if log has HTTPError in them) [~nickboldt] tagging you here as a reminder we should always have a "next" proper named version with a startDate for both maintanence and master versions to avoid filters to go haywire. > [jiralint] Update filters so ds_my_next_master_unresolved points to b2 > ---------------------------------------------------------------------- > > Key: JBIDE-20097 > URL: https://issues.jboss.org/browse/JBIDE-20097 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20097) [jiralint] Update filters so ds_my_next_master_unresolved points to b2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20097?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20097: ---------------------------------------- Fix Version/s: 4.3.0.Beta1 Component/s: build > [jiralint] Update filters so ds_my_next_master_unresolved points to b2 > ---------------------------------------------------------------------- > > Key: JBIDE-20097 > URL: https://issues.jboss.org/browse/JBIDE-20097 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Diógenes Rettori (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ] Diógenes Rettori updated JBIDE-20099: ------------------------------------- Fix Version/s: 4.3.0.Final > enable a logstream for Openshift Pods > ------------------------------------- > > Key: JBIDE-20099 > URL: https://issues.jboss.org/browse/JBIDE-20099 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Diógenes Rettori > Priority: Minor > Fix For: 4.3.0.Final > > > enable the eclipse console to show > oc get logs <pod> > oc get build-logs <build> > You click on the pod, then right-click show logs, or double click go to logs... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Diógenes Rettori (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ] Diógenes Rettori updated JBIDE-20099: ------------------------------------- Description: enable the eclipse console to show oc get logs <pod> oc get build-logs <build> You click on the pod, then right-click show logs, or double click go to logs... was: enable the eclipse console to show oc get logs <pod> oc get build-logs <build> > enable a logstream for Openshift Pods > ------------------------------------- > > Key: JBIDE-20099 > URL: https://issues.jboss.org/browse/JBIDE-20099 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Diógenes Rettori > Priority: Minor > > enable the eclipse console to show > oc get logs <pod> > oc get build-logs <build> > You click on the pod, then right-click show logs, or double click go to logs... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Diógenes Rettori (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ] Diógenes Rettori updated JBIDE-20099: ------------------------------------- Description: enable the eclipse console to show oc get logs <pod> oc get build-logs <build> was: enable the eclipse console to show oc get lods <pod> oc get build-logs <build> > enable a logstream for Openshift Pods > ------------------------------------- > > Key: JBIDE-20099 > URL: https://issues.jboss.org/browse/JBIDE-20099 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Diógenes Rettori > Priority: Minor > > enable the eclipse console to show > oc get logs <pod> > oc get build-logs <build> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Diógenes Rettori (JIRA)

Diógenes Rettori created JBIDE-20099: ---------------------------------------- Summary: enable a logstream for Openshift Pods Key: JBIDE-20099 URL: https://issues.jboss.org/browse/JBIDE-20099 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Diógenes Rettori Priority: Minor enable the eclipse console to show oc get lods <pod> oc get build-logs <build> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19815) Application wizard: As I a user I want to use a template from my local disk to create a new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19815?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19815. ------------------------------------ Labels: application_wizard new_and_noteworthy openshift_v3 (was: application_wizard new_and_noteworthy v3) Resolution: Done > Application wizard: As I a user I want to use a template from my local disk to create a new application > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19815 > URL: https://issues.jboss.org/browse/JBIDE-19815 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: application_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.3.0.Beta1 > > > Add the ability to upload a template from disk -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015