December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18919) Weak performance on Software/Update tab features loading

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18919?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18919: ---------------------------------------- Most comments in this bug seem to drive to the conclusion that this is not an infrastructure or a download issue, but more an issue in the code itself while comparing state of the application with content of remote repositories. > Weak performance on Software/Update tab features loading > -------------------------------------------------------- > > Key: JBIDE-18919 > URL: https://issues.jboss.org/browse/JBIDE-18919 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > It takes about ~1 minute to load content into Software/Update tab in central. > Some of my colleagues noticed this too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18980) New Table wizard for HTML5 palette

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-18980: --------------------------------------------- Summary: New Table wizard for HTML5 palette Key: JBIDE-18980 URL: https://issues.jboss.org/browse/JBIDE-18980 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-375) Missing source feature for org.eclipse.bpmn2.feature

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-375?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-375: ------------------------------------------ We have a new build here: http://download.eclipse.org/modeling/mdt/bpmn2/updates/luna/1.0.0/ This has both the bpmn2 and bpmn2.source features. > Missing source feature for org.eclipse.bpmn2.feature > ---------------------------------------------------- > > Key: JBTIS-375 > URL: https://issues.jboss.org/browse/JBTIS-375 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta2 > Environment: JBDS 8.0.1.GA + JBDS-IS 8.0.0.Beta2 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Each BPMN2 feature has its appropriate source feature except org.eclipse.bpmn2.feature > http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3296: ------------------------------------- Yes, I did clean jbds 8.0.0.GA install, then I ran update and got all reported errors. Those errors about missing repositories appear only in case installation to drive different from where user home is. I could not replicate any of reported problems when bot user home and jbds installation on the same device. > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18669: ---------------------------------- Description: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items and edit set of items was: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items 3. Custom set of items (defined by user) It should be possible to limit number of items and edit set of items (for 1 and 2) > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items and edit set of items -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3284: --------------------------------- Fix Version/s: 9.0.0.Alpha1 > Ionic Palette - version selection, detection > -------------------------------------------- > > Key: JBDS-3284 > URL: https://issues.jboss.org/browse/JBDS-3284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Fix For: 9.0.0.Alpha1 > > > As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3284: ----------------------------------- [~akazakov]I believe it is enough > Ionic Palette - version selection, detection > -------------------------------------------- > > Key: JBDS-3284 > URL: https://issues.jboss.org/browse/JBDS-3284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > > As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3294) Remove File->New->RichFaces Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3294: ------------------------------------ Assignee: Fred Bricon (was: Nick Boldt) I have changed the title and assigning to [~fbricon] to verify and merge the corresponding PR - https://github.com/jbosstools/jbosstools-central/pull/314 > Remove File->New->RichFaces Project > ----------------------------------- > > Key: JBDS-3294 > URL: https://issues.jboss.org/browse/JBDS-3294 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha1 > > > With RichFaces going into maintenance mode in 2016, we should remove 'File-New RichFaces Project' and have RichFaces available in the Software/Update tab much like Seam. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3294) Remove File->New->RichFaces Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3294: --------------------------------- Summary: Remove File->New->RichFaces Project (was: Remove RichFaces tooling from default JBDS installation) > Remove File->New->RichFaces Project > ----------------------------------- > > Key: JBDS-3294 > URL: https://issues.jboss.org/browse/JBDS-3294 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Reporter: Burr Sutter > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > With RichFaces going into maintenance mode in 2016, we should remove 'File-New RichFaces Project' and have RichFaces available in the Software/Update tab much like Seam. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18869: -------------------------------------- -1 on pointing to Thym snaphots. We can probably use the release repo for Thym once we do the first release soon. I guess we prefer our own mirrors over Eclipse.org infrastructure for builds. In that case Jenkins job to update and with the generic URL seems the best solution to me > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 December 2014