December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18274: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname > ------------------------------------------------------------------------------- > > Key: JBIDE-18274 > URL: https://issues.jboss.org/browse/JBIDE-18274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.0.AM1 > > Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png > > > This is a follow up of JBIDE-17935 . > Previously, Rob fixed this: > {quote} > I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here. > {quote} > But in this rare case it still fails for me. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-18131: ------------------------------------ [~rob.stryker] I remember you did some work about core and ui, bit is this about this module > Split the org.jboss.tools.common.validation plugin in 'core' + 'ui' > ------------------------------------------------------------------- > > Key: JBIDE-18131 > URL: https://issues.jboss.org/browse/JBIDE-18131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > > IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}: > - the {{core}} part would deal with performing the validation (based on the WST Validation Framework) > - the {{ui}} part would deal for the preference pages and configuration. > ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong. > OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.) > Can we discuss about that change for JBoss Tools 4.3 ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18131: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.3.x) > Split the org.jboss.tools.common.validation plugin in 'core' + 'ui' > ------------------------------------------------------------------- > > Key: JBIDE-18131 > URL: https://issues.jboss.org/browse/JBIDE-18131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Alexey Kazakov > Fix For: 4.5.0.AM1 > > > IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}: > - the {{core}} part would deal with performing the validation (based on the WST Validation Framework) > - the {{ui}} part would deal for the preference pages and configuration. > ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong. > OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.) > Can we discuss about that change for JBoss Tools 4.3 ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18098) many "Unknown" markers during maven import

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18098?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18098: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > many "Unknown" markers during maven import > ------------------------------------------ > > Key: JBIDE-18098 > URL: https://issues.jboss.org/browse/JBIDE-18098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.5.0.AM1 > > > not sure if this is a maven or eclipse issue but when importing javaee7-samples the problem view lists *alot* of unknown markers. > example: https://www.dropbox.com/s/63n9f1kxn9ubrg7/Screenshot%202014-08-20%2012.49... > Eventually they dissapear, but they are there for several minutes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18099) Configure Maven Repositories quickfix shows up on unrelated quickfixes

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18099?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18099: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Configure Maven Repositories quickfix shows up on unrelated quickfixes > ---------------------------------------------------------------------- > > Key: JBIDE-18099 > URL: https://issues.jboss.org/browse/JBIDE-18099 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.5.0.AM1 > > > I have a project where the groupid is the same as parent in many projects (i.e. javaee7-samples) > I get about 50 warnings about this and want to use the quickfix to remove this line. > I can't because our "Configure Maven Repositories" thinks it is a relevant fix for this issue. > Can we make it so it wont show up unless it is relevant ? > Screenshot: https://www.dropbox.com/s/dmo1a7x1em7qq06/Screenshot%202014-08-20%2012.51... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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.5.0.AM1 (was: 4.3.x) (was: 4.4.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.5.0.AM1 > > > 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.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18096) could not complete update project configuration - illegalargumentexception

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18096: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > could not complete update project configuration - illegalargumentexception > -------------------------------------------------------------------------- > > Key: JBIDE-18096 > URL: https://issues.jboss.org/browse/JBIDE-18096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Labels: f2f2014 > Fix For: 4.5.0.AM1 > > > while trying to fix import of javaee-samples I bumped into this happening when running update project configuration. > java.lang.IllegalArgumentException > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) > at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150) > at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93) > at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70) > at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318) > at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > It happened on ~100 projects so was quite invasive ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18097) Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18097?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18097: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Update project configuration is not enough to update eclipse settings - need to delete .project/.classpath and reimport > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18097 > URL: https://issues.jboss.org/browse/JBIDE-18097 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.5.0.AM1 > > > I'm finding this more and more worrisome so wanted to record it. > When trying to fix JBDS-2847 or rather fix javee7-samples to be able to import easily we easily end up with a set of projects where settings are wrong. > I updated the parent pom to not have the groovy compiler enabled and ran update project configuration - and the changes regarding source paths did not take effect. > Only way to fix was to nuke all files and reimport. > can this be true ? no way to "force" an update ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17858) Can't resolve context variable of a built-in Seam component in imported Seam project

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17858?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-17858: ------------------------------- Fix Version/s: LATER (was: 4.3.x) > Can't resolve context variable of a built-in Seam component in imported Seam project > ------------------------------------------------------------------------------------ > > Key: JBIDE-17858 > URL: https://issues.jboss.org/browse/JBIDE-17858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, seam2, upstream > Environment: JBDS 8.0.0.Beta3 > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: LATER > > > Unknown context variable name: "topicPublisher" > ChatRoomAction.java > /chatroom-ejb/src/main/java/org/jboss/seam/example/remoting/chatroom > line 26 > Seam Problem -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3089) x509 Authentication to OpenShift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-3089?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-3089: ----------------------------- Fix Version/s: LATER (was: 9.x) > x509 Authentication to OpenShift > -------------------------------- > > Key: JBDS-3089 > URL: https://issues.jboss.org/browse/JBDS-3089 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Eric Rich > Assignee: Alexey Kazakov > Labels: authentication, ssl > Fix For: LATER > > > Currently customers are asking for RHC to support x509 Authentication with the broker service (https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of JBDS -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016