December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23641: --------------------------------------- I installed latest STS (3.8.2.RELEASE) on latest macOS Sierra, then I started it and installed Java EE Development -> JBoss AS Tools from the JBoss Tools 4.4.2 update site: http://download.jboss.org/jbosstools/neon/stable/updates/ Then I restarted the IDE. I did not see any freeze. Then I installed mylyn from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.7 . I restarted the IDE and still no freeze. > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM1 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23587) Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23587?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23587: ------------------------------------- Description: Maven command from CLI: {code} mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false {code} Launching in Eclipse needs the following parameters: {code} -Dusage_reporting_enabled=false -Drd.config=resources/servers -Djbosstools.test.seam.2.1.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.1.2 -Djbosstools.test.seam.2.3.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.3.0.CR1 -Djbosstools.test.seam.2.2.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.2.0.GA -Djbosstools.test.wildfly8.home=/home/dbocharo/wildfly-8.2.1.Final -Dmaven.settings.path=/home/dbocharo/dev/openshift/jbosstools-integration-tests/tests/org.jboss.tools.maven.ui.bot.test/target/classes/usersettings/settings.xml {code} Corresponding directories must contain Seam and Wildfly was: Maven command: {code} mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false {code} > Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23587 > URL: https://issues.jboss.org/browse/JBIDE-23587 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: integration, integration_tests, maven > Fix For: 4.4.3.AM1 > > > Maven command from CLI: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false > {code} > Launching in Eclipse needs the following parameters: > {code} > -Dusage_reporting_enabled=false -Drd.config=resources/servers -Djbosstools.test.seam.2.1.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.1.2 -Djbosstools.test.seam.2.3.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.3.0.CR1 -Djbosstools.test.seam.2.2.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.2.0.GA -Djbosstools.test.wildfly8.home=/home/dbocharo/wildfly-8.2.1.Final -Dmaven.settings.path=/home/dbocharo/dev/openshift/jbosstools-integration-tests/tests/org.jboss.tools.maven.ui.bot.test/target/classes/usersettings/settings.xml > {code} > Corresponding directories must contain Seam and Wildfly -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4221) User can install JBDS from market without acceptation license agreements

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4221?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4221: ------------------------------------ Deletion of ~/.eclipse directory didn't solve my problem. This problem occurs also on clean virtual machine on the very first installation of eclipse. > User can install JBDS from market without acceptation license agreements > ------------------------------------------------------------------------ > > Key: JBDS-4221 > URL: https://issues.jboss.org/browse/JBDS-4221 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.2.0.GA > Environment: Fedora 24, openjdk 1.8.0_102 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.3.0.AM1 > > Attachments: Install_JBDS_from_marketplace.png > > > User can install Developer Studio from eclipse marketplace without acceptation terms of the licence agreements. > Step to reproduce: > # Download, unpack and start Eclipse Neon 1 > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... > # Market -> Search form "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install > # The window "Review Licenses" looks like on screenshot !Install_JBDS_from_marketplace.png|thumbnail! > # Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install JBDS. > When I check "I accept" radio button and then switch back to "I do not accept" it start works correctly. > This problem doesn't occur when installing JBoss Tools. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23638) Scaling: Sometimes incorrect version of RC leads to error when scaling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23638?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23638: --------------------------------------- Yeah, refresh usually works. > Scaling: Sometimes incorrect version of RC leads to error when scaling > ---------------------------------------------------------------------- > > Key: JBIDE-23638 > URL: https://issues.jboss.org/browse/JBIDE-23638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > > Sometimes when scaling an OpenShift 3 application several times, there is an error about failed PUT call. No jobs are running when triggering a scaling. Even though pods are shown correctly (right amount is shown) this error is shown: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/test-project/replicationcontrolle... response code: 409 Operation cannot be fulfilled on replicationcontrollers "nodejs-example-1": the object has been modified; please apply your changes to the latest version and try again > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:155) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1003: ----------------------------------- [~apodhrad] - please try this: http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.1.CR... https://origin-repository.jboss.org/nexus/content/repositories/snapshots/... > Add id to all repositories defined in target platform > ----------------------------------------------------- > > Key: JBTIS-1003 > URL: https://issues.jboss.org/browse/JBTIS-1003 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, the definition looks as follows > {code:title=src/targets/integration-stack-base.target} > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> > ... > <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> > </location> > {code} > Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. > {code} > http://download.jboss.org/jbosstools/updates/requirements/neon/ > {code} > I think that the composite site should work without any problem since all needed versions are specified in each unit. > Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1004) Integration Stack Installation Guide peer review

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1004?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1004: --------------------------------- Assignee: Misha Ali (was: Paul Leacu) > Integration Stack Installation Guide peer review > ------------------------------------------------ > > Key: JBTIS-1004 > URL: https://issues.jboss.org/browse/JBTIS-1004 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, testing > Reporter: Gemma Sheldon > Assignee: Misha Ali > Priority: Minor > Fix For: 10.0.0.GA > > > General peer review stuff from the JBDIS Installation Guide. > *Chapter 2:* > - Oxford comma after "architecture" in the first para. > *Chapter 4:* > - "At the Select Additional Features to Install screen, select the required components: " > This could be "Select the required components from the Select Additional Features to Install screen"? > - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. " > When complete? Once installed? > - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. " > Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe: > The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect. > *Chapter 6* > - The sub-steps here could use a full stop based on the IBM style guide pp84-85. > - Same Warning as in previous chapter > *Chapter 7* > - Same point about the sub-steps and full stops. Some have them here, some don't. > - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal" > *Chapter 8* > - Several steps throughout the procedure are missing full stops at the end. > - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step. > - Same as above with Step 6, which is also missing the opening bracket. > - Same Warning as in Chapters 5 and 6. > - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects." > This statement also appears in Chapter 6. > *Chapter 9* > - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint." > 2x continued here. Could be "... provides continued stability and ensures optimal performance..." > - " in an efficient manner" --> efficiently. > - full stops at the end of the bullet points. > - substeps of step 4 are missing full stops. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23497) Integration tests: StoreConnectionTest isnt working

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23497?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23497: ------------------------------------------ merged into jbosstools-integration-tests/master. QE verified the PR, closing. > Integration tests: StoreConnectionTest isnt working > --------------------------------------------------- > > Key: JBIDE-23497 > URL: https://issues.jboss.org/browse/JBIDE-23497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM1 > > > StoreConnectionTest isnt working. There are a few problems with it: > * It can trigger the ssl certificate dialog if it's the test is the 1st test that is run against the given connection (and the certificate wasnt stored beforehand). The test wont take this possibility into account > * The test isnt autonoumous, it relies on a connection being set up beforehand > * etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23497) Integration tests: StoreConnectionTest isnt working

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23497?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-23497. ------------------------------------ > Integration tests: StoreConnectionTest isnt working > --------------------------------------------------- > > Key: JBIDE-23497 > URL: https://issues.jboss.org/browse/JBIDE-23497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM1 > > > StoreConnectionTest isnt working. There are a few problems with it: > * It can trigger the ssl certificate dialog if it's the test is the 1st test that is run against the given connection (and the certificate wasnt stored beforehand). The test wont take this possibility into account > * The test isnt autonoumous, it relies on a connection being set up beforehand > * etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3439) Unable to add a new Forge Runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBDS-3439?page=com.atlassian.jira.plugin.... ] Koen Aers resolved JBDS-3439. ----------------------------- Resolution: Rejected The reasons for the rejection are explained in the first comment. > Unable to add a new Forge Runtime > --------------------------------- > > Key: JBDS-3439 > URL: https://issues.jboss.org/browse/JBDS-3439 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Quality Risk > Components: forge > Affects Versions: 8.0.0.GA, 8.1.0.GA > Environment: Fedora 20, jdk1.7.0_67, JBoss Developer Studio 8+ > Reporter: Miguel Angel Morales Pedraza > Assignee: Koen Aers > Priority: Optional > Labels: forge, runtime > Fix For: 8.x > > > Unable to add a new Forge runtime on JBDS 8.0.0 and 8.1.0. The button "Add" it doesn't shown anymore. > On the JBDS v7.1.1 this button appears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3439) Unable to add a new Forge Runtime

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBDS-3439?page=com.atlassian.jira.plugin.... ] Koen Aers reassigned JBDS-3439: ------------------------------- Assignee: Koen Aers (was: Jeff MAURY) > Unable to add a new Forge Runtime > --------------------------------- > > Key: JBDS-3439 > URL: https://issues.jboss.org/browse/JBDS-3439 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Quality Risk > Components: forge > Affects Versions: 8.0.0.GA, 8.1.0.GA > Environment: Fedora 20, jdk1.7.0_67, JBoss Developer Studio 8+ > Reporter: Miguel Angel Morales Pedraza > Assignee: Koen Aers > Priority: Optional > Labels: forge, runtime > Fix For: 8.x > > > Unable to add a new Forge runtime on JBDS 8.0.0 and 8.1.0. The button "Add" it doesn't shown anymore. > On the JBDS v7.1.1 this button appears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016