July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19546: --------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.3.0.CR1 > > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20236) Batch New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20236?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20236: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/434 (was: https://github.com/jbosstools/jbosstools-website/pull/432) > Batch New and Noteworthy for 4.3.0.Beta2 > ---------------------------------------- > > Key: JBIDE-20236 > URL: https://issues.jboss.org/browse/JBIDE-20236 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Batch is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Batch by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20236) Batch New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20236?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-20236 at 7/15/15 3:05 PM: ----------------------------------------------------------------- There is a PR for features already pushed to master for Beta2 - https://github.com/jbosstools/jbosstools-website/pull/434 One more feature (QuickFixes) is still in progress - JBIDE-19266. There is a good chance it will be done by Beta2 code freeze. If so then I will create a separate PR (if this one is merged) to update the current N&N. was (Author: akazakov): There is a PR for features already pushed to master for Beta2 - https://github.com/jbosstools/jbosstools-website/pull/432 One more feature (QuickFixes) is still in progress - JBIDE-19266. There is a good chance it will be done by Beta2 code freeze. If so then I will create a separate PR (if this one is merged) to update the current N&N. > Batch New and Noteworthy for 4.3.0.Beta2 > ---------------------------------------- > > Key: JBIDE-20236 > URL: https://issues.jboss.org/browse/JBIDE-20236 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Batch is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Batch by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20283) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices]

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20283?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick closed JBIDE-20283. ------------------------------------- Resolution: Done Branch. Done. Update master pom to 4.3.0.CR1-SNAPSHOT of parent. Done. > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-20283 > URL: https://issues.jboss.org/browse/JBIDE-20283 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Webservices]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. 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 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20283) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices]

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20283?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick reassigned JBIDE-20283: ----------------------------------------- Assignee: Brian Fitzpatrick > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices] > --------------------------------------------------------- > > Key: JBIDE-20283 > URL: https://issues.jboss.org/browse/JBIDE-20283 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Webservices]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. 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 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20281) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Birt]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20281?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-20281. --------------------------------- Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Birt] > -------------------------------------------------- > > Key: JBIDE-20281 > URL: https://issues.jboss.org/browse/JBIDE-20281 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Birt]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. 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 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, 11 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20213?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20213: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.CR1) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [LiveReload] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20213 > URL: https://issues.jboss.org/browse/JBIDE-20213 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [LiveReload]: 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 LiveReload 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20033) Standalone browsersim build produces two zip archives

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20033?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20033: ------------------------------- Fix Version/s: 4.3.x > Standalone browsersim build produces two zip archives > ----------------------------------------------------- > > Key: JBIDE-20033 > URL: https://issues.jboss.org/browse/JBIDE-20033 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > > After local build of standalone browsersim I have jbosstools-4.3.0.Beta2-browsersim.zip and org.jboss.tools.browsersim-standalone-3.7.0-SNAPSHOT.zip. Both files has equal content. We don't need zip archive without standalone. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20033) Standalone browsersim build produces two zip archives

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20033?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20033: ------------------------------- Fix Version/s: (was: 4.3.0.CR1) > Standalone browsersim build produces two zip archives > ----------------------------------------------------- > > Key: JBIDE-20033 > URL: https://issues.jboss.org/browse/JBIDE-20033 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > > After local build of standalone browsersim I have jbosstools-4.3.0.Beta2-browsersim.zip and org.jboss.tools.browsersim-standalone-3.7.0-SNAPSHOT.zip. Both files has equal content. We don't need zip archive without standalone. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14610: ------------------------------- Labels: documentation (was: ) > Design http://download.jboss.org/jbosstools structure > ----------------------------------------------------- > > Key: JBIDE-14610 > URL: https://issues.jboss.org/browse/JBIDE-14610 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: documentation > Fix For: 4.3.0.CR1 > > > We have several types of objects which names should be presented in site stucture: > # Project: jbosstools > # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final > # Subproject: core, soatools > # Module: base, javaee, central, freemarker and etc. > # Distribution Type: updates|builds > # Bits Type: stable|development|nightly > # Targeted Eclipse: indigo|juno|kepler > # You name it ... > Now we mostly use following patterns to publish nightly bits, but not always and not for every project: > # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\} > # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure > # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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