August 2015 - jbosstools-issues - Jboss List Archives

[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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20100: ---------------------------------------- Here is a screencast: https://vid.me/qPQz With this, new Early-Access stuff are immediatly visible to users. About how to make users know that they have to use older JBDS in order to get Fuse, I still don't have a clue, and IMO it's not a problem we should resolve. I'd rather invest some time in having a Fuse build compatible enough with JBDS to be Early-Access on JBDS release than to spend time setting up UI telling users to download an older version of JBDS... > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20447: ------------------------------------ Node names are not predictive. How would you know based on the slave name what was installed on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev135-virt1/ ? > 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component > ------------------------------------------------------------------ > > Key: JBIDE-20447 > URL: https://issues.jboss.org/browse/JBIDE-20447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Labels: testfailure > Fix For: 4.3.0.CR1 > > > *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.268</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowserOrLink</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.0030</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowser</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-482) Migrate to using license feature in JBT IS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-482?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-482: ---------------------------------- find.sh is my own creation. Here's a copy: https://gist.github.com/nickboldt/43424bad58b7c93acacc > Migrate to using license feature in JBT IS 4.3 / JBDS IS 9 > ---------------------------------------------------------- > > Key: JBTIS-482 > URL: https://issues.jboss.org/browse/JBTIS-482 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > Attachments: jbide20194-portlet-not-updated.png > > > 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 (probably already done when you moved from Luna to Mars). > 2. Switch to using the new o.j.t.foundation.license.feature, which includes the new Red Hat license address -- see JBIDE-19826 for more details. > Instructions for migration are 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...] > STEPS TO VERIFY THAT YOUR CHANGES WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20528) Need to cover Bower Tools with RedDeer Tests

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20528?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20528: ---------------------------------------- Yes Max, we have discussed it with Pavol. These tests are supposed to be added to jbosstools-integration-tests. Not to jbosstools-jst. > Need to cover Bower Tools with RedDeer Tests > -------------------------------------------- > > Key: JBIDE-20528 > URL: https://issues.jboss.org/browse/JBIDE-20528 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > Attachments: Bower Init.png, Bower Update.png > > > The test scenarios: > # "Bower Init" Wizard flow > #* File -> New -> Other... -> New -> Bower -> Bower Init > #* Test default value in the Wizard (Name / Version etc.) > # "Bower Update" Launch Shortcut Availability > #* on IProject (with bower.json) > #* on IFolder (with bower.json) > #* on bower.json -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19335: ------------------------------------- > It shows dialog "Cannot create default browser No more handles" and then asks to exit workbench. [~vpakan] The question is why FoundationUIPlugin.pluginLog().logError(etc) is showing a dialog and asking to exit the workspace... how is that even happening? > org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19335 > URL: https://issues.jboss.org/browse/JBIDE-19335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, runtime-detection > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Environment: Linux > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.CR1 > > > DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'. > Steps to tests the issue: > 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify) > 2. Run JBT and try to download WildFly using Runtime Download dialog; > 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one > 4. Close eclipse > 5. Install libwebkit > 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015