September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-12929) Delete dialog invoked by Del key is not located correctly

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12929?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-12929. ----------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.0.x) Resolution: Done Fixed in Kepler SR1. > Delete dialog invoked by Del key is not located correctly > --------------------------------------------------------- > > Key: JBIDE-12929 > URL: https://issues.jboss.org/browse/JBIDE-12929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.0.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha2 > > Attachments: JBIDE-12929_context_menu.jpg, JBIDE-12929_del_key.jpg, org.eclipse.wst.server.ui_1.4.1.v20120821_1330.jar > > > I hope this is not bug only in my environment. When I delete archive from server with context menu, delete dialog is opened in the middle of the eclipse screen. However, when invoking with Del key, it is located outside the eclipse (if eclipse not maximized of course). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14619) Server's editor is horizontally scrolled back

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14619?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-14619. ----------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: LATER) Resolution: Done Fixed in Kepler SR1. > Server's editor is horizontally scrolled back > ---------------------------------------------- > > Key: JBIDE-14619 > URL: https://issues.jboss.org/browse/JBIDE-14619 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha2 > > > When server's editor doesn't fit to one window (e.g Runtime Environment name is too long) there is a horizontal scroll at the bottom for user to be able to manage all provided configuration settings. > When I move to the right part of editor and click on any widget (text, combobox ...) editor is scrolled back to the initial view. > This is happening only for the first time after editor's opening. > Reproducing steps are captured in [screencast|http://www.youtube.com/watch?v=Kzy_2le2ivg&feature=youtu.be] -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15541) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15541?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15541 at 9/30/13 2:57 PM: ------------------------------------------------------------- Reopen. Feature(s) not correctly bumped to include changed version of forge runtime (1.3.3 -> 1.4.1). Containing feature should be bumped to 1.2.1, since 1.2.0 was released in JBT 4.1.0.Final in July. For instructions on how to bump, see step 1 in issue description above. was (Author: nickboldt): Reopen. Feature(s) not correctly bumped to include changed version of forge runtime (1.3.3 -> 1.4.1). Containing feature should be bumped to 1.2.1, since 1.2.0 was released in JBT 4.1.0.Final in July. > For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge] > ---------------------------------------------------- > > Key: JBIDE-15541 > URL: https://issues.jboss.org/browse/JBIDE-15541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha2 > > > For JBIDE 4.1.1.Alpha2 [Forge]: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2 > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.31.0.Alpha2 > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Alpha2x > git push origin jbosstools-4.1.1.Alpha2x > {code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15382) Create target platform from Kepler SR1 dependencies

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15382?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15382: ---------------------------------- Fix Version/s: 4.1.1.Alpha2 > Create target platform from Kepler SR1 dependencies > --------------------------------------------------- > > Key: JBIDE-15382 > URL: https://issues.jboss.org/browse/JBIDE-15382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.1.Alpha2 > > > Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0. > [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1 > There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items. > For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS. > === FORMAL REQUEST === > Reason: Leverage bugfixs of Kepler SR1 RC1 (or RC2 for components which already submitted RC2) > License and owner: EPL, Eclispe community > Original repository: download.eclipse.org webtools,kepler,mylyn,tm,m2e,orbit > JBoss Mirrored repository: > Source: git.eclipse.org > Affected projects: All > Required in devstudio: Yes > Type of dependency: distributions > List of bundles: only some version changed + new dependency for EGit (org.tukaani.xy) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15574) Wildfly management plugin getting unsupported class version unit test errors

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15574?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15574: -------------------------------- Description: This should be fixed in wildfly beta. There is nothing that tools can do to fix this. The relevant server jars need to rebuilt with a lower class version. https://issues.jboss.org/browse/WFLY-2072 We will switch our unit tests to beta1 as soon as it is available. was: This should be fixed in beta. There is nothing that tools can do to fix this. The relevant server jars need to rebuilt with a lower class version. https://issues.jboss.org/browse/WFLY-2072 We will switch our unit tests to beta1 as soon as it is available. > Wildfly management plugin getting unsupported class version unit test errors > ---------------------------------------------------------------------------- > > Key: JBIDE-15574 > URL: https://issues.jboss.org/browse/JBIDE-15574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > This should be fixed in wildfly beta. There is nothing that tools can do to fix this. The relevant server jars need to rebuilt with a lower class version. > https://issues.jboss.org/browse/WFLY-2072 > We will switch our unit tests to beta1 as soon as it is available. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15586) Allow RuntimeUIActivator to use BaseUIActivator...

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15586?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15586. --------------------------------- Resolution: Done Pushed to master with the following commit: https://github.com/jbosstools/jbosstools-base/commit/239d6688fa7e52701397... Changes build locally. Majority of changes are hte new logging method, the cleaned up shared images, and hte cleaned up tracing. > Allow RuntimeUIActivator to use BaseUIActivator... > --------------------------------------------------- > > Key: JBIDE-15586 > URL: https://issues.jboss.org/browse/JBIDE-15586 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > BaseUIActivator includes methods for tracing, logging, and shared images. Allow runtimes to use these apis and remove unneeded internal apis. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15587) Convert downloadRuntime wizard to use WizardFragments in foundation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15587?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15587. --------------------------------- Resolution: Done This was pushed with the following commit: https://github.com/jbosstools/jbosstools-base/commit/f39421537a3520afa3e5... If you look closely, you'll see the large majority of the patch was moving 50% of one class out into a utility class and small changes for clarity. Other than that, all changes are very small and obvious when converting a wizard page to a wizard fragment. > Convert downloadRuntime wizard to use WizardFragments in foundation > ------------------------------------------------------------------- > > Key: JBIDE-15587 > URL: https://issues.jboss.org/browse/JBIDE-15587 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Convert the download runtimes wizard to use the wizard fragment framework to allow for easier implementation of the ToC pages in the future. Very versatile framework. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15591) Stacks in Master should be version 1.1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15591?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15591. --------------------------------- Resolution: Done Pushed to master. Simple version change. > Stacks in Master should be version 1.1.0 > ---------------------------------------- > > Key: JBIDE-15591 > URL: https://issues.jboss.org/browse/JBIDE-15591 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Self-explanatory title. Version was not bumped for master yet. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15591) Stacks in Master should be version 1.1.0

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15591: ----------------------------------- Summary: Stacks in Master should be version 1.1.0 Key: JBIDE-15591 URL: https://issues.jboss.org/browse/JBIDE-15591 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.2.0.Alpha1 Self-explanatory title. Version was not bumped for master yet. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15590) Central should avoid using internal apis inside runtime

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15590: ----------------------------------- Summary: Central should avoid using internal apis inside runtime Key: JBIDE-15590 URL: https://issues.jboss.org/browse/JBIDE-15590 Project: Tools (JBoss Tools) Issue Type: Task Components: central Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Fred Bricon Fix For: 4.2.0.Alpha1 Eventually, internal packages inside runtimes will be just that... internal. They will not be exposed. Central should ensure no internal code is being referenced. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013