June 2018 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------------ [~ksuzumur] please allow one more question: if the customer isn't using the Eclipse tooling currently, can you tell us how they proceed currently? (Insights would allow us to plan further features). > 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 > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ] Bob Davis commented on JBDS-4706: --------------------------------- I think we need to grab these images up together and start a separate ticket to address naming of the middleware products in Central. The middleware team should be involved, since this is their product set. [~kcbabo] should be involved on the Fuse side, as I believe they've already removed "JBoss" from the name there. As for the EULA, we'll need help from legal - [~fontana], can you assist with the right people to engage? Should the name on the EULA (cited a couple comments above) change to reflect the product name changes? > 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: build, 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, devstudio12-central.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

1
0
0 / 0

[JBoss JIRA] (JBIDE-26098) Repair org.jboss.tools.stacks test failures in jbosstools_base-master job

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26098: ------------------------------------- Summary: Repair org.jboss.tools.stacks test failures in jbosstools_base-master job Key: JBIDE-26098 URL: https://issues.jboss.org/browse/JBIDE-26098 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: qa Affects Versions: 4.6.0.Final Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.6.0.Final org.jboss.tools.stacks needs to bump up a version while updating plugins to run all tests. Have tests to be run on jenkins jbt-base master and pull request job and have green. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25207: ---------------------------------- Summary: Integration Tests: PortForwardingTest (was: Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges) > Integration Tests: PortForwardingTest > ------------------------------------- > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[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 resolved JBIDE-26038. -------------------------------- Resolution: Done Central updated in AM3, but needs verification that this change fixes the issue seen by customer. Resolving for now. > [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

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25597: ------------------------------------ Respinning now to pick up m2e 1.8.3 (for compatibility with nodeclipse - JBIDE-26065): https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM3, 4.6.0.Final > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1231) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1231: --------------------------------- Summary: Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text Key: JBTIS-1231 URL: https://issues.jboss.org/browse/JBTIS-1231 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 12.0.0.CR1 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 12.0.0.GA IS version of https://issues.jboss.org/browse/JBDS-4706 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25615) Update test cases for server in Polarion

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25615?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25615. --------------------------------- Closing - tests are updated. > Update test cases for server in Polarion > ---------------------------------------- > > Key: JBIDE-25615 > URL: https://issues.jboss.org/browse/JBIDE-25615 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.5.2.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.0.AM3 > > > Add latest EAP and WildFly, remove servers with expired support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25207: ---------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) > Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges > ------------------------------------------------------------------------------------ > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-25207: ------------------------------------- Assignee: Josef Kopriva > Integration Tests: PortForwardingTest, Win10: Eclipse is missing required privileges > ------------------------------------------------------------------------------------ > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 June 2018