September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14732) Hide preview should hide preview only

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14732?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14732: ----------------------------------- Fix Version/s: LATER (was: 4.2.x) > Hide preview should hide preview only > ------------------------------------- > > Key: JBIDE-14732 > URL: https://issues.jboss.org/browse/JBIDE-14732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Beta1 > Environment: Any > Reporter: Denis Golovin > Assignee: Alexey Kazakov > Labels: usability > Fix For: LATER > > Attachments: dialog-new.gif, dialog.gif > > > Now Hide Preview button forces to close whole right part of wizard. It looks ok, but jumps to much and hides html source too. Looks like this: > !dialog.gif! > Would it be better to have it implemented like this: > !dialog-new.gif! -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2623: ---------------------------------- Next missing IU: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/1321/INSTALL_PLAN=http%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2F%3Bhttp%3A%2F%2Fdownload.jboss.org%2Fjbosstools%2Fdiscovery%2Fnightly%2Fcore%2Ftrunk%2Fjbosstools-directory.xml,eclipseBundleVersion=kepler.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console} Contains: Missing requirement: Spring AOP 4.0.0.20130522-M1 (org.springframework.aop 4.0.0.20130522-M1) requires 'package org.aopalliance.aop [1.0.0,2.0.0)' but it could not be found {code} > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2, 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15509) prepare for JBDS 7.0.1 patch release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15509?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15509: ------------------------------------ After much debate it's been decided that in addition to the actual reason for this patch release, JBIDE-15494, we ought to also update the JBDS update site to include the Kepler SR1 bits, since they were released just last week. Respinning third candidate release now: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=7 Will push to QE when done. > prepare for JBDS 7.0.1 patch release > ------------------------------------ > > Key: JBIDE-15509 > URL: https://issues.jboss.org/browse/JBIDE-15509 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.1.Final > > Attachments: 15509_JBDS701.CR1.png, 15509_JBT4101.CR1.png > > > Placeholder JIRA to contain work needed to do to release JBDS 7.0.1.GA: > 1. branch jbosstools-central from 4.1.x to 4.1.0.x > 2. adjust jbosstools-central/site/category.xml so it only contains the affected features (and feature.sources) > 3. build Central using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-central_410/ which gets its sources from the correct fork/branch > 4. create new composite staging site containing the last stable release + the new staging site for jbosstools-central, eg., > http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... > 5. branch jbdevstudio-product from 4.1.x to 4.1.0.x > 6. ensure that JBDS sources are correctly versioned (eg., 7.0.1 not 7.1.0) > 7. build JBDS using a new job, eg., https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_70/ which sets -DBUILD_ALIAS=GA, pulls from the correct branch origin/jbosstools-4.1.0.x, and sets these overrides in the maven configuration: > {code} > jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c... > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Gary Hu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Gary Hu commented on JBIDE-15185: --------------------------------- A user defined variable pointing to the run time location instead of an absolute path brings a lot of flexibility. This way, every user just needs to set an variable as a system property or in the launch configurations to get the run time server configured. > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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, 6 months

1
0
0 / 0

[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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 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