March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBIDE-13812: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=902017 > openshift-java-client: get rid of external class to (de)code base64 > ------------------------------------------------------------------- > > Key: JBIDE-13812 > URL: https://issues.jboss.org/browse/JBIDE-13812 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. > Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13812: ------------------------------------- Summary: openshift-java-client: get rid of external class to (de)code base64 (was: openshift-java-client: get rid of external class to (de)code bas64) > openshift-java-client: get rid of external class to (de)code base64 > ------------------------------------------------------------------- > > Key: JBIDE-13812 > URL: https://issues.jboss.org/browse/JBIDE-13812 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. > Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code bas64

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13812: ---------------------------------------- Summary: openshift-java-client: get rid of external class to (de)code bas64 Key: JBIDE-13812 URL: https://issues.jboss.org/browse/JBIDE-13812 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead. Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2485) Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2485?page=com.atlassian.jira.plugin.... ] Vlado Pakan edited comment on JBDS-2485 at 3/19/13 5:02 AM: ------------------------------------------------------------ No issues have been found when installed and used with JBDS 7.0.0.Alpha1 was (Author: vpakan): No issues ahve been found when installed and used with JBDS 7.0.0.Alpha1 > Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central > --------------------------------------------------------------- > > Key: JBDS-2485 > URL: https://issues.jboss.org/browse/JBDS-2485 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.0.0.Alpha2 > > > New mirrors: > http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.8.1... > https://devstudio.jboss.com/updates/requirements/subclipse/1.8.18_1.7.8.1/ > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2485) Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2485?page=com.atlassian.jira.plugin.... ] Vlado Pakan resolved JBDS-2485. ------------------------------- Resolution: Done No issues ahve been found when installed and used with JBDS 7.0.0.Alpha1 > Investigate use of Subclipse 1.8.18 & SVNKit 1.7.8.1 in Central > --------------------------------------------------------------- > > Key: JBDS-2485 > URL: https://issues.jboss.org/browse/JBDS-2485 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.0.0.Alpha2 > > > New mirrors: > http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.8.1... > https://devstudio.jboss.com/updates/requirements/subclipse/1.8.18_1.7.8.1/ > New composites: > http://download.jboss.org/jbosstools/updates/kepler/extras/4.30.1/ > https://devstudio.jboss.com/updates/7.0-staging/extras/4.30.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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13711) typo "JBos Enterprise Application Platform"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13711?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13711. --------------------------------- Fix Version/s: 4.1.0.Alpha2 Resolution: Done in master > typo "JBos Enterprise Application Platform" > ------------------------------------------- > > Key: JBIDE-13711 > URL: https://issues.jboss.org/browse/JBIDE-13711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Burr Sutter > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > http://docs.jboss.org/tools/latest/en/jmx_ref_guide/html_single/index.html > Search for "JBos Enterprise" > In 2.4. Managing a JBoss application server Remotely -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2363) Update to 5.0.1 Tooling refers to plugin being "modified" not "updated"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2363?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-2363. --------------------------------------- Resolution: Rejected The behaviour is as expected when you are *installing* software it will say that we are not going to actually install new things, we are just updating thus the request is modified. rejecting this since the request seems bogus. reopen with more details if there is something I'm missing. > Update to 5.0.1 Tooling refers to plugin being "modified" not "updated" > ----------------------------------------------------------------------- > > Key: JBDS-2363 > URL: https://issues.jboss.org/browse/JBDS-2363 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.CR1-SOA > Reporter: Len DiMaggio > Assignee: Douglas Palmer > Fix For: 5.0.4.GA-SOA > > > See bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=867483 -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13796: --------------------------------------------- I'm mostly -1 on this since it affects *everyone* and the only difference is this name. why not call the JBTIS one jbosstools-is-integration-tests or jbosstools-integration-stack-itests ? btw. Which maven convention/other project uses "itest" ? Haven't seen that so I would be interested. > rename jbosstools-integration-tests to jbosstools-itests > -------------------------------------------------------- > > Key: JBIDE-13796 > URL: https://issues.jboss.org/browse/JBIDE-13796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests. > Once renamed, will need to refactor: > * job name > * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/ -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13597) Empty Dialog for downloading EAP is not sufficient

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13597?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13597. --------------------------------- Resolution: Done > After some searches, i did discover a workaround, whereby i wrap my link widget with another composite, and it is that compoosite which holds the tooltip. So this seems to address all concerns. Committing this fix to master. > Empty Dialog for downloading EAP is not sufficient > -------------------------------------------------- > > Key: JBIDE-13597 > URL: https://issues.jboss.org/browse/JBIDE-13597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > Attachments: JBIDE-13597.jpg > > > Supposing you would like to use AS runtime but you don't have any. You can download and configure it when creating a project. > This feature is not correctly enabled for EAP (product, not project), but IMO empty dialog for downloading EAP is not sufficient for users. There should be either some message that is not possible to download a product or link to that dialog should be not clickable at all. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13597) Empty Dialog for downloading EAP is not sufficient

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13597?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13597: ------------------------------------- Discovering if there are runtimes available for download is a long-running process. The only other option is to make the widget invisible, and then, if there are runtimes available, the widget is set to visible. This may work in the case where there are no runtimes available (initial invisible, then remains invisible) but is very confusing to the eye when runtimes ARE available (initial invisible, then suddenly appears). An alternative possibility is to set a tooltip text, however, if the widget is disabled (no runtimes available for download), the tooltip text does NOT appear. So I'd need to live the hyperlink enabled (blue) but have a click on it do nothing. This also would be confusing to the user. I am re-closing this issue because there really isn't any possible way to fix it cleanly. Either we have a widget appear suddenly when runtimes are available, which would confuse a user, or an inconsistant UI (widget is there for some wizards, not there for others), or, the more logical solution, which is that a feature that is not currently available is simply greyed out. This occurs all throughout eclipse. If you right-click on a newly created server, you will see the "Stop" menu item exists, but it is grey. If you right-click on a stopped server, and click show in ->, you will see several grey items as well. After some searches, i did discover a workaround, whereby i wrap my link widget with another composite, and it is that compoosite which holds the tooltip. So this seems to address all concerns. > Empty Dialog for downloading EAP is not sufficient > -------------------------------------------------- > > Key: JBIDE-13597 > URL: https://issues.jboss.org/browse/JBIDE-13597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > Attachments: JBIDE-13597.jpg > > > Supposing you would like to use AS runtime but you don't have any. You can download and configure it when creating a project. > This feature is not correctly enabled for EAP (product, not project), but IMO empty dialog for downloading EAP is not sufficient for users. There should be either some message that is not possible to download a product or link to that dialog should be not clickable at all. -- 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

13 years

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 March 2013