September 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3139: ------------------------------------ Assignee: Denis Golovin > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16868) Resizing of Cordova Plugin Discovery dialog doesn't work

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16868?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16868: --------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.CR1) > Resizing of Cordova Plugin Discovery dialog doesn't work > -------------------------------------------------------- > > Key: JBIDE-16868 > URL: https://issues.jboss.org/browse/JBIDE-16868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux > Reporter: Vlado Pakan > Assignee: Denis Golovin > Fix For: 4.3.x > > > Resizing of this dialog is very slow or doesn't work at all. > Try to resize it by mouse cursor for bigger distance and dialog is resized only a little and it takes too much time -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16868) Resizing of Cordova Plugin Discovery dialog doesn't work

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16868?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16868: -------------------------------------- sure..but that is a larger implementation because it affects search etc. > Resizing of Cordova Plugin Discovery dialog doesn't work > -------------------------------------------------------- > > Key: JBIDE-16868 > URL: https://issues.jboss.org/browse/JBIDE-16868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux > Reporter: Vlado Pakan > Assignee: Denis Golovin > Fix For: 4.3.x > > > Resizing of this dialog is very slow or doesn't work at all. > Try to resize it by mouse cursor for bigger distance and dialog is resized only a little and it takes too much time -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16868) Resizing of Cordova Plugin Discovery dialog doesn't work

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16868?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16868: --------------------------------------- There is no way to improve it unless we limit number of items that displayed by default and add button 'Show more...'. > Resizing of Cordova Plugin Discovery dialog doesn't work > -------------------------------------------------------- > > Key: JBIDE-16868 > URL: https://issues.jboss.org/browse/JBIDE-16868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux > Reporter: Vlado Pakan > Assignee: Denis Golovin > Fix For: 4.2.0.CR1 > > > Resizing of this dialog is very slow or doesn't work at all. > Try to resize it by mouse cursor for bigger distance and dialog is resized only a little and it takes too much time -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17550) When Install/Update button pressed no progress reported about installation preparation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17550?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17550: ---------------------------------- Labels: f2f2014 respin-a (was: f2f2014) > When Install/Update button pressed no progress reported about installation preparation > -------------------------------------------------------------------------------------- > > Key: JBIDE-17550 > URL: https://issues.jboss.org/browse/JBIDE-17550 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: f2f2014, respin-a > Fix For: 4.2.0.CR1 > > > When big features like ADT or set of features requested to be installed from central there is no indication in eclipse by any means that something is going on. Meantime central calls > {code} > computeInstallableUnits(monitor.newChild(50)); > {code} > and > {code}resolveInstall(monitor.newChild(50));{code} > which can take considerable amount of time. > I think progress for Preparation to install requested features should be visible in eclipse. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18165) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18165?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-18165. ----------------------------------- Resolution: Done parent pom version updated to 4.2.0.CR2-SNAPSHOT > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central] > --------------------------------------------------- > > Key: JBIDE-18165 > URL: https://issues.jboss.org/browse/JBIDE-18165 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Mickael Istria > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Central]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18167) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Freemarker]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18167?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-18167. ----------------------------------- Resolution: Done parent pom version updated to 4.2.0.CR2-SNAPSHOT > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Freemarker] > ------------------------------------------------------ > > Key: JBIDE-18167 > URL: https://issues.jboss.org/browse/JBIDE-18167 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Mickael Istria > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Freemarker]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 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.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3139: --------------------------------- Fix Version/s: 8.0.0.CR1 > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18239: ---------------------------------------- I don't see the difference between what's suggested here, and using 0.0.0 in target files. > Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18239 > URL: https://issues.jboss.org/browse/JBIDE-18239 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.). > We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG. > These would be produced as new zips using the JBT aggregate builder: > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ > Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18239: ------------------------------- Summary: Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site (was: Create new update site zip (rather than target platform zip) for JBT content needed for Central/EA site) > Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18239 > URL: https://issues.jboss.org/browse/JBIDE-18239 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.). > We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG. > These would be produced as new zips using the JBT aggregate builder: > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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