December 2015 - jbosstools-issues

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Martin Malina resolved JBDS-3571. --------------------------------- Assignee: Martin Malina (was: Jiri Pallich) Resolution: Done This is the conclusion: CSP - includes details including links to BZ/CVE - good enough http://tools.jboss.org/downloads/devstudio/mars/9.0.0.GA.html - includes link to http://tools.jboss.org/blog/ga-cve-for-mars.html http://www.jboss.org/products/devstudio/download/ - @Nick will add a "Release Notes" item which links to the blog - part of DEVELOPER-1435 This was agreed upon on today's PM call. So there is nothing more to be done in this JIRA. Resolved. > 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-20531) Expose additional service ports from deploy docker image wizard

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ] Catherine Robson commented on JBIDE-20531: ------------------------------------------ Can you edit the text or are you forced to only change it through the spinner? Spinner only is likely not a good user experience in this case as users might have to jump to a completely different port series. I would expect this to happen often in dev and test environments where they might need to avoid regular ports. Also, double clicking on the port to edit it on that first page doesn't feel obvious to me. Is there a hover state or anything that indicates that users can edit these fields as you mouse over? > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21284?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21284: ------------------------------------ Also fails locally: {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] {code} So, yeah, disabling it would be good. Curiously, the tests site does NOT fail the check. +1 to https://github.com/jbosstools/jbosstools-build-sites/pull/212 -- please apply in 4.3.1.Beta1x branch too. > 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-21293) CDK start timed out due to slow image download

by Martin Malina (JIRA)

Martin Malina created JBIDE-21293: ------------------------------------- Summary: CDK start timed out due to slow image download Key: JBIDE-21293 URL: https://issues.jboss.org/browse/JBIDE-21293 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Martin Malina Assignee: Rob Stryker I set up a CDK server using https://github.com/redhat-developer-tooling/openshift-vagrant . Then I tried to start the server for the first time. Of course this will take quite long as it needs to download the VM image first. I was on a very fast connection, but it still only went around 1 MB/s. So the startup took longer than the default timeout of 450 s. The result was that the startup timed out in the middle followed by an attempted shutdown by the tooling which failed. So in the end I ended up with the running box, but with two unwanted errors. I'm not sure what we can do here. Perhaps just increase the timeout to something bigger? Even better would be if could detect that a download is in progress so it will take longer, but I don't think the current mechanism is capable of anything like that. -- 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 Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-694?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-694: -------------------------------------------- Cool, [~mmalina]! Do let me know if we still need to go ahead with this. > 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

[JBoss JIRA] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-537. ---------------------------- Fix Version/s: 4.3.0.Alpha2 Resolution: Duplicate Issue Already fixed - ref https://issues.jboss.org/browse/JBTIS-529 > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: fuse1.png, fuse2.png, fuse3.png, fuse4.png, fuse5.png, fuse6.png > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- 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: ------------------------------------- Spinners are fine with me. They still act as text fields anyway so you can type whatever you want. But I'm no UI expert, contrary to [~crobson] :-) > 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] (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 commented on TOOLSDOC-694: ---------------------------------------- [~supriya.bharadwaj], I added this to the PM meeting agenda - the call is in 15 minutes. So I hope everybody agrees with this conclusion that we don't need a special doc. But thanks for the effort! > 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

[JBoss JIRA] (JBIDE-20726) Docker explorer - Default setting should be to display and not hide stopped containers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20726?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20726: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Docker explorer - Default setting should be to display and not hide stopped containers > -------------------------------------------------------------------------------------- > > Key: JBIDE-20726 > URL: https://issues.jboss.org/browse/JBIDE-20726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta2 > > > By default, only running containers are shown in the Docker explorer view - I think that users will expect to see all containers by default. The OOTB default setting should be changed to show all containers. Thx! -- 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 Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20531: --------------------------------------- [~jcantrill] yeah I agree. New JIRA but with low priority, maybe optional. > 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

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