April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18911) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18911?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18911: -------------------------------- Labels: application_wizard embed_wizard new_and_noteworthy openshift_v2 (was: application_wizard embed_wizard new_and_noteworthy) > allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18911 > URL: https://issues.jboss.org/browse/JBIDE-18911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Labels: application_wizard, embed_wizard, new_and_noteworthy, openshift_v2 > Fix For: 4.4.x > > Attachments: clone-error.png, source-code.png > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git(a)github.com: or ssh://git@github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21479) Explorer: Display deployment details like web console

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21479?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21479: ------------------------------------- [~jcantrill]: can you be more specific? > Explorer: Display deployment details like web console > ----------------------------------------------------- > > Key: JBIDE-21479 > URL: https://issues.jboss.org/browse/JBIDE-21479 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20597: ------------------------------------- [~jeffmaury], can you please take a look at this one please? > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.x > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21651) Create and use Mars.2 RC4 target platform

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21651?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21651: ---------------------------------------- OK. But what about now? It can be resolved, right? :) > Create and use Mars.2 RC4 target platform > ----------------------------------------- > > Key: JBIDE-21651 > URL: https://issues.jboss.org/browse/JBIDE-21651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: p2diff_450x_jbds.txt, p2diff_450x_jbds_summary.txt, p2diff_450x_jbt.txt, p2diff_450x_jbt_summary.txt, p2diff_452x_jbds.txt, p2diff_452x_jbds_summary.txt, p2diff_452x_jbt.txt, p2diff_452x_jbt_summary.txt > > > Prepare new 4.52.x TPs to use Mars.2 bits. > https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M... > First RC4 bits should be available the week of 2/12 - 2/19, with 4.3.1.CR1 TP freeze day on Mar 1. > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build > * update install/matrix jobs to use new Eclipse JEE/platform binary > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22044) JBT 4.3.1.CR1 build has old aerogear bits

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22044?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22044. ------------------------------------ Resolution: Done Resolved as done for CR1a. Please reopened if it's still an issue. > JBT 4.3.1.CR1 build has old aerogear bits > ------------------------------------------ > > Key: JBIDE-22044 > URL: https://issues.jboss.org/browse/JBIDE-22044 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Looking at the JBT updatesite [1] aerogear.thym has been built on v20160203-2301-B70. > But there are newer commits in 4.3.x branch. It seems we aggregated old bits. > [1] http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22044) JBT 4.3.1.CR1 build has old aerogear bits

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22044?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22044: ----------------------------------- Priority: Major (was: Blocker) > JBT 4.3.1.CR1 build has old aerogear bits > ------------------------------------------ > > Key: JBIDE-22044 > URL: https://issues.jboss.org/browse/JBIDE-22044 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Looking at the JBT updatesite [1] aerogear.thym has been built on v20160203-2301-B70. > But there are newer commits in 4.3.x branch. It seems we aggregated old bits. > [1] http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21967: ------------------------------------- I think that if we start from the Server Adapter menu in OpenShift explorer, we should only display the selected service. We'd get rid of unnecessary loadings and would be insulated from irrelevant, building services. > Cannot create server adapter if there is a running build on a project although there are more projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21967 > URL: https://issues.jboss.org/browse/JBIDE-21967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22078: ----------------------------------- Component/s: server > Error publishing war file to wildfy 10.0 on windows > --------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Rob Stryker > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22041) Exception is thrown when I do not want to open cheatsheet

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22041?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22041: ---------------------------------------- Yes it should have been fixed in both master and 4.3.x but too late for CR1a build. It's not a blocker for 9.1.0.GA though. > Exception is thrown when I do not want to open cheatsheet > --------------------------------------------------------- > > Key: JBIDE-22041 > URL: https://issues.jboss.org/browse/JBIDE-22041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22057: ----------------------------------------------- [~mlabuda], could you please check two more cases. 1. After completing all steps and making sure that in debug mode the changes are not present, stop server adapter and restart it in Run mode. Will changes appear again, or the state remains as old as in Debug mode? 2. Repeat steps from the beginning but when restarting, do it in Run mode instead of Debug mode. That is to make sure that the mode does matter, rather than just the fact of restarting. > Changes done to OpenShift application are thrown away when debugging is enabled > ------------------------------------------------------------------------------- > > Key: JBIDE-22057 > URL: https://issues.jboss.org/browse/JBIDE-22057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different. > I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016