September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18442) Windows suddenly resizing and getting stuck in the middle of the screen in JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18442?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-18442. --------------------------------- Closing as duplicate. Please see linked issue JBDS-2499 for details. > Windows suddenly resizing and getting stuck in the middle of the screen in JBDS > ------------------------------------------------------------------------------- > > Key: JBIDE-18442 > URL: https://issues.jboss.org/browse/JBIDE-18442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 8.0.0.CR1 > Environment: Fedora 20 > Reporter: Suz Dorfield > Assignee: Denis Golovin > > Clicking Window -> Preferences and navigating through the list of options occasionally results in the Preferences window suddenly resizing into a vertical line that gets stuck in the middle of the screen. This does not happen every time Preferences are accessed, does not have a trigger, and appears to be random. I have also seen this happen to the "About JBoss Developer Studio" window. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18442) Windows suddenly resizing and getting stuck in the middle of the screen in JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18442?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-18442. ----------------------------------- Resolution: Duplicate Issue > Windows suddenly resizing and getting stuck in the middle of the screen in JBDS > ------------------------------------------------------------------------------- > > Key: JBIDE-18442 > URL: https://issues.jboss.org/browse/JBIDE-18442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 8.0.0.CR1 > Environment: Fedora 20 > Reporter: Suz Dorfield > Assignee: Denis Golovin > > Clicking Window -> Preferences and navigating through the list of options occasionally results in the Preferences window suddenly resizing into a vertical line that gets stuck in the middle of the screen. This does not happen every time Preferences are accessed, does not have a trigger, and appears to be random. I have also seen this happen to the "About JBoss Developer Studio" window. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18444) jst.web.kb should not depend on org.codehaus.plexus.util

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18444?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18444: ------------------------------------ Fix Version/s: 4.2.0.CR2 > jst.web.kb should not depend on org.codehaus.plexus.util > -------------------------------------------------------- > > Key: JBIDE-18444 > URL: https://issues.jboss.org/browse/JBIDE-18444 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Fred Bricon > Fix For: 4.2.0.CR2 > > > On my local environment using m2e 1.6, I see some failure starting eclipse : > {noformat} > Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" > -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" > org.jboss.tools.jst.web.kb [989] > Unresolved requirement: Import-Package: org.codehaus.plexus.util > {noformat} > plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). > Apache commons-io should be used in [RemoteFileManager|https://github.com/jbosstools/jbosstools-jst/commit/cd9...] instead, as it is available in eclipse orbit. It provides the same capabilities : > * [copy(InputStream, OutputStream)|http://commons.apache.org/proper/commons-io/apidocs/org/apa..., java.io.OutputStream)] > * [closeQuietly(...)|http://commons.apache.org/proper/commons-io/apidocs/org...] > I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3166) XML identation size is not editable

by Stefan Miklosovic (JIRA)

Stefan Miklosovic created JBDS-3166: --------------------------------------- Summary: XML identation size is not editable Key: JBDS-3166 URL: https://issues.jboss.org/browse/JBDS-3166 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 8.0.0.CR1 Environment: JBDS 8.0.CR1b, Eclipse 4.4 Reporter: Stefan Miklosovic https://mojo.redhat.com/servlet/JiveServlet/showImage/102-149246-4-928027... Window -> Preferencies -> XML -> XML Files -> Editor Ident using spaces is checked. Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-328) JBTIS Target Platform modification - 8.0.0.Beta1

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-328?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-328. ------------------------------ Resolution: Done Published to nexus: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... https://github.com/jbosstools/jbosstools-integration-stack/commit/899a19e... > JBTIS Target Platform modification - 8.0.0.Beta1 > ------------------------------------------------ > > Key: JBTIS-328 > URL: https://issues.jboss.org/browse/JBTIS-328 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 8.0.0.Beta1, 4.2.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Beta1-TP > > > Proposed JBTIS TP modifications are are follows: > 1. Pick up the org.eclipse.birt.feature.group for use in Teiid > 2. Update to Luna SR1 > http://download.jboss.org/jbosstools/updates/requirements/luna/2014091809... > 3. Update JBoss Tools core target dependencies to CR1 > http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1... > http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.CR1... > 4. Update orbit requirements to 2014 > http://download.jboss.org/jbosstools/updates/requirements/orbit/R20140525... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-331) Get the integration stack into Early Access in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-331?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-331: ---------------------------------- == STEP 1: Build & Release == Procedure is the same that it was for JBT IS 4.1 / JBDS IS 7, except that you need to label the connectors with the correct certificationId = *com.jboss.jbds.discovery.certification.earlyaccess* Here are a couple of examples: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools... https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... The directory.xml file is the same, eg., https://devstudio.redhat.com/updates/8.0-staging/devstudio-directory.xml (forthcoming CR2, starting in a couple weeks) https://devstudio.redhat.com/updates/8.0-development/devstudio-directory.xml (currently CR1 released milestone) https://devstudio.redhat.com/updates/8.0/devstudio-directory.xml (future location of 8.0.0.GA; currently empty) It is not necessary to refactor (or copy) your plugin to include .earlyaccess in the name, UNLESS you plan to have one plugin for "early access" and one for "released" content, as we do in JBT/JBDS. (You can also include both types of content in the same plugin.) To release Early Access integration stack content once it goes GA, simply change the certificationId from *com.jboss.jbds.discovery.certification.earlyaccess* to another value, and push out a new plugin jar. Possible values are listed here Supported, Tested, External, Technology Preview, Experimental: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... ---- == STEP 2: Declaration of EA IUs == In order for users to know that they have Early Access content installed when they open the Help > About dialog, you also need to update these files: http://download.jboss.org/jbosstools/updates/development/luna/jbosstools-... https://devstudio.redhat.com/updates/8.0-staging/discovery/devstudio-earl... https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyacces... The location of these EA config files are listed in this global properties file, which is used for both JBT and JBDS configuration: http://download.jboss.org/jbosstools/configuration/ide-config.properties > Get the integration stack into Early Access in JBoss Central > ------------------------------------------------------------ > > Key: JBTIS-331 > URL: https://issues.jboss.org/browse/JBTIS-331 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Procedure for encorporating the IS into Early Access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18404) InAppBrowser struggles with POST

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18404?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18404: -------------------------------------- [~ibuziuk] If we are not close to a good solution, I think we can punt this one to next release. > InAppBrowser struggles with POST > -------------------------------- > > Key: JBIDE-18404 > URL: https://issues.jboss.org/browse/JBIDE-18404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.0.CR2 > > > The following inAppBrowserSamle doesn't work properly - > https://github.com/ibuziuk/google-api-oauth-phonegap -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-331) Get the integration stack into Early Access in JBoss Central

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-331: -------------------------------- Summary: Get the integration stack into Early Access in JBoss Central Key: JBTIS-331 URL: https://issues.jboss.org/browse/JBTIS-331 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 8.0.0.Alpha2 Reporter: Paul Leacu Assignee: Paul Leacu Procedure for encorporating the IS into Early Access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18239: ------------------------------------ OK, so what I heard here was: For Central: * For JBDS: "move the JBT content that is currently in JBoss Central into the JBDS update site, but leave it uncategorized; this makes it still accessible in Central but *hidden* in the JBDS update site zip and therefore less likely to be accidentally installed by a naive user doing an offline install" * For JBT: "remove the JBT content that is currently in JBoss Central; this duplicated content is already in the JBT Central composite (JBT + JBT TP + JBoss Central)" And for EA: * Build a new update site (like what I had above in the PR, but containing ONLY the EA content) and use that instead of the EA TP. Aside: I think you mean "ad nauseum" or "ad infinitum", rather than "ad libitum" [1]. [1] http://en.wikipedia.org/wiki/Ad_libitum > Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18239 > URL: https://issues.jboss.org/browse/JBIDE-18239 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > Attachments: JBIDE18239-proposed.png > > > In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.). > We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG. > These would be produced as new zips using the JBT aggregate builder: > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ > Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18444) jst.web.kb should not depend on org.codehaus.plexus.util

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18444?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18444: -------------------------------- Description: On my local environment using m2e 1.6, I see some failure starting eclipse : {noformat} Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" org.jboss.tools.jst.web.kb [989] Unresolved requirement: Import-Package: org.codehaus.plexus.util {noformat} plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). Apache commons-io should be used in [RemoteFileManager|https://github.com/jbosstools/jbosstools-jst/commit/cd9...] instead, as it is available in eclipse orbit. It provides the same capabilities : * [copy(InputStream, OutputStream)|http://commons.apache.org/proper/commons-io/apidocs/org/apa..., java.io.OutputStream)] * [closeQuietly(...)|http://commons.apache.org/proper/commons-io/apidocs/org...] I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. was: On my local environment using m2e 1.6, I see some failure starting eclipse : {noformat} Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" org.jboss.tools.jst.web.kb [989] Unresolved requirement: Import-Package: org.codehaus.plexus.util {noformat} plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). Apache commons-io should be used insted, as it is available in eclipse orbit. It provides the same capabilities. I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. > jst.web.kb should not depend on org.codehaus.plexus.util > -------------------------------------------------------- > > Key: JBIDE-18444 > URL: https://issues.jboss.org/browse/JBIDE-18444 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.CR1 > Reporter: Fred Bricon > > On my local environment using m2e 1.6, I see some failure starting eclipse : > {noformat} > Unresolved requirement: Require-Bundle: org.jboss.tools.jst.web.kb; visibility:="reexport" > -> Bundle-SymbolicName: org.jboss.tools.jst.web.kb; bundle-version="3.6.0.CR1-v20140711-0354-B645"; singleton:="true" > org.jboss.tools.jst.web.kb [989] > Unresolved requirement: Import-Package: org.codehaus.plexus.util > {noformat} > plexus is provided by the m2e runtime, so should not be a dependency of jst (which was added by this [commit|https://github.com/jbosstools/jbosstools-jst/commit/cd919ad62f2d5b...]). > Apache commons-io should be used in [RemoteFileManager|https://github.com/jbosstools/jbosstools-jst/commit/cd9...] instead, as it is available in eclipse orbit. It provides the same capabilities : > * [copy(InputStream, OutputStream)|http://commons.apache.org/proper/commons-io/apidocs/org/apa..., java.io.OutputStream)] > * [closeQuietly(...)|http://commons.apache.org/proper/commons-io/apidocs/org...] > I'm not entirely sure why I see the error in my workspace, plexus should be available, but the real point here, is that this dependency should never be there in the first place. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014