December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16119) CordovaSim: Need to make panels design more user-friendly

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16119?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-16119: -------------------------------- Fix Version/s: 4.2.0.Alpha1 > CordovaSim: Need to make panels design more user-friendly > --------------------------------------------------------- > > Key: JBIDE-16119 > URL: https://issues.jboss.org/browse/JBIDE-16119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Environment: Mac OSX lion > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha1 > > Attachments: CordovaSim.jpg > > > See video, trying to get access to the accelerometer drop-down > http://www.screencast.com/t/RBwdqXxeCsHJ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16100. --------------------------------- nothing to verify (bcs. of rejection) > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Environment: Version: 7.1.0.CR1 > Build id: CR1-v20131124-0717-B560 > Build date: 20131124-0717 > Reporter: Michelle Murray > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.CR1 > > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16221) Application wizard: dont know what field is erroring when "use existing" is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16221?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16221: ------------------------------------- Attachment: missing-decoration.png > Application wizard: dont know what field is erroring when "use existing" is checked > ----------------------------------------------------------------------------------- > > Key: JBIDE-16221 > URL: https://issues.jboss.org/browse/JBIDE-16221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: missing-decoration.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16221) Application wizard: dont know what field is erroring when "use existing" is checked

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16221: ---------------------------------------- Summary: Application wizard: dont know what field is erroring when "use existing" is checked Key: JBIDE-16221 URL: https://issues.jboss.org/browse/JBIDE-16221 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Alpha1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 4.2.x Attachments: missing-decoration.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16220: ------------------------------- Description: Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs. {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} "git submodule" started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating with the commit recorded in the superproject's gitlink). {code} Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. was: Git 1.8.2 now includes an option to have submodules track a branch tip, rather than specific commit IDs. {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} "git submodule" started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating with the commit recorded in the superproject's gitlink). {code} Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. > create an all-in-one build for JBT projects, using submodules > ------------------------------------------------------------- > > Key: JBIDE-16220 > URL: https://issues.jboss.org/browse/JBIDE-16220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs. > {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} > "git submodule" started learning a new mode to integrate with the > tip of the remote branch (as opposed to integrating with the commit > recorded in the superproject's gitlink). > {code} > Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. > If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16220: ------------------------------- Description: Git 1.8.2 now includes an option to have submodules track a branch tip, rather than specific commit IDs. {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} "git submodule" started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating with the commit recorded in the superproject's gitlink). {code} Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. was: Git 1.8.2 now includes an option to have submodules track a branch tip, rather than specific commit IDs. {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} "git submodule" started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating with the commit recorded in the superproject's gitlink). {code} Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. If we can get Git 1.8.2 installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. > create an all-in-one build for JBT projects, using submodules > ------------------------------------------------------------- > > Key: JBIDE-16220 > URL: https://issues.jboss.org/browse/JBIDE-16220 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Git 1.8.2 now includes an option to have submodules track a branch tip, rather than specific commit IDs. > {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} > "git submodule" started learning a new mode to integrate with the > tip of the remote branch (as opposed to integrating with the commit > recorded in the superproject's gitlink). > {code} > Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. > If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16218) Project selection dialog on import should not list closed projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16218?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-16218: ---------------------------------------- Assignee: Andre Dietisheim > Project selection dialog on import should not list closed projects > ------------------------------------------------------------------ > > Key: JBIDE-16218 > URL: https://issues.jboss.org/browse/JBIDE-16218 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > When selecting a project while creating an OpenShift application, the dialog shows all projects, including the closed ones. Those later ones should be filtered out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16119) CordovaSim: Need to make panels design more user-friendly

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16119?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-16119: -------------------------------- Summary: CordovaSim: Need to make panels design more user-friendly (was: CordovaSim "windows" will not open) > CordovaSim: Need to make panels design more user-friendly > --------------------------------------------------------- > > Key: JBIDE-16119 > URL: https://issues.jboss.org/browse/JBIDE-16119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Environment: Mac OSX lion > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: CordovaSim.jpg > > > See video, trying to get access to the accelerometer drop-down > http://www.screencast.com/t/RBwdqXxeCsHJ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16220: ---------------------------------- Summary: create an all-in-one build for JBT projects, using submodules Key: JBIDE-16220 URL: https://issues.jboss.org/browse/JBIDE-16220 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Git 1.8.2 now includes an option to have submodules track a branch tip, rather than specific commit IDs. {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} "git submodule" started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating with the commit recorded in the superproject's gitlink). {code} Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. If we can get Git 1.8.2 installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16217) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16217?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-16217. --------------------------------- Assignee: Xavier Coulon Resolution: Done > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload] > --------------------------------------------------------- > > Key: JBIDE-16217 > URL: https://issues.jboss.org/browse/JBIDE-16217 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha2 > > > For JBIDE 4.2.0.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > 1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0. > {code}mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT{code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1-SNAPSHOT; > {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged){code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code}git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x{code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 2013