January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4204: -------------------------------- Assignee: Supriya Bharadwaj (was: Snjezana Peco) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Supriya Bharadwaj > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4204: ---------------------------------- RPM solution rejected in https://bugzilla.redhat.com/show_bug.cgi?id=1406886 as Fedora 25 not a supported environment for RHSCL rpms, and Wayland isn't planned to be in RHEL 7 any time soon (or ever). If this becomes a problem in RHEL 8, we can address it then, assuming Wayland support for Eclipse isn't already fixed by then. New KI in the devstudio 10.2 release notes doc looks good. Thanks, [~supriya.bharadwaj] ! > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Workaround Description: {code}export GDK_BACKEND=x11 ./eclipse{code} Or, use the new devstudio-wayland script in your ~/devstudio installation folder, which does the same thing: {code} ~/devstudio/devstudio-wayland {code} was: {code}export GDK_BACKEND=x11 ./eclipse{code} > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23389: ----------------------------------------- OpenShift 3.4 has been added to the supported platform of FIS 2.0. Is is something that will be available in the next JBDSIS release? Is it planned? Is it possible? I'm aware that it is quite late to ask for it so if it is not possible, please tell me and we will need to document it on FIS support. > OpenShift 3.4 support > --------------------- > > Key: JBIDE-23389 > URL: https://issues.jboss.org/browse/JBIDE-23389 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.3.AM2 > > > OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it. > cc: [~adietish] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1015: --------------------------------- Assignee: Paul Leacu > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- created: [JBTIS-1015] > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Aurélien Pupier updated JBTIS-1015: ----------------------------------- Summary: Latest JBDSIS Target Platform cannot be used locally (was: Local Target Platform are no more working with latest JBDSIS Target Platform) > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Local Target Platform are no more working with latest JBDSIS Target Platform

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBTIS-1015: -------------------------------------- Summary: Local Target Platform are no more working with latest JBDSIS Target Platform Key: JBTIS-1015 URL: https://issues.jboss.org/browse/JBTIS-1015 Project: JBoss Tools Integration Stack Issue Type: Bug Components: target-platform Affects Versions: 4.4.1.CR2-TP Reporter: Aurélien Pupier Current state of understanding: There are 2 different bugs: * when using local "Directory": the jars which should be exploded in folder stay in jars ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? ** the implication is that we can't start a CDK server with such a TP * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) ** looks like a p2 bugs ** the implication is that the TP doesn't resolve at all If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1008: ----------------------------------- [~aurelien.pupier] - Hey Aurelien - I've released the 4.4.1.CR2 JBTIS TP with the missing openshift plugins. I plan on closing this Jira since it's original issue is resolved - can you open a new Jira on the Eclipse issue with the local TP? > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23668) Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23668?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23668: ------------------------------------ Comments on the PR. https://github.com/jbosstools/jbosstools-build/pull/240 > Move integration-tests parent pom configuration to jbosstools-build/parent/pom.xml > ---------------------------------------------------------------------------------- > > Key: JBIDE-23668 > URL: https://issues.jboss.org/browse/JBIDE-23668 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > > This configuration needs to be moved from [1] to build/parent/pom.xml > {code} > <properties> > <surefire.timeout>7200</surefire.timeout> > <integrationTestsSystemProperties>-Dusage_reporting_enabled=false</integrationTestsSystemProperties> > <devstudio.repository>https://devstudio.redhat.com/10.0/snapshots/updates/</devstudio.repository> > <testProduct>com.jboss.devstudio.core.product</testProduct> > </properties> > {code} > {code} > <profile> > <id>mac-installPath</id> > <activation> > <os> > <family>mac</family> > </os> > </activation> > <properties> > <test.installPath.OSX>/devstudio.app/Contents/Eclipse/</test.installPath.OSX> > </properties> > </profile> > <profile> > <id>install-base</id> > <activation> > <property> > <name>test.installBase</name> > </property> > </activation> > <properties> > <test.installPath>${test.installBase}${test.installPath.OSX}</test.installPath> > </properties> > <build> > <plugins> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-surefire-plugin</artifactId> > <configuration> > <work>${test.installPath}</work> > <product>${testProduct}</product> > </configuration> > </plugin> > </plugins> > </build> > </profile> > <profile> >  > <id>osx</id> > <activation> > <os> > <family>mac</family> > </os> > </activation> > <properties> > <platformSystemProperties> -XstartOnFirstThread </platformSystemProperties> > </properties> > </profile> > <profile> > <id>download-devstudio</id> > <activation> > <property> > <name>!test.installBase</name> > </property> > </activation> > <build> > <plugins> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-surefire-plugin</artifactId> > <configuration> > <product>${testProduct}</product> > </configuration> > </plugin> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>target-platform-configuration</artifactId> > <configuration> > <dependency-resolution> > <extraRequirements> > <requirement> > <type>p2-installable-unit</type> > <id>com.jboss.devstudio.core.feature.feature.group</id> > <versionRange>0.0.0</versionRange> > </requirement> > </extraRequirements> > </dependency-resolution> > </configuration> > </plugin> > </plugins> > </build> > <repositories> > <repository> > <id>devstudio-repo</id> > <name>devstudio-repo</name> > <layout>p2</layout> > <url>${devstudio.repository}</url> > </repository> > </repositories> > </profile> > {code} > {code} > <build> > <plugins> > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-surefire-plugin</artifactId> > <configuration> > <useUIThread>false</useUIThread> > <appArgLine>-pluginCustomization ${basedir}/../pluginCustomization.ini</appArgLine> > <systemProperties> > <org.eclipse.update.reconcile>false</org.eclipse.update.reconcile> >  > <tpc.version>${TARGET_PLATFORM_VERSION_MAX}</tpc.version> > </systemProperties> > <explodedBundles> > <bundle>org.mozilla.xulrunner.cocoa.macosx</bundle> > <bundle>org.mozilla.xulrunner.gtk.linux.x86</bundle> > <bundle>org.mozilla.xulrunner.gtk.linux.x86_64</bundle> > <bundle>org.mozilla.xulrunner.win32.win32.x86</bundle> > </explodedBundles> > </configuration> > </plugin> > </plugins> > </build> > {code} > We need to find out how to deal with pluginCustomization.ini [2]. Download from somewhere? > [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > [2] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017