June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3261: -------------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Xavier Coulon > Priority: Critical > Labels: websockets > Fix For: 9.0.0.Beta2 > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19926?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-19926: ------------------------------------------- Assignee: Max Rydahl Andersen > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-19926 > URL: https://issues.jboss.org/browse/JBIDE-19926 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Webservices]: 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 Webservices 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-19839) Cannot proceed to New OpenShift Application wizard via shell menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19839: ------------------------------------------ I cant reproduce this in my current workspace, i assume this was fixed with some fix that was done for 4.3.0.Beta1? Resolving. > Cannot proceed to New OpenShift Application wizard via shell menu > ----------------------------------------------------------------- > > Key: JBIDE-19839 > URL: https://issues.jboss.org/browse/JBIDE-19839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png > > > While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed). > Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19839) Cannot proceed to New OpenShift Application wizard via shell menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19839. -------------------------------------- Resolution: Done > Cannot proceed to New OpenShift Application wizard via shell menu > ----------------------------------------------------------------- > > Key: JBIDE-19839 > URL: https://issues.jboss.org/browse/JBIDE-19839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png > > > While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed). > Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19512) version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19512?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19512: ------------------------------------ Um... in Beta2 we have rse 3.7 http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... And versionwatch is happy (except for the javax.servlet thing - JBIDE-19605 - which should be fixed shortly). https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat... > version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2 > --------------------------------------------------------------------------- > > Key: JBIDE-19512 > URL: https://issues.jboss.org/browse/JBIDE-19512 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa, target-platform, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > These plugins versions dropped from these versions in JBDS 8.1.0... > {code} > org.eclipse.rse.dstore_3.7.0.201502160819 > org.eclipse.tm.terminal_3.7.0.201502160819 > org.eclipse.rse_3.7.0.201502160819 > org.eclipse.rse.ssh_3.7.0.201502160819 > org.eclipse.rse.telnet_3.7.0.201502160819 > org.eclipse.rse.ftp_3.7.0.201502160819 > org.eclipse.rse.terminals_3.7.0.201502160819 > org.eclipse.rse.local_3.7.0.201502160819 > org.eclipse.rse.core_3.7.0.201502160819 > org.eclipse.rse.terminals.ui_1.2.200.201412161015 > org.eclipse.tm.terminal_3.3.0.201501281007 {code} > to older versions in JBDS 9.0. > This could be an upstream problem (plugins not correctly upversioned at Eclipse) or it could be something that's been fixed in the latest Mars M6. Something we definitely need to investigate and report upstream if not fixed there already. > See detailed reports here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19786: ------------------------------------- Labels: connection_wizard (was: ) > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: connection_wizard > Fix For: 4.3.0.Beta1 > > Attachments: blank-browser-page.ogv, retrieve-dialog-1.png, retrieve-dialog-2.png, unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3317) Basic Docker support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3317?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3317: ------------------------------------------- FYI, I think we got all the features listed in main description covered for beta1 except api for server tooling. > Basic Docker support > -------------------- > > Key: JBDS-3317 > URL: https://issues.jboss.org/browse/JBDS-3317 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: docker, requirements > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.0.0.Beta1 > > > Basic docker support is to provide the following Docker features: > * pull/add images from registry > * list images > * list containers > * start containers from an image > * stop/restart/kill containers > * connect/disconnect from containers to show log/provide interactive console/terminal > * build dockerfile (available via right click on DockerFile / project / file with DockerFile - this should support .dockerignore) > * filter image/containers > * provide details for image/containers > * during launch be able to mount volumes, port forwards etc. in a simple UI (leave more advanced details to separate pages/different ui) > * provide API for other tooling in eclipse to use it (like server launches etc.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19786: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: blank-browser-page.ogv, retrieve-dialog-1.png, retrieve-dialog-2.png, unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19938) java.io.FileNotFoundException when batch feature installed

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19938?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-19938: ------------------------------------------ Sprint: Sprint #4 May 2015 > java.io.FileNotFoundException when batch feature installed > ---------------------------------------------------------- > > Key: JBIDE-19938 > URL: https://issues.jboss.org/browse/JBIDE-19938 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > I have a bunch of JavaEE projects in my workspace. > When opening that workspace I saw the following exception in the log: > {code} > java.io.FileNotFoundException: /home/igels/Java/eclipse-mars/workspace/runtime/SeamTest/WebContent/WEB-INF/classes (Is a directory) > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:220) > at java.util.zip.ZipFile.<init>(ZipFile.java:150) > at java.util.jar.JarFile.<init>(JarFile.java:166) > at java.util.jar.JarFile.<init>(JarFile.java:130) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:47) > at org.jboss.tools.common.core.jandex.JandexUtil.hasSubtypes(JandexUtil.java:123) > at org.jboss.tools.batch.internal.core.scanner.BatchArchiveDetector.computeIsJarBatchArchive(BatchArchiveDetector.java:278) > {code} > WEB-INF/classes or any other bin folder should not been scanned by Batch JAR scanner. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19938) java.io.FileNotFoundException when batch feature installed

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19938?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-19938: ------------------------------------------ Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Beta2) > java.io.FileNotFoundException when batch feature installed > ---------------------------------------------------------- > > Key: JBIDE-19938 > URL: https://issues.jboss.org/browse/JBIDE-19938 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > I have a bunch of JavaEE projects in my workspace. > When opening that workspace I saw the following exception in the log: > {code} > java.io.FileNotFoundException: /home/igels/Java/eclipse-mars/workspace/runtime/SeamTest/WebContent/WEB-INF/classes (Is a directory) > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:220) > at java.util.zip.ZipFile.<init>(ZipFile.java:150) > at java.util.jar.JarFile.<init>(JarFile.java:166) > at java.util.jar.JarFile.<init>(JarFile.java:130) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:47) > at org.jboss.tools.common.core.jandex.JandexUtil.hasSubtypes(JandexUtil.java:123) > at org.jboss.tools.batch.internal.core.scanner.BatchArchiveDetector.computeIsJarBatchArchive(BatchArchiveDetector.java:278) > {code} > WEB-INF/classes or any other bin folder should not been scanned by Batch JAR scanner. -- 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