April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3755: ----------------------------- Attachment: readme.png readme2.png Oh, it's in the zip. !readme.png! And here's the contents: !readme2.png! > JBDS source zip: all files have 000 permissions after unzip > ----------------------------------------------------------- > > Key: JBDS-3755 > URL: https://issues.jboss.org/browse/JBDS-3755 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: readme.png, readme2.png > > > While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem: > When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22069) Allow stop / start / restart to work on module selections in server view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22069?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22069. --------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-21934 > Allow stop / start / restart to work on module selections in server view > ------------------------------------------------------------------------ > > Key: JBIDE-22069 > URL: https://issues.jboss.org/browse/JBIDE-22069 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Allow simple module-state verification based on rsync and checking deployment markers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22068) [openshift server] Wire up module-restart / republish for hot-code replace

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22068?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-22068. ------------------------------- Resolution: Duplicate Issue Duplicate of JBIDE-21933 > [openshift server] Wire up module-restart / republish for hot-code replace > -------------------------------------------------------------------------- > > Key: JBIDE-22068 > URL: https://issues.jboss.org/browse/JBIDE-22068 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > I've made this a subtask because it is related to but not a core piece of enabling module-restart. This jira is for allowing more options on hotcode-replace failure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21917) oc rsync waits forever on windows

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21917?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21917. --------------------------------- Resolution: Cannot Reproduce Bug Can't reproduce, resolving > oc rsync waits forever on windows > --------------------------------- > > Key: JBIDE-21917 > URL: https://issues.jboss.org/browse/JBIDE-21917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > On windows 10 + CDK 2 Beta5, oc rsync is stuck until it times out when saving a file, autopublished via the server adapter > {noformat} > "Worker-7" #48 prio=5 os_prio=0 tid=0x000000001bc85000 nid=0x1928 runnable [0x00000000275ee000] > java.lang.Thread.State: RUNNABLE > at java.lang.ProcessImpl.waitForTimeoutInterruptibly(Native Method) > at java.lang.ProcessImpl.waitFor(Unknown Source) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.waitForExit(OpenShiftBinaryRSync.java:59) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.sync(OpenShiftBinaryRSync.java:50) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:102) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.core.server.RSync.syncPodToDirectory(RSync.java:99) > at org.jboss.tools.openshift.core.server.RSync.syncPodsToDirectory(RSync.java:67) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:84) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1330) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(OpenshiftResourceChangeListener.java:227) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.run(OpenshiftResourceChangeListener.java:208) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22010?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22010. ------------------------------ Resolution: Done > For JBIDE 4.3.1.CR1: Prepare for Final/GA > ----------------------------------------- > > Key: JBIDE-22010 > URL: https://issues.jboss.org/browse/JBIDE-22010 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3740 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22016) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22016?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22016. ------------------------------ Thanks for being the last on the train. :D > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server] > -------------------------------------------------- > > Key: JBIDE-22016 > URL: https://issues.jboss.org/browse/JBIDE-22016 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Server]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22016) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22016?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22016 at 4/1/16 11:43 AM: ------------------------------------------------------------- Please push this at your earliest convenience. https://github.com/jbosstools/jbosstools-server/pull/407 Please then also kick your job, eg., {code}firefox https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... {code} was (Author: nickboldt): Please push this at your earliest convenience. https://github.com/jbosstools/jbosstools-server/pull/407 > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server] > -------------------------------------------------- > > Key: JBIDE-22016 > URL: https://issues.jboss.org/browse/JBIDE-22016 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Server]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3753) Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3753?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3753: -------------------------------- Fix Version/s: 9.1.0.GA > Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway > --------------------------------------------------------------------------------------- > > Key: JBDS-3753 > URL: https://issues.jboss.org/browse/JBDS-3753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160401-28 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Using bundled installer build 28 - confirmation page will not let me use the bundled JDK if it detects a pre-existing JDK somewhere else. > Once the installation is triggered, JDK goes straight to finished (not a problem under these circumstances) but JBDS fails right away and the log says: > {noformat} > Fri, 01 Apr 2016 07:20:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zSE006.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds failed to install: Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > {noformat} > So basically, I can't get it to install the bundled JDK but it will still try to use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22010?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22010: ------------------------------------ Only one project remaining, as predicted. * jbosstools-server > For JBIDE 4.3.1.CR1: Prepare for Final/GA > ----------------------------------------- > > Key: JBIDE-22010 > URL: https://issues.jboss.org/browse/JBIDE-22010 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3740 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3757: -------------------------------- Fix Version/s: 9.1.0.GA > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- 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