May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1223) Update BPEL to 1.1.2 (Photon)

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1223: --------------------------------- Summary: Update BPEL to 1.1.2 (Photon) Key: JBTIS-1223 URL: https://issues.jboss.org/browse/JBTIS-1223 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPEL Affects Versions: 12.0.0.AM1-TP Reporter: Paul Leacu Assignee: Paul Leacu Update BPEL to 1.1.2 (Photon) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime

by Marco Del Percio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26016?page=com.atlassian.jira.plugi... ] Marco Del Percio commented on JBIDE-26016: ------------------------------------------ Thanks Rob > javax.websocket is missing from default classpath entries of WildFly 12 Runtime > ------------------------------------------------------------------------------- > > Key: JBIDE-26016 > URL: https://issues.jboss.org/browse/JBIDE-26016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.Final > Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final > Reporter: Marco Del Percio > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.6.0.AM2 > > Attachments: javax.websocket.missing.png > > > When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket. > The workaround is to manually amend the default classpath entries for that runtime and add the missing module. > javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26016?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26016. --------------------------------- Resolution: Done squashed and merged > javax.websocket is missing from default classpath entries of WildFly 12 Runtime > ------------------------------------------------------------------------------- > > Key: JBIDE-26016 > URL: https://issues.jboss.org/browse/JBIDE-26016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.3.Final > Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final > Reporter: Marco Del Percio > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.6.0.AM2 > > Attachments: javax.websocket.missing.png > > > When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket. > The workaround is to manually amend the default classpath entries for that runtime and add the missing module. > javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25922) Runtime detection finds new cdk even if it already exists

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25922?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25922: ------------------------------------- https://github.com/jbosstools/jbosstools-openshift/pull/1741 was pushed > Runtime detection finds new cdk even if it already exists > --------------------------------------------------------- > > Key: JBIDE-25922 > URL: https://issues.jboss.org/browse/JBIDE-25922 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.0.AM2 > > > I just noticed that sometimes if you repeatedly search for runtimes, the same cdk binary will be recognised as new again and again, creating duplicate server adapters if you click OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25971: -------------------------------- Fix Version/s: 4.6.0.AM2 (was: 4.6.x) > Add Red Hat Developers sign up link to CDK New Server wizard > ------------------------------------------------------------ > > Key: JBIDE-25971 > URL: https://issues.jboss.org/browse/JBIDE-25971 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.5.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: cdk_server_adapter_wizard > Fix For: 4.6.0.AM2 > > Attachments: new-server-cdk.png > > > While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow. > Imagine you don't have an account on developers.redhat.com yet. > You go to New Server -> CDK 3.2+. > On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome. > So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials. > That's issue 1. > !new-server-cdk.png! > There are also a few side issues: > 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough. > 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title? > 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-25974. --------------------------------- Resolution: Done I'm marking this as resolved, but please test it with the patch in https://issues.jboss.org/browse/JBIDE-25968 applied. I pushed that one to master so you should be able to test it tomorrow. > CDK 3.4 runtime detection failing > --------------------------------- > > Key: JBIDE-25974 > URL: https://issues.jboss.org/browse/JBIDE-25974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.0.AM1 > > Attachments: image-2018-05-07-17-59-59-316.png > > > Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better > steps: > # EXE: Preferences > JBoss Runtime Detection > Download > # ASSERT: List of available runtimes shows up, containing CDK 3.4.0 > # EXEC: Choose "CDK 3.4.0" & hit "Next" > # EXEC: next page: provide credentials & hit "Next" > # EXEC: next page: accept the terms & hit "Next" > # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish" > # ASSERT: wait for the download to finish > Result: > The download wont detect the new CDK 3.4.0 that you just downloaded > !image-2018-05-07-17-59-59-316.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1222) Target platform Photon initial build (12.0.0.AM1)

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1222: --------------------------------- Summary: Target platform Photon initial build (12.0.0.AM1) Key: JBTIS-1222 URL: https://issues.jboss.org/browse/JBTIS-1222 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 12.0.0.CR1-TP, 4.6.0.CR1-TP Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 12.0.0.CR1-TP, 4.6.0.CR1-TP *Reason:* Initial Photon support - sync w/ Eclipse 4.7.0.M6 Oxygen.0.M6 via JBT 4.6.0.AM1 *Project page/sources:* *Version:* 4.6.0.AM1 *License and owner:* EPL *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* DevstudioIS *Include in JBDS:* Yes DevstudioIS *Type of dependency:* testing|central-only|distribution *List of bundles added/removed:* {code} {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 edited comment on JBIDE-25615 at 5/22/18 9:33 AM: ---------------------------------------------------------------- Update: we have selected servers(added WF12, removed all before WF_821, but I will select one server with old directory layout), now I am working on stabilization of ITests on Jenkins. was (Author: jkopriva): Update: we have selected servers, now I am working on stabilization of ITests on Jenkins. > 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.x > > > Add latest EAP and WildFly, remove servers with expired support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 commented on JBIDE-25615: --------------------------------------- Update: we have selected servers, now I am working on stabilization of ITests on Jenkins. > 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.x > > > Add latest EAP and WildFly, remove servers with expired support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4702) Multiple warnings when opening Spring perspective

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4702?page=com.atlassian.jira.plugin.... ] Josef Kopriva commented on JBDS-4702: ------------------------------------- [~nickboldt] Maybe we should update Spring IDE version? Please see comment in upstream issue. > Multiple warnings when opening Spring perspective > ------------------------------------------------- > > Key: JBDS-4702 > URL: https://issues.jboss.org/browse/JBDS-4702 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-certification, central-update, upstream > Affects Versions: 12.0.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Optional > Fix For: 12.x > > > {code:java} > eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428 > java.version=1.8.0_171 > 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_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.ui > Warning > Wed May 09 11:50:19 CEST 2018 > org.eclipse.contribution.xref.ui.views.XReferenceView: Deprecated relationship "fast" should be converted to "stack". > {code} > {code:java} > eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428 > java.version=1.8.0_171 > 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_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.ui > Warning > Wed May 09 11:50:19 CEST 2018 > org.springframework.ide.eclipse.aop.ui.navigator.aopReferenceModelNavigator: Deprecated relationship "fast" should be converted to "stack". > {code} > {code:java} > eclipse.buildId=12.0.0.AM1-v20180508-1631-B2428 > java.version=1.8.0_171 > 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_B2428_3/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.ui > Warning > Wed May 09 11:50:19 CEST 2018 > org.eclipse.jdt.junit.ResultView: Deprecated relationship "fast" should be converted to "stack". > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 May 2018