September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-11367: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: 4.4.x > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19181: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > correct naming of internal packages so that they're consistent across all openshift plugins > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19181 > URL: https://issues.jboss.org/browse/JBIDE-19181 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > Internal packages across the openshift plugins are non-consistent: > ex. > org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal > org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal > the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins. > For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages > {quote} > org.eclipse.jdt.internal.core.compiler - Correct usage > org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name. > org.eclipse.core.internal.resources - Correct usage > org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse. > org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name. > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20596) Next button in the New OpenShift Application window is enabled only after clicking Use default server check box

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20596?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20596: -------------------------------- Labels: (was: respin-a) > Next button in the New OpenShift Application window is enabled only after clicking Use default server check box > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20596 > URL: https://issues.jboss.org/browse/JBIDE-20596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Supriya Bharadwaj > Assignee: Jeff Cantrill > Fix For: 4.3.1.Final > > Attachments: screenshot-1.png, screenshot-2.png > > > In the New OpenShift Application window, after all the fields are filled in and the token is entered in the Token field, (my guess is) the Next button should get enabled, which doesn't happen. The button gets enabled only after the "Use default Server" check box is clicked. Is this a bug? > (I am trying this in JBDS v9.0cr1) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20759) Add project name validation

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20759: -------------------------------- Issue Type: Bug (was: Feature Request) > Add project name validation > --------------------------- > > Key: JBIDE-20759 > URL: https://issues.jboss.org/browse/JBIDE-20759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Final > > > We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-501) stable URLs used for Integration Stack installs/updates via Central should not contain a version number

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-501?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-501: ---------------------------------- [~nickboldt] has already taken care of the example above (thanks Nick). The other versioned URL is needed by SAP since it has trouble with composite sites (ref https://issues.jboss.org/browse/FUSETOOLS-1440). > stable URLs used for Integration Stack installs/updates via Central should not contain a version number > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-501 > URL: https://issues.jboss.org/browse/JBTIS-501 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.2.3.Final , 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Stable URLs used for Integration Stack installs/updates via Central should not contain a version number, so that users only see ONE URL, which is updated to contain new, fresh content. > This allows new users to see the latest updates, existing users to see newer updates (Help > Check for updates), and existing users to seek new updates in Central, too. > So... > {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L82} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download... > Needs to change to > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download... > {code} > And http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ needs to be a composite of http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20747: --------------------------------- Attachment: plugins.txt features.txt > install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20747 > URL: https://issues.jboss.org/browse/JBIDE-20747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.Final > > Attachments: features.txt, plugins.txt > > > This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120] > Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0" > -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true" > org.jboss.tools.browsersim.ui [1122] > Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)" > -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730" > org.eclipse.jetty.websocket.server [555] > Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)" > Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)" > -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13" > org.eclipse.jetty.websocket.servlet [556] > Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple" > -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory" > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Similar problems for other IUs: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222] > {code} > But the job was successful! > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20755) Import OpenShift Application wizard contains redundant validation mark

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20755?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20755: -------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > Import OpenShift Application wizard contains redundant validation mark > ---------------------------------------------------------------------- > > Key: JBIDE-20755 > URL: https://issues.jboss.org/browse/JBIDE-20755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.Final > > Attachments: validation_mark.png > > > In Import OpenShift Application wizard is one validation mark (red cross) on a text widget for a git clone location in case of already imported such repo. But there is shown also another validation mark in the middle of checkbox label. > !validation_mark.png! > This one is redundant and also its rendering is performed only when mouse is moved over the checkbox or its label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20755) Import OpenShift Application wizard contains redundant validation mark

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20755?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20755: ------------------------------------- This is the same problem causing JBIDE-19952, which [~snjeza] "fixed" by cheating on the margins > Import OpenShift Application wizard contains redundant validation mark > ---------------------------------------------------------------------- > > Key: JBIDE-20755 > URL: https://issues.jboss.org/browse/JBIDE-20755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.x > > Attachments: validation_mark.png > > > In Import OpenShift Application wizard is one validation mark (red cross) on a text widget for a git clone location in case of already imported such repo. But there is shown also another validation mark in the middle of checkbox label. > !validation_mark.png! > This one is redundant and also its rendering is performed only when mouse is moved over the checkbox or its label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20760: ---------------------------------------- I would go for the main solution (not the alternative ones). Use the original feature with a disabled update site. [~maxandersen], [~dgolovin]? > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: xtriage > Fix For: 4.3.0.Final > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20760: ----------------------------------- Labels: xtriage (was: ) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: xtriage > Fix For: 4.3.0.Final > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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