April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19329) Start Forge2 runtime when workbench starts

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19329?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19329: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Start Forge2 runtime when workbench starts > ------------------------------------------ > > Key: JBIDE-19329 > URL: https://issues.jboss.org/browse/JBIDE-19329 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.3.0.Alpha1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.6.x > > > With removal of Forge1 some of the preferences related to Forge1 are gone. For example, Start Forge when workbench starts, or start in Debug mode. > Some of them make sense and come handy also for Forge2. > It would be good to bring back the start option for F2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24441) Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24441?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24441: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24441 > URL: https://issues.jboss.org/browse/JBIDE-24441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.6.x > > Attachments: image-2017-05-15-11-26-27-131.png, image-2017-05-15-11-31-02-611.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21924) Various broken icons in menus on OS X

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21924?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21924: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Various broken icons in menus on OS X > ------------------------------------- > > Key: JBIDE-21924 > URL: https://issues.jboss.org/browse/JBIDE-21924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Fix For: 4.6.x > > Attachments: broken-icons.png > > > For some time now I've had problems with icons disappearing or just being malformed in Eclipse IDE. I thought it was connected to the fact that I was running JBDS using cli which is not the right way (I did this to overcome an issue where cdk was missing PATH). > But now I'm running JBDS normally and I still have this issue. I'm mostly using Oracle JDK 1.8 > !broken-icons.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24759) JMX Monitor: If you collapse nodes and reset connection, nodes will expand again

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24759?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24759: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JMX Monitor: If you collapse nodes and reset connection, nodes will expand again > -------------------------------------------------------------------------------- > > Key: JBIDE-24759 > URL: https://issues.jboss.org/browse/JBIDE-24759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.x > > > when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8849) JPA project revalidation after export to db

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8849?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-8849: ------------------------------ Fix Version/s: 4.6.x (was: 4.5.x) > JPA project revalidation after export to db > ------------------------------------------- > > Key: JBIDE-8849 > URL: https://issues.jboss.org/browse/JBIDE-8849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate, upstream > Affects Versions: 3.2.1.M1 > Environment: JBDS 4.1.0 m1 H359 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: jpa > Fix For: 4.6.x > > > 1. Create datasource and open it > 2. Let's have JPA Project referenced datasource from step above > 3. Create entity M with table name Z, you'll get Table "Z" cannot be resolved > 4. Project -> JPA Tools -> Generate Tables from Entities with "Check Export to database" selected > 5. Finish > After doing this project entity is not yet valid > It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20983) cannot use oracle service name in datasource creation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20983?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20983: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > cannot use oracle service name in datasource creation > ----------------------------------------------------- > > Key: JBIDE-20983 > URL: https://issues.jboss.org/browse/JBIDE-20983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.2.Final > Reporter: Tom Fonteyne > Assignee: Koen Aers > Fix For: 4.6.x > > > When connecting to an Oracle data source, a SID is required for a connection and a service name can not be used. > The Oracle URL formats are: > With a SID you use ":sid" at the end > jdbc:oracle:thin:@//oraclehost:1521:mysid > with a service name you use "/myservicename" > jdbc:oracle:thin:@//oraclehost:1521/myservicename > The dialog box prevent removing the ":" and replacing it with the needed "/" > (not even via the driver definition where you seem to be allowed to set the url format...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23279: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.6.x > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19593?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19593: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Minor UI issues in "Configure Repositories" wizard on OSX > --------------------------------------------------------- > > Key: JBIDE-19593 > URL: https://issues.jboss.org/browse/JBIDE-19593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Fred Bricon > Priority: Minor > Labels: uxp > Fix For: 4.6.x > > > On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... > * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels. > This was fixed for Windows/Linux in 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24292) Integration Tests: It should be possible to retrieve build log from pod in error state.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24292?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24292: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration Tests: It should be possible to retrieve build log from pod in error state. > --------------------------------------------------------------------------------------- > > Key: JBIDE-24292 > URL: https://issues.jboss.org/browse/JBIDE-24292 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, openshift > Affects Versions: 4.4.4.AM3 > Reporter: Radim Hopp > Assignee: Josef Kopriva > Fix For: 4.6.x > > > When Build ends in error, it should still be possible to retrieve build log from the failed pod. > Reference jira: JBIDE-23708 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18113) Wrong 'dirty regions' values passed to the 'as-you-type' validator

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18113?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18113: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Wrong 'dirty regions' values passed to the 'as-you-type' validator > ------------------------------------------------------------------ > > Key: JBIDE-18113 > URL: https://issues.jboss.org/browse/JBIDE-18113 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Victor Rubezhny > Fix For: 4.6.x > > > The as-you-type validator received an array of dirty regions that can be wrong when the region contains a String. > Steps to reproduce: > - grab the latest changes in jbosstools-webservices repo > - start a runtime workbench > - create a new dynamic web project targeting Wildfly 8.x (the example below uses JAX-RS 2.0 APIs) > - add support for JAX-RS > - create a class with the following content: > {code} > package jaxrs; > import java.io.IOException; > import javax.ws.rs.GET; > import javax.ws.rs.Path; > import javax.ws.rs.PathParam; > import javax.ws.rs.container.ContainerRequestContext; > import javax.ws.rs.container.ContainerResponseContext; > import javax.ws.rs.container.ContainerResponseFilter; > import javax.ws.rs.core.Response; > import javax.ws.rs.ext.Provider; > @Path("/") > public class RestService { > > @GET > @Path("/{ide}") > public Response get(@PathParam("ide") String id) { > System.out.println("Just passed in method"); > return Response.ok().build(); > } > > @Provider > public static class AuthorizedResponseFilter implements ContainerResponseFilter { > @Override > public void filter(ContainerRequestContext arg0, > ContainerResponseContext arg1) throws IOException { > System.out.println("Just passed in filter"); > } > } > } > {code} > - In your development workspace, open {{org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator}} and put a breakpoint on line 441 > - Back in the runtime workspace, remove the @Provider annotation and see the value for 'dirtyRegion'. In my last test, this one alone looked good (offset=559) > - DO NOT SAVE THE FILE > - remove the @Path("/") annotation on the RestService type, this time you should have *4* dirty regions, with unexpected values (ie, pointing at other locations in the document). > As [~akazakov] commented in a private mail: > {quote} > JaxrsMetamodelValidator implements IJavaElementValidator and IStringValidator. > When you remove @Provider then you get the region with offset of the removed JavaElement because you validator implements IJavaElementValidator. > This interface tells our validation manager that the validator is interested in validating of changes in java elements. > When you remove @Path("/") you also remove a string ("/") and since your validator implements IStringValidator this validator is notified and you got a list of the regions of all the strings of the file: 4 regions in your case. > The problem is that you also should have been notified about removed java element because this annotation is not just a String. It's also a java element. That looks like a bug for me. > So if you remove any code with a string inside then you will get a list of strings of the file (but only if you implements IStringValidator). > If you don't implement IStringValidator and remove any java element which contains a string you won't be notified at all. This is a bug. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018