September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15389) User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15389: ------------------------------------- Description: When doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. !tail-files.png! Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. was: Whe doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. !tail-files.png! Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. > User should be able have its custom tail-command persisted so that he doesnt have to re-type it every time. > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15389 > URL: https://issues.jboss.org/browse/JBIDE-15389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha2 > > Attachments: tail-files.png > > > When doing tail-files for an app the user gets the tail-command in a dialog. He then can provide his very own cmd. > !tail-files.png! > Unfortunately whatever he's providing is not persisted. He has to re-type it every time he wants to tail the files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] I just verified JBDS6 (which is equivalent to JUNO + JBT 4.0) and it works for me on STG. awesome! The links to the environment variables, which cause JUNO + JBT 4.0 to break are now gone. I also verified Zent Studio 10 which works for me now when using (the fixed) https://stg.openshift.redhat.com > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15467?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15467: --------------------------------------------- I'm fine with this idea of a "non-abridged" category. I actually think that would be a better name than "Additional JBoss Tools" since what is it "additional" too ? Maybe call it "Additonal JBoss Tools (non-abridged)" or "Additonal JBoss Tools (not found in abridged)" ? > should JBT have a category for "stuff not in Abridged" ? > -------------------------------------------------------- > > Key: JBIDE-15467 > URL: https://issues.jboss.org/browse/JBIDE-15467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein. > So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"? > {code} > org.jboss.tools.arquillian.feature > org.jboss.tools.common.mylyn.feature > org.jboss.tools.gwt.feature > org.jboss.tools.maven.gwt.feature > org.jboss.tools.aerogear.hybrid.feature > org.jboss.tools.vpe.cordovasim.feature > org.jboss.tools.central.themes.feature > org.jboss.tools.birt.feature > org.jboss.tools.forge.ext.feature > {code} > Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- weiwei jiang <wjiang(a)redhat.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] (In reply to weiwei jiang from comment #10) > Reproduced with eclipse Juno & jboss tool for Juno on PROD; > Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD; > Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD; Update the result. Reproduced with eclipse Juno & jboss tool for Juno on PROD; Can not reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD; Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2512) JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2512?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-2512. ------------------------------------- Resolution: Duplicate Issue one is a duplicate of the other. killing this old one. > JBDS70_0010: [Commit] (Dev) (P1) Download of EAP and setup of runtime > --------------------------------------------------------------------- > > Key: JBDS-2512 > URL: https://issues.jboss.org/browse/JBDS-2512 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements, runtime > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Critical > > - Downloading of EAP6 with the appropriate Ts & Cs agreement > - Login/registration process > - All versions EAP6.x (and 7.x) available while the default is latest > - Align project examples/central download -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15435: --------------------------------------------- [~nickboldt], The issue is described by [~fbricon]: "In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed." I think the problem is that there is some broken or non-understood semantics in how the examples define and test the existence of the required plugins. Why is both plugin and connector id necessary ? shouldn't connector id be sufficient ? Right now connector id seem to only be used when deciding what to install. IMO explicit plugin listing is only required if subset of plugins of a connector is enough - and if that is the case, how does a project example list multiple plugins ? and can they use features instead so they don't break if plugins gets added/remvoed ? > "installed plugins" detection seems fishy in project examples / central > ----------------------------------------------------------------------- > > Key: JBIDE-15435 > URL: https://issues.jboss.org/browse/JBIDE-15435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha2 > > > Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. > Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15435: ---------------------------------------- Labels: (was: needinfo) > "installed plugins" detection seems fishy in project examples / central > ----------------------------------------------------------------------- > > Key: JBIDE-15435 > URL: https://issues.jboss.org/browse/JBIDE-15435 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha2 > > > Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins. > Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15396) cannot log into OpenShift (even though credentials are valid)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15396?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15396: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 1003037|https://bugzilla.redhat.com/show_bug.cgi?id=1003037] Hi weiwei jiang (In reply to weiwei jiang from comment #10) > Reproduced with eclipse Juno & jboss tool for Juno on PROD; expected, thanks for confirming. > Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD; completely unexpected and contradicts Nam telling upgrading worked for him. Are you sure that kepler + JBT 4.1. is NOT working for you? > Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD; expected, thanks for confirming (but is in contradiction to the above. JBDS7 == Kepler + JBT 4.1). > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBIDE-15396 > URL: https://issues.jboss.org/browse/JBIDE-15396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBoss Tools 4.0 / JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15451) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15451?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-15451 at 9/9/13 3:59 AM: --------------------------------------------------------------- Hello [~nickboldt], first, sorry for missing step #1 in the description above :-/ I applied PR #82 and #83 to fix the pom parent version I bumped version from 1.5.0 to 1.6.0 on master branch. Issue #JBIDE-15316 was opened for that but I forgot to resolve it until today. Thanks was (Author: xcoulon): Hello [~nickboldt], first, sorry for missing step #1 in the description above :-/ I applied PR #82 and #83 to fix the pom parent version, but why to you suggest to bump version from 1.5.0 to 1.5.100 and not 1.6.0 in master branch ? Thanks > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Webservices] > ---------------------------------------------------------- > > Key: JBIDE-15451 > URL: https://issues.jboss.org/browse/JBIDE-15451 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Webservices] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTIS-163: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1005683 > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3, 4.1.4-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.4-TP > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013