[JBoss JIRA] (JBIDE-26034) test failures in archives.ui.bot.*
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26034?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26034:
------------------------------------
Down to one failure:
org.jboss.ide.eclipse.archives.ui.test.bot.ArchiveViewReSwitchingTest no-configuration.org.jboss.ide.eclipse.archives.ui.test.bot.ArchiveViewReSwitchingTest no-configuration
-- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> test failures in archives.ui.bot.*
> ----------------------------------
>
> Key: JBIDE-26034
> URL: https://issues.jboss.org/browse/JBIDE-26034
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives, server
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> 9 tests have been failing for 25 builds:
> {code}
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testCreatingFolder no-configuration 2.4 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testModifyingFolder no-configuration 2.7 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testCreatingFileset no-configuration 2.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testModifyingFileset no-configuration 3 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testDeletingFileset no-configuration 2.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.UserLibrariesFilesetTest.testCreatingUserLibraryFileset no-configuration 1.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.CreatingArchiveTest.testCreatingArchiveWithExplorer no-configuration 0.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest.testDeletingArchiveWithExplorer no-configuration 1 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest.testModifyingArchiveWithExplorer no-configuration 1 sec 25
> {code}
> These 3 failures are newer:
> {code}
> org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveTest.testBuildingArchiveWithView no-configuration 0.75 sec 1
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testDeletingFolder no-configuration 3.4 sec 2
> org.jboss.ide.eclipse.archives.ui.test.bot.BuildingProjectTest.testBuildingProjectWithExplorer no-configuration 0.66 sec 12
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25916:
------------------------------------------
Couldn't reproduce this in several attempts so far.
Currently engint seems defunct, no build is started. If you try to start it manually, it'll complain about a missing "builder" serviceaccount.
> OpenShift Server Adapter: Error in Log after "Restart in Debug"
> ---------------------------------------------------------------
>
> Key: JBIDE-25916
> URL: https://issues.jboss.org/browse/JBIDE-25916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.Final
> Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: debugging, server_adapter
> Fix For: 4.6.0.AM3
>
> Attachments: error-launching-server.png
>
>
> An error occurs when restarting server adapter in debug:
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Warning
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy
> {code}
> {code:java}
> eclipse.buildId=11.3.0.GA-v20180410-1152-B2341
> java.version=1.8.0_162
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Apr 11 18:09:03 CEST 2018
> Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war
> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3]
> error: exit status 23
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by James Cobb (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
James Cobb commented on JBDS-4706:
----------------------------------
[~nickboldt] -
I just saw your two installer attachments. "JBoss by Red Hat" is a dead tagline so it should be removed. It's my understanding that "Red Hat JBoss Middleware" is still a thing (for the time being). The formal logotype has "Red Hat® JBoss® Middleware" since this is several steps into the process, do we still need the ® in the written out form?
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.0.0.AM3
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22138:
-------------------------------------
Fix Version/s: 4.6.x
(was: 4.6.0.AM3)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22138:
------------------------------------------
postponed from 4.6.0.AM3, went out of time for this.
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse & older SVNKit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26038:
-------------------------------
Summary: [Red Hat Central] Update to latest Subclipse & older SVNKit (was: [Red Hat Central] Update to latest Subclipse)
> [Red Hat Central] Update to latest Subclipse & older SVNKit
> -----------------------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> http://post-office.corp.redhat.com/archives/sme-jbds/2018-May/msg00004.html
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1229?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1229:
-----------------------------------
[~blafond] - Hey Barry - please try building TD using the JBTIS TP 4.6.0.AM1-SNAPSHOT so we can identify any missing dependencies.
Thanks!
> Cannot install Teiid Designer into Devstudio 12.0.0
> ---------------------------------------------------
>
> Key: JBTIS-1229
> URL: https://issues.jboss.org/browse/JBTIS-1229
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: teiid
> Affects Versions: 4.6.0.CR1
> Environment: Red Hat Developer Studio
> Version: 12.0.0.AM3
> Build id: AM3-v20180605-1618-B2654
> OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from
> https://devstudio.redhat.com/12/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457)
> To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months