June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22466) Bump all server plugins' BREE to JavaSE-1.8

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22466?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22466. --------------------------------- The commit looks correct and server is building fine. Closing. > Bump all server plugins' BREE to JavaSE-1.8 > ------------------------------------------- > > Key: JBIDE-22466 > URL: https://issues.jboss.org/browse/JBIDE-22466 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > > [~tmader] made some PR on servers depending on Java 8 language features/API, but the server plugins are targeting Java 6. Their BREE should be bumped to JavaSE-1.8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22483) For JBIDE 4.4.0.Final: Prepare for Final/GA [Server]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22483?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22483. --------------------------------- Closing. > For JBIDE 4.4.0.Final: Prepare for Final/GA [Server] > ---------------------------------------------------- > > Key: JBIDE-22483 > URL: https://issues.jboss.org/browse/JBIDE-22483 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [Server]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22387) Create New and Noteworthy for 4.4.0.Alpha2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22387?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22387. --------------------------------- All sub-tasks being closed, closing this uber-task as well. > Create New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-22387 > URL: https://issues.jboss.org/browse/JBIDE-22387 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22407) Core/General New and Noteworthy for 4.4.0.Alpha2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22407?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22407. --------------------------------- It seems there is no content here. So closing. > Core/General New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------------ > > Key: JBIDE-22407 > URL: https://issues.jboss.org/browse/JBIDE-22407 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19260) Investigate expanding more "command line" options into UI and the IRuntime

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19260?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19260. --------------------------------- > Investigate expanding more "command line" options into UI and the IRuntime > -------------------------------------------------------------------------- > > Key: JBIDE-19260 > URL: https://issues.jboss.org/browse/JBIDE-19260 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: JBIDE-19260.png > > > https://bugzilla.redhat.com/show_bug.cgi?id=1191153 > Investigate whether it makes sense to expose the following command line options in the UI and API for IRuntime: > jboss.server.config.dir = jboss.server.base.dir/configuration > jboss.server.data.dir = jboss.server.base.dir/data > jboss.server.log.dir = jboss.server.base.dir/log > jboss.server.temp.dir = jboss.server.base.dir/tmp > jboss.server.deploy.dir = jboss.server.data.dir/content -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22541) server New and Noteworthy for 4.4.0.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22541?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22541. --------------------------------- Really, nothing... so less work for Rob and less work for me verifying it :) Closing. > server New and Noteworthy for 4.4.0.Final > ----------------------------------------- > > Key: JBIDE-22541 > URL: https://issues.jboss.org/browse/JBIDE-22541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > If no news for 4.4.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22362 at 6/8/16 10:42 AM: ---------------------------------------------------------------- The upstream issue has been fixed, nodejs template uses fixed base image. But static content is not visible by default/published and propagated. It requires DEV_MODE runtime environment set to true (this was not working earlier, but it is the fixed issue and working) and once the DEV_MODE is set to true, static content is updated. There are 2 outstanding question: a) How should it really work? I was trying to get some answer on #aos channel and bparees answered on question whether DEV_MODE is required even for static content: "depends how nodejs is serving that static content, i'm really not sure, but i'd be willing to be it caches it, so you'd need DEV_MODE to get the changes picked up." We need someone who is deep enough in nodejs stuff to clarify this one. b) Do we wanna have DEV_MODE environment variable set to true by default for nodejs examples to let users easily modify their application? If Answer from question A is that DEV_MODE is required even for static content. I think it would be quite "must be" to have an application which is changeable. was (Author: mlabuda): The upstream issue has been fixed, nodejs template uses fixed base image. But static content is not visible by default/published and propagated. It requires DEV_MODE runtime environment set to true (this was not working earlier, but it is the fixed issue and working) and once the DEV_MODE is set to true, static content is updated. There are 2 outstanding question: a) How should it really work? I was trying to get some answer on #aos channel and bparees answered on question whether DEV_MODE is required even for static content: "depends how nodejs is serving that static content, i'm really not sure, but i'd be willing to be it caches it, so you'd need DEV_MODE to get the changes picked up." b) Do we wanna have DEV_MODE environment variable set to true by default for nodejs examples to let users easily modify their application? If Answer from question A is that DEV_MODE is required even for static content. I think it would be quite "must be" to have an application which is changeable. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22513) [launchbar] NPE when null target

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22513?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22513. --------------------------------- Closing as I've never seen this happening and I don't have a way to verify. > [launchbar] NPE when null target > -------------------------------- > > Key: JBIDE-22513 > URL: https://issues.jboss.org/browse/JBIDE-22513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > > Stacktrace is as follows > {code} > java.lang.NullPointerException > at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76) > at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128) > at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964) > at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942) > at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424) > at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423) > at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043) > at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22362: --------------------------------------- The upstream issue has been fixed, nodejs template uses fixed base image. But static content is not visible by default/published and propagated. It requires DEV_MODE runtime environment set to true (this was not working earlier, but it is the fixed issue and working) and once the DEV_MODE is set to true, static content is updated. There are 2 outstanding question: a) How should it really work? I was trying to get some answer on #aos channel and bparees answered on question whether DEV_MODE is required even for static content: "depends how nodejs is serving that static content, i'm really not sure, but i'd be willing to be it caches it, so you'd need DEV_MODE to get the changes picked up." b) Do we wanna have DEV_MODE environment variable set to true by default for nodejs examples to let users easily modify their application? If Answer from question A is that DEV_MODE is required even for static content. I think it would be quite "must be" to have an application which is changeable. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Alpha1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22508. --------------------------------- Build #1013 is blue. Closing. > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016