October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23285: ---------------------------------------- We are not removing old Server Adapters. But if it helps to disable/remove slow integration tests for ancient servers which officially are not supported anymore then we can do it IMO. What is the time difference? What disk space we are talking about? Do we have any disk space issues? > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23289) ServerProfileModel.getController fails to find publish controller for wf10 [aeri]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23289?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23289: -------------------------------------- Assignee: Rob Stryker > ServerProfileModel.getController fails to find publish controller for wf10 [aeri] > --------------------------------------------------------------------------------- > > Key: JBIDE-23289 > URL: https://issues.jboss.org/browse/JBIDE-23289 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > > I hesitated to make a bug report here. On the one hand, this is simply a log message, and the environment still has a chance to recover. > However, it does seem extremely strange that the publish subsystem is not being found for wf10. Our unit tests indicate it is found. The fact that this is still being replicated in astools 3.2.x is puzzling to me. But I simply cannot imagine what environment is causing this. Subsystem and profile mappings are done in the same plugin the subsystems are declared for the most part. > The following problem was reported via the automated error reporting: > Message: No subsystem found for servertype org.jboss.ide.eclipse.as.wildfly.100 and system type publish > {noformat} > com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted. > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel.getController(ServerProfileModel.java:187) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ProfileServerBehavior.getController(ProfileServerBehavior.java:59) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.getPublishController(CachedPublisherProfileBehavior.java:35) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297) > at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218) > at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231) > at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139) > at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73) > at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:273) > at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367) > at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349) > at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372) > at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | > | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 | > | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | > | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 | > | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 | > | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 | > | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.2.1.v20160711-1757 | > Operating Systems: > | Linux | 3.10.0.28 | 4.6.7.fc24 | > | MacOSX | 10.10.5 | 10.12.0 | > | Windows | 5.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56f024b6e4b08ccb7b...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23291: -------------------------------------- Assignee: Rob Stryker > If start of container fails on timeout, the status in server view is "Started, Synchronized" > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23291 > URL: https://issues.jboss.org/browse/JBIDE-23291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23291: ---------------------------------------- Is this devstudio 10.1 / JBoss tools 4.4.1? > If start of container fails on timeout, the status in server view is "Started, Synchronized" > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23291 > URL: https://issues.jboss.org/browse/JBIDE-23291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Aurélien Pupier > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23294: -------------------------------------- Assignee: Rob Stryker > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23294 > URL: https://issues.jboss.org/browse/JBIDE-23294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23294: ----------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-23294 (was: JBDS-4086) Docs QE Status: (was: NEW) Component/s: cdk server (was: server) (was: cdk) Affects Version/s: 4.4.1.Final (was: 10.1.0.GA) > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23294 > URL: https://issues.jboss.org/browse/JBIDE-23294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23290?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23290: ------------------------------------ I believe the problem here is that I forgot to bump the version after releasing the AM1 bits. Solution: https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/0ce86095c7fb8fe6... https://github.com/jbosstools/jbosstools-build/commit/ace5f7a8ff4e7320eb8... > Move parent pom to AM2 > ---------------------- > > Key: JBIDE-23290 > URL: https://issues.jboss.org/browse/JBIDE-23290 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > > Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no? > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23290?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23290: ------------------------------- Fix Version/s: 4.4.2.AM2 > Move parent pom to AM2 > ---------------------- > > Key: JBIDE-23290 > URL: https://issues.jboss.org/browse/JBIDE-23290 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > > Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no? > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23290) Move parent pom to AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23290?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23290. ------------------------------ Resolution: Done > Move parent pom to AM2 > ---------------------- > > Key: JBIDE-23290 > URL: https://issues.jboss.org/browse/JBIDE-23290 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > > Parent pom [1] and hence all the builds still show AM1, but we're already one week into sprint 121 = AM2. I could just create a PR for the change. But I wonder what happened. Anything went wrong? This change is supposed to be part of the release process after each sprint, no? > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4088) Stop building the devstudio src.zip as it is now replaced by a link to github

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4088?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4088: ---------------------------------- disable creation and processing of the sources zip entirely; tweak instructions to point users to github > Stop building the devstudio src.zip as it is now replaced by a link to github > ----------------------------------------------------------------------------- > > Key: JBDS-4088 > URL: https://issues.jboss.org/browse/JBDS-4088 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build > Affects Versions: 10.2.0.AM1 > Reporter: Nick Boldt > > Per https://trello.com/c/OhNmvELX/4-remove-jbds-sources-zip-from-list-of-deli... it's time to stop building the devstudio src.zip entirely, so it won't be included in the deliverables on developers.redhat.com and in the CSP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 October 2016