December 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3571. ---------------------------- Closing: nothing to see here, please more along. > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Len DiMaggio > Assignee: Martin Malina > Fix For: 9.0.0.CVE-2015-7501-GA > > Attachments: patch.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20915: --------------------------------------- @vpakan: thanks for confirming that is works with a delay. As I explained before, there must be a bad synchronization between LiveReload and Wildfly, because the LiveReload plugin in JBoss Tools is notified when the html file has been published and then it notified the browser, but it is possible that WildFly did not re-deploy this html file before the browser received the "reload" command, and hence, it gets the old copy of the page instead of the new one. [~mhusnain], where should we document this workaround ? > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20915: ---------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20915: --------------------------------------- To be documented in 4.3.1.Beta2. > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) ReLicense JBDS Installer

by Richard Fontana (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Richard Fontana commented on JBDS-3557: --------------------------------------- I agree :) > ReLicense JBDS Installer > ------------------------ > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20531: ------------------------------------- As I said in my previous comment, you can still type whatever you want, so it behaves as a standard text field: http://screencast.com/t/W5DcaYXqW There's no tooltip though, and using the spinner when both values are "unlinked", seems weird > Expose additional service ports from deploy docker image wizard > --------------------------------------------------------------- > > Key: JBIDE-20531 > URL: https://issues.jboss.org/browse/JBIDE-20531 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: Service and routing page.png, service port edit dialog.png > > > Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21284) compare baselines failing in 4.3.x branch for aggregate site builds (central and EA)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21284?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21284: ---------------------------------------- The build of the central and ea sites seem to happen a bit differently from the other sites. > compare baselines failing in 4.3.x branch for aggregate site builds (central and EA) > ------------------------------------------------------------------------------------ > > Key: JBIDE-21284 > URL: https://issues.jboss.org/browse/JBIDE-21284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {code} > [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4": For input string: "raw:4" -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines (default) on project org.jboss.tools.site.central: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4" > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.MojoFailureException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4" > at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:176) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > Caused by: java.lang.IllegalArgumentException: invalid version "raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT": non-numeric "raw:4" > at org.osgi.framework.Version.parseInt(Version.java:170) > at org.osgi.framework.Version.<init>(Version.java:126) > at org.eclipse.tycho.plugins.p2.extras.CompareWithBaselineMojo.execute(CompareWithBaselineMojo.java:120) > ... 21 more > Caused by: java.lang.NumberFormatException: For input string: "raw:4" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:580) > at java.lang.Integer.parseInt(Integer.java:615) > at org.osgi.framework.Version.parseInt(Version.java:168) > ... 23 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-20915: ------------------------------------- Tested with JBDSA 9.1.0.Beta1-v20151208-2104-B170. Setting "Reload delay" to 4 seconds helped. Page was properly redisplayed but it's not user friendly because JBDS was displaying dialog with running processes while typing and saving index.html page frequently in VPE. This need to set "Reload delay" LiveReload server parameter should be somewhere documented where it would be easy to find and maybe would be good to have default value to appropriate non zero value? > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Vlado Pakan > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Vlado Pakan reassigned JBIDE-20915: ----------------------------------- Assignee: Xavier Coulon (was: Vlado Pakan) > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-694) Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-694?page=com.atlassian.jira.plug... ] Martin Malina resolved TOOLSDOC-694. ------------------------------------ Resolution: Rejected Everybody on today's PM call agreed that we don't need a special doc. Rejecting this JIRA. > Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article > -------------------------------------------------------------------- > > Key: TOOLSDOC-694 > URL: https://issues.jboss.org/browse/TOOLSDOC-694 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Martin Malina > > [~mmalina], you may find the article at > https://docs.google.com/document/d/1BiZV7vMatYblmv73WJzNqUrmzF2ah011pwEqK... > As discussed, please feel free to recommend deletions/additions/modifications to the article so that we can come up with the most appropriate content for the users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015