January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19116: ------------------------------------ Only one I can find is JBIDE-18765 but that's about refactoring the code, not he jobs. > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19114) Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [Server]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19114?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19114: ----------------------------------- Summary: Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [Server] (was: Upversion plugins + features for JBT 4.2.3 / JBDS 8.1) > Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [Server] > -------------------------------------------------------------- > > Key: JBIDE-19114 > URL: https://issues.jboss.org/browse/JBIDE-19114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > There are changes in jbosstools-server since 4.2.2.Final was released but the versions of plugins/features have not incremented. > https://github.com/jbosstools/jbosstools-server/commits/jbosstools-4.2.x > So, please upversion all your plugins & features, or at the very least, org.jboss.ide.eclipse.as.jmx.integration, so that it's at least up to version 3.0.2. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19122) Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19122?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19122: -------------------------------------- Description: There are changes in jbosstools-openshift since 4.2.2.Final was released but the versions of plugins/features have not incremented. https://github.com/jbosstools/jbosstools-openshift/commits/jbosstools-4.2.x So, please upversion all your plugins & features & /pom.xm was: There are changes in jbosstools-server since 4.2.2.Final was released but the versions of plugins/features have not incremented. https://github.com/jbosstools/jbosstools-server/commits/jbosstools-4.2.x So, please upversion all your plugins & features, or at the very least, org.jboss.ide.eclipse.as.jmx.integration, so that it's at least up to version 3.0.2. Assignee: Andre Dietisheim (was: Rob Stryker) Component/s: openshift (was: server) > Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift] > ----------------------------------------------------------------- > > Key: JBIDE-19122 > URL: https://issues.jboss.org/browse/JBIDE-19122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.Beta1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > There are changes in jbosstools-openshift since 4.2.2.Final was released but the versions of plugins/features have not incremented. > https://github.com/jbosstools/jbosstools-openshift/commits/jbosstools-4.2.x > So, please upversion all your plugins & features & /pom.xm -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19122) Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19122?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19122: ----------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-server/pull/323) > Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift] > ----------------------------------------------------------------- > > Key: JBIDE-19122 > URL: https://issues.jboss.org/browse/JBIDE-19122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.Beta1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > There are changes in jbosstools-openshift since 4.2.2.Final was released but the versions of plugins/features have not incremented. > https://github.com/jbosstools/jbosstools-openshift/commits/jbosstools-4.2.x > So, please upversion all your plugins & features & /pom.xm -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19122) Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift]

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19122: -------------------------------------- Summary: Upversion plugins + features for JBT 4.2.3 / JBDS 8.1 [OpenShift] Key: JBIDE-19122 URL: https://issues.jboss.org/browse/JBIDE-19122 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.3.Beta1 Reporter: Alexey Kazakov Assignee: Rob Stryker Priority: Blocker Fix For: 4.2.3.Beta1 There are changes in jbosstools-server since 4.2.2.Final was released but the versions of plugins/features have not incremented. https://github.com/jbosstools/jbosstools-server/commits/jbosstools-4.2.x So, please upversion all your plugins & features, or at the very least, org.jboss.ide.eclipse.as.jmx.integration, so that it's at least up to version 3.0.2. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19096: --------------------------------------- [~maxandersen] [~adietish] In regards to OAuth, I was speaking to the OS web console guy who implemented the tokens for the server. Our simplest implementation might be to provide a dialog where the user is directed to get their token and paste it into our textbox. Probably not the most ideal solution, but might be the best first approach. > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > !screenshot-openshift-signin.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Jeff Cantrill (JIRA)

Jeff Cantrill created TOOLSDOC-583: -------------------------------------- Summary: Add Section for OpenShift v3 Key: TOOLSDOC-583 URL: https://issues.jboss.org/browse/TOOLSDOC-583 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Components: User Guide - OpenShift Tools Reporter: Jeff Cantrill Assignee: Michelle Murray Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19118) ConcurrentModificationException

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19118?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19118: ---------------------------------------- It seems to be easy to fix, doesn't it? If so we can fix it for 4.3.0.Alpha1 and 4.2.3.Beta1. > ConcurrentModificationException > ------------------------------- > > Key: JBIDE-19118 > URL: https://issues.jboss.org/browse/JBIDE-19118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.2.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.x > > > This error occurred during a workspace refresh at startup with 2 projects having JAX-RS enabled (so not sure how reproduce, and not sure if the fact that there were 2 projects matters): > {code} > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) > at java.util.HashMap$EntryIterator.next(HashMap.java:1463) > at java.util.HashMap$EntryIterator.next(HashMap.java:1461) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.getProblemSeverity(JaxrsMetamodel.java:214) > at org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateCategory.getProblemLevel(UriPathTemplateCategory.java:163) > at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsLabelProvider.getImage(UriMappingsLabelProvider.java:39) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateCommonLabelProvider.getImage(SafeDelegateCommonLabelProvider.java:106) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.findImage(NavigatorContentServiceLabelProvider.java:197) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getColumnImage(NavigatorContentServiceLabelProvider.java:105) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.getImage(NavigatorContentServiceLabelProvider.java:98) > at org.eclipse.ui.internal.navigator.NavigatorDecoratingLabelProvider$StyledLabelProviderAdapter.getImage(NavigatorDecoratingLabelProvider.java:59) > at org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.getImage(DelegatingStyledCellLabelProvider.java:195) > at org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.getImage(DecoratingStyledCellLabelProvider.java:173) > at org.eclipse.jface.viewers.DelegatingStyledCellLabelProvider.update(DelegatingStyledCellLabelProvider.java:121) > at org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider.update(DecoratingStyledCellLabelProvider.java:136) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154) > at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:949) > at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:114) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1029) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1886) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1850) > at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561) > at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1528) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1436) > at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1397) > at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1525) > at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:533) > at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:350) > at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider$1.run(UriMappingsContentProvider.java:251) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19115: ----------------------------------- Fix Version/s: 4.2.3.Beta1 > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19121) web.xml shows dubious warning on missing welcome file matching Faces mapping

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19121?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19121: ------------------------------------- Unless the fix is *really* trivial, it doesn't need to be fixed in 4.2.3 > web.xml shows dubious warning on missing welcome file matching Faces mapping > ---------------------------------------------------------------------------- > > Key: JBIDE-19121 > URL: https://issues.jboss.org/browse/JBIDE-19121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.2.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > Given a web project containing index.xhtml at the root of the web folder, an web.xml file containing > {noformat} > <servlet> > <servlet-name>Faces Servlet</servlet-name> > <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> > <load-on-startup>1</load-on-startup> > </servlet> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern>*.jsf</url-pattern> > </servlet-mapping> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern>/faces/*</url-pattern> > </servlet-mapping>{noformat} > and > {noformat} > <welcome-file-list> > <welcome-file>faces/index.xhtml</welcome-file> > </welcome-file-list>{noformat} > shows an unexpected warning on <welcome-file>: > {quote}file name references to "faces/index.xhtml" that does not exist in web content{quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2015