July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20392: --------------------------------------- [~nickboldt], yes, as I said in the description, browsersim plugins are listed under the Plug-ins tab in the same window. I can't really compare what's shown in the UI to what I see on the disk, because there is no way to copy&paste from the UI, BUT ... {code} nattura:features rasp$ ls|grep org.jboss.tools|wc -l 45 {code} Whereas in the UI I can only see 21 features starting with org.jboss.tools. So this is definitely not just browsersim and most likely this is a non-issue? > Browsersim feature not shown in Installation details > ---------------------------------------------------- > > Key: JBIDE-20392 > URL: https://issues.jboss.org/browse/JBIDE-20392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features. > In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2. > Maybe there is an explanation for this, but I asked around and nobody knows why this happens. > Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-663) JBDS 9 Beta2: Create Release Notes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-663?page=com.atlassian.jira.plug... ] Marián Labuda commented on TOOLSDOC-663: ---------------------------------------- OpenShift: - link to retrieve token opens internal browser in a new shell with page providing token - second para could have also double arrow sign in the beginning. This information could probably precede the previous para and it is not related to OAuth which is described in first para - could you please rephrase "You can easily point your browser to your OpenShift v3 application via the context menu."? Because we are not pointing browser to OS v3 app via context menu but we are showing an application in browser via this context menu. Since Beta2 it is also possible to use Show in Browser from context menu of a specific routing - "JBoss Developer Studio 9.0 Beta1 will show you OpenShift v3 routes " maybe there should be Beta2? thanks > JBDS 9 Beta2: Create Release Notes > ---------------------------------- > > Key: TOOLSDOC-663 > URL: https://issues.jboss.org/browse/TOOLSDOC-663 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Essentially update the Beta1 release notes to include all new known and resolved issues for Beta2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20394: ------------------------------------ After discussion in IRC and experimentation offline, I've found that the hudson profile won't work: https://github.com/nickboldt/jbosstools-integration-tests/commit/5083dc16... Found a better solution & have updated the PR https://github.com/jbosstools/jbosstools-integration-tests/pull/1091 > jbosstools integration tests site depends on itself to build; site is not self-cleaning > --------------------------------------------------------------------------------------- > > Key: JBIDE-20394 > URL: https://issues.jboss.org/browse/JBIDE-20394 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > I've found some problems today: > 1. building JBT integration tests requires the JBT integration tests site [circular dependency] > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > {code} > 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1] > [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... > 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts. > [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time. > 5. The check that the build does to determine if it should publish the new bits is failing to find the check script. > 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical. > [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > This is because we have symlinks: > {code} > updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/ > updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/ > {code} > So this is OK but we should migrate to use the new correct URLs instead of the old ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20394: ------------------------------- Priority: Blocker (was: Major) > jbosstools integration tests site depends on itself to build; site is not self-cleaning > --------------------------------------------------------------------------------------- > > Key: JBIDE-20394 > URL: https://issues.jboss.org/browse/JBIDE-20394 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > I've found some problems today: > 1. building JBT integration tests requires the JBT integration tests site [circular dependency] > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > {code} > 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1] > [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... > 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts. > [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time. > 5. The check that the build does to determine if it should publish the new bits is failing to find the check script. > 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical. > [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > This is because we have symlinks: > {code} > updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/ > updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/ > {code} > So this is OK but we should migrate to use the new correct URLs instead of the old ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-466) JBTIS 4.2.3.Final component updates

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-466: -------------------------------- Summary: JBTIS 4.2.3.Final component updates Key: JBTIS-466 URL: https://issues.jboss.org/browse/JBTIS-466 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution Affects Versions: 4.2.3.Final Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.2.3.Final Component updated to JBTIS composites and discovery metadata. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3261) JSR-356: Websockets. Import, build, run on server

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3261?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-3261. ------------------------------- Verified in JBDS 9.0.0.Beta2 respin b. > JSR-356: Websockets. Import, build, run on server > ------------------------------------------------- > > Key: JBDS-3261 > URL: https://issues.jboss.org/browse/JBDS-3261 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, webservices > Reporter: Burr Sutter > Assignee: Marián Labuda > Priority: Critical > Labels: websockets > Fix For: 9.0.0.Beta2 > > > Support for import (without error), build, Run on Server and Debug on Server. > https://github.com/javaee-samples/javaee7-samples/tree/master/websocket -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3454) Mobile Hybrid Project not opening on the emulator

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3454?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3454: ------------------------------------ Can you also attach your .log file? > Mobile Hybrid Project not opening on the emulator > ------------------------------------------------- > > Key: JBDS-3454 > URL: https://issues.jboss.org/browse/JBDS-3454 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 9.0.0.Alpha2 > Reporter: Supriya Bharadwaj > Assignee: Gorkem Ercan > Priority: Minor > > I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20208: --------------------------------------- [~nickboldt], I didn't say the license.html file shouldn't be there, I assumed that's how the license feature works - it will copy the license into the feature when you build it. So you can confirm that's how it works? That is settled then. But there is still the problem that the license is not correctly displayed in Eclipse - see the screenshot above. So that should be fixed. But right now I'm not sure why that happens, what's the problem. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt] > -------------------------------------------------------------------------------- > > Key: JBIDE-20208 > URL: https://issues.jboss.org/browse/JBIDE-20208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > Attachments: birt-no-license.png > > > For JBIDE 4.3.0.CR1 [Birt]: 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 Birt 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20394: --------------------------------------- [~nickboldt], yes, using the already existing hudson profile seems like a better option. In the hudson profile, we would effectively duplicate the jbosstools-site repo definition which has zero effect, is that what you mean? Can you add that to the PR if that's not a bother? I would do it myself if I could ;) Just: {code} <profiles> <profile> <id>hudson</id> <properties> <jbosstools-integrationtests-site>${jbosstools-site}</jbosstools-integrationtests-site> </properties> </profile> </profiles> {code} That should do the trick? > jbosstools integration tests site depends on itself to build; site is not self-cleaning > --------------------------------------------------------------------------------------- > > Key: JBIDE-20394 > URL: https://issues.jboss.org/browse/JBIDE-20394 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > I've found some problems today: > 1. building JBT integration tests requires the JBT integration tests site [circular dependency] > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > {code} > 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1] > [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... > 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts. > [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time. > 5. The check that the build does to determine if it should publish the new bits is failing to find the check script. > 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical. > [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > This is because we have symlinks: > {code} > updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/ > updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/ > {code} > So this is OK but we should migrate to use the new correct URLs instead of the old ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20392: ------------------------------- Component/s: updatesite > Browsersim feature not shown in Installation details > ---------------------------------------------------- > > Key: JBIDE-20392 > URL: https://issues.jboss.org/browse/JBIDE-20392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features. > In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2. > Maybe there is an explanation for this, but I asked around and nobody knows why this happens. > Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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