August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20479) broken images in JBT/JBDS Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20479?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20479: ---------------------------------------- Ubuntu 15.04. JDK Oracle 8. > broken images in JBT/JBDS Central > --------------------------------- > > Key: JBIDE-20479 > URL: https://issues.jboss.org/browse/JBIDE-20479 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1 > > Attachments: broken-images-central-JBDS9CR1.png, broken-images-central-JBT-JBDS.png > > > Broken images. See screenshot. The first image, for the HTML5 project, links to this: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%2Fwizards%2Fhtml5.png > But that won't load in my browser. > Instead, THIS image DOES load: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%252Fwizards%252Fhtml5.png > Seems you need one extra level of escapes: `%252F` instead of just `%2F` for those slashes ( / ). > Could your filenames simply be images-wizards-html5.png to avoid the need for hexcode escapes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20343) Processing easymport cannot be stopped in reasonable time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20343?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-20343. ------------------------------------ Resolution: Done Resolved with https://github.com/jbosstools/jbosstools-playground/commit/be74ac37239575... > Processing easymport cannot be stopped in reasonable time > --------------------------------------------------------- > > Key: JBIDE-20343 > URL: https://issues.jboss.org/browse/JBIDE-20343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2, L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > During Easyimport operation it's unable to stop it. There is red stop box but it doesn't do anything in reasonable time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20479) broken images in JBT/JBDS Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20479?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20479: ------------------------------------ [~rhopp] [~akazakov] Which OS are you on / which version? Which JDK? > broken images in JBT/JBDS Central > --------------------------------- > > Key: JBIDE-20479 > URL: https://issues.jboss.org/browse/JBIDE-20479 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1 > > Attachments: broken-images-central-JBDS9CR1.png, broken-images-central-JBT-JBDS.png > > > Broken images. See screenshot. The first image, for the HTML5 project, links to this: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%2Fwizards%2Fhtml5.png > But that won't load in my browser. > Instead, THIS image DOES load: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%252Fwizards%252Fhtml5.png > Seems you need one extra level of escapes: `%252F` instead of just `%2F` for those slashes ( / ). > Could your filenames simply be images-wizards-html5.png to avoid the need for hexcode escapes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20509) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [reddeer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20509?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20509. ------------------------------ Resolution: Rejected Closing because rejected. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [reddeer] > ----------------------------------------------------------------------------------- > > Key: JBIDE-20509 > URL: https://issues.jboss.org/browse/JBIDE-20509 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Integration Tests]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20209) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [BrowserSim]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20209?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20209: ------------------------------------ [~kmarmaliykov] Please apply the PR here to update copyright dates and remove obsolete updateSiteName variables. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [BrowserSim] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20209 > URL: https://issues.jboss.org/browse/JBIDE-20209 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [BrowserSim]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20195) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20195?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20195: ------------------------------------ [~kmarmaliykov] Please apply the PR here to update copyright dates and remove obsolete updateSiteName variables. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear] > ------------------------------------------------------------------------------------ > > Key: JBIDE-20195 > URL: https://issues.jboss.org/browse/JBIDE-20195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20210: ------------------------------------ [~dgolovin] please apply the PR here. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20401: ------------------------------------ OLD url: http://tools.jboss.org/documentation/howto/openshift3_getting_started.html (empty doc / placeholder) NEW url: https://docs.openshift.com/enterprise/3.0/admin_guide/install/overview.html (doc in progress) PR to change the above URL within the wizard: https://github.com/jbosstools/jbosstools-download.jboss.org/pull/550 > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-478) when updating earlyaccess.properties files, please commit changes to BOTH JBT and JBDS files, in both git repos and on both servers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-478?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-478 at 8/31/15 11:10 AM: ------------------------------------------------------------ One step is missing here. Once you update the source files [1],[2],[3],[4] so that JBT/JBDS respins will pick up your changes, you still have to push your changes into the *live* files *as you stage your bits for QE*, or *release your bits to public*. [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [3] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... [4] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... This includes staging and development/stable, as documented in ide-config.properties [5]. [5] http://download.jboss.org/jbosstools/configuration/ide-config.properties You can also update the snapshots/ version, if you would like. Or the job can simply be re-run to collect your changes. {code} jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download... ... #jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR1/jbosstools-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|jbosstools|4.3=http://download.jboss... ... jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudi... ... #jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.0.0.CR1/devstudio-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|devstudio|9.0=https://devstudio.redh... {code} was (Author: nickboldt): One step is missing here. Once you update the source files [1],[2],[3],[4] so that JBT/JBDS respins will pick up your changes, you still have to push your changes into the *live* files *as you stage your bits for QE*, or *release your bits to public*. [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [3] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... [4] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... This includes staging and development/stable, as documented in ide-config.properties: {code} jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download... ... #jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR1/jbosstools-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|jbosstools|4.3=http://download.jboss... ... jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudi... ... #jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.0.0.CR1/devstudio-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|devstudio|9.0=https://devstudio.redh... {code} > when updating earlyaccess.properties files, please commit changes to BOTH JBT and JBDS files, in both git repos and on both servers > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-478 > URL: https://issues.jboss.org/browse/JBTIS-478 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha1, 4.3.0.Alpha1 > > Attachments: jbtis-vs-jbdis-earlyaccess.png > > > Discovered today that a change was pushed into https://devstudio.redhat.com/9.0/development/updates/discovery.earlyacces... > But the same change was NOT pushed to http://download.jboss.org/jbosstools/mars/development/updates/discovery.e... > So, comparing the files, we see a strange number of deltas between the JBDSIS version (adding bpel 1.0.5, upversioning from bpmn2 modeler 1.1.1 to 1.2, etc.) > Related: JBTIS-476, JBTIS-477 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-478) when updating earlyaccess.properties files, please commit changes to BOTH JBT and JBDS files, in both git repos and on both servers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-478?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-478: ---------------------------------- One step is missing here. Once you update the source files [1],[2],[3],[4] so that JBT/JBDS respins will pick up your changes, you still have to push your changes into the *live* files *as you stage your bits for QE*, or *release your bits to public*. [1] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... [3] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... [4] https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties... This includes staging and development/stable, as documented in ide-config.properties: {code} jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download... ... #jboss.discovery.earlyaccess.list.url|jbosstools|4.3.0.CR1=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.0.CR1/jbosstools-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|jbosstools|4.3=http://download.jboss... ... jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudi... ... #jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.CR1=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/9.0.0.CR1/devstudio-earlyaccess.properties ... jboss.discovery.earlyaccess.list.url|devstudio|9.0=https://devstudio.redh... {code} > when updating earlyaccess.properties files, please commit changes to BOTH JBT and JBDS files, in both git repos and on both servers > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-478 > URL: https://issues.jboss.org/browse/JBTIS-478 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 9.0.0.Alpha1, 4.3.0.Alpha1 > > Attachments: jbtis-vs-jbdis-earlyaccess.png > > > Discovered today that a change was pushed into https://devstudio.redhat.com/9.0/development/updates/discovery.earlyacces... > But the same change was NOT pushed to http://download.jboss.org/jbosstools/mars/development/updates/discovery.e... > So, comparing the files, we see a strange number of deltas between the JBDSIS version (adding bpel 1.0.5, upversioning from bpmn2 modeler 1.1.1 to 1.2, etc.) > Related: JBTIS-476, JBTIS-477 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 August 2015