May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13287) examples URLs should use major/minor/service/milestone convention

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13287?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13287: -------------------------------- Story Points: 2 > examples URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------ > > Key: JBIDE-13287 > URL: https://issues.jboss.org/browse/JBIDE-13287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.2.x > > > Instead of > {code:title=http://download.jboss.org/jbosstools/examples/} > project-examples-community-4.0.GA.xml > project-examples-jbds60.xml > project-examples-maven-4.0.GA.xml > project-examples-shared-4.0.GA.xml > ... > {code} > We should consider using something like 6/1/0/Alpha1/project-examples*.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21307: ------------------------------- Story Points: 8 > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. > the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: > {quote} > Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22227: -------------------------------------- Sorry, you are correct, I was thinking about the general case of the hcr not working without the System.gc(); > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22126) Application wizard: local template buttons are truncated

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22126?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22126: -------------------------------- Story Points: 3 > Application wizard: local template buttons are truncated > -------------------------------------------------------- > > Key: JBIDE-22126 > URL: https://issues.jboss.org/browse/JBIDE-22126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: local-template-buttons.png, openshift_buttons.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19988) Run Docker image wizard does not recognize image that it pulled

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19988?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19988: ---------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Run Docker image wizard does not recognize image that it pulled > --------------------------------------------------------------- > > Key: JBIDE-19988 > URL: https://issues.jboss.org/browse/JBIDE-19988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.4.x > > > When you're in the Run a Docker Image and search for an image that you don't have (e.g. fedora:latest) and then pull it, using the link below the Image field, after the image is pulled, the wizard still says it's not available locally. > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469709 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21716: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) Sprint: devex #114 May 2017 > Don't re-prompt for password > ---------------------------- > > Key: JBIDE-21716 > URL: https://issues.jboss.org/browse/JBIDE-21716 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Pete Muir > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21716: -------------------------------- Story Points: 7 Priority: Major (was: Blocker) > Don't re-prompt for password > ---------------------------- > > Key: JBIDE-21716 > URL: https://issues.jboss.org/browse/JBIDE-21716 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Pete Muir > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21441: ----------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha2 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21441: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha2 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21351: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Error during "Update Maven projects configuration" > -------------------------------------------------- > > Key: JBIDE-21351 > URL: https://issues.jboss.org/browse/JBIDE-21351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.Beta1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha2 > > > Sometimes I get > {noformat} > An internal error occurred during: "Update Maven projects configuration". > Cannot add projects when processing is started{noformat} > when I'm importing maven project using easymport. > Full stacktrace: > {noformat} > java.lang.IllegalStateException: Cannot add projects when processing is started > at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97) > at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016