June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19935) Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19935?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19935: ---------------------------------- Workaround Description: Access to the token via web browser (https://api.stg.openshift.com/oauth/token/request). (was: Access to the token via web browser.) > Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty. > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19935 > URL: https://issues.jboss.org/browse/JBIDE-19935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard > > After filling in credentials to obtain token for OAuth for v3 connection there is opened new shell where is supposed to be shown token for authentication. Shell is loaded empty (blank) without any token. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19935) Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19935?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19935: ---------------------------------- Summary: Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty. (was: Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty.) > Shell which is supposed to contain token for OAuth authentication for OpenShift v3 connection is empty. > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19935 > URL: https://issues.jboss.org/browse/JBIDE-19935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard > > After filling in credentials to obtain token for OAuth for v3 connection there is opened new shell where is supposed to be shown token for authentication. Shell is loaded empty (blank) without any token. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19933: ---------------------------------- Assignee: Nick Boldt > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19935) Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19935?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19935: ---------------------------------- Workaround Description: Access to the token via web browser. > Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty. > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19935 > URL: https://issues.jboss.org/browse/JBIDE-19935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard > > After filling in credentials to obtain token for OAuth for v3 connection there is opened new shell where is supposed to be shown token for authentication. Shell is loaded empty (blank) without any token. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19935) Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19935?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19935: ---------------------------------- Labels: connection_wizard (was: ) > Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty. > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19935 > URL: https://issues.jboss.org/browse/JBIDE-19935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard > > After filling in credentials to obtain token for OAuth for v3 connection there is opened new shell where is supposed to be shown token for authentication. Shell is loaded empty (blank) without any token. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19933: ------------------------------------ Actually, there's a better way to avoid this: c) Wait until all projects have branched before updating parent pom in Beta1x branch to point to stream=4.3.mars: https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.3.0.Beta... > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19935) Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty.

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-19935: ------------------------------------- Summary: Shell supposed to containt token for OAuth authentication for OpenShift v3 connection is empty. Key: JBIDE-19935 URL: https://issues.jboss.org/browse/JBIDE-19935 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Marián Labuda After filling in credentials to obtain token for OAuth for v3 connection there is opened new shell where is supposed to be shown token for authentication. Shell is loaded empty (blank) without any token. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19918) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19918?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-19918. ----------------------------- Resolution: Done > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Hibernate] > ------------------------------------------------------- > > Key: JBIDE-19918 > URL: https://issues.jboss.org/browse/JBIDE-19918 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Hibernate]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19849) As a user I want to easily show my (v3) application in a browser

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19849?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19849: ---------------------------------------- Assignee: Andre Dietisheim > As a user I want to easily show my (v3) application in a browser > ---------------------------------------------------------------- > > Key: JBIDE-19849 > URL: https://issues.jboss.org/browse/JBIDE-19849 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: v3 > Fix For: 4.3.0.Beta1 > > > The tooling should allow the user to easily open up the application in a browser without having to look the url up in some property of the resources. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19934?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19934: ---------------------------------------- Does it happen when opening any file or some particular only? > NPE when opening a HTML file > ---------------------------- > > Key: JBIDE-19934 > URL: https://issues.jboss.org/browse/JBIDE-19934 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Gorkem Ercan > Assignee: Daniel Azarov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though. > eclipse.buildId=unknown > java.version=1.8.0_25 > java.vendor=Oracle Corporation > org.eclipse.ui.workbench > Error > Thu Jun 04 11:10:36 EDT 2015 > Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". > java.lang.NullPointerException > at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214) > at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140) > at org.eclipse.ui.internal.PartService$1.run(PartService.java:84) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81) > at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056) > at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810) > at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798) > at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195) > at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102) > at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541) > at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500) > at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360) > at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167) > at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268) > at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251) > at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50) > at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229) > at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191) > at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) > at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854) > 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:173) > at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851) > at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168) > at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449) > at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275) > at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278) > at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 June 2015