December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13450) New SSH Key Wizard: add a passphare confirmation field

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13450?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13450: ------------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > New SSH Key Wizard: add a passphare confirmation field > ------------------------------------------------------ > > Key: JBIDE-13450 > URL: https://issues.jboss.org/browse/JBIDE-13450 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > > There's a single passphare field when creating a new SSH Key Pair. This form could have a second "Confirm passphare" field to check that the user did not make a typo when typing his passphrase. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13450) New SSH Key Wizard: add a passphare confirmation field

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13450?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13450: ------------------------------------------ thanks [~rawb], very nice! pushed upstream master. > New SSH Key Wizard: add a passphare confirmation field > ------------------------------------------------------ > > Key: JBIDE-13450 > URL: https://issues.jboss.org/browse/JBIDE-13450 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > > There's a single passphare field when creating a new SSH Key Pair. This form could have a second "Confirm passphare" field to check that the user did not make a typo when typing his passphrase. -- 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, 7 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 updated JBIDE-16217: ---------------------------------- Description: 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...] was: 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 jbosstools-4.1.x 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...] > 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 > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15073) LiveReload for workspace resources should be shown under 'Show In' in context menu

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15073?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15073: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > LiveReload for workspace resources should be shown under 'Show In' in context menu > ---------------------------------------------------------------------------------- > > Key: JBIDE-15073 > URL: https://issues.jboss.org/browse/JBIDE-15073 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta2 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > For deployed apps, can right-click app in servers tab and click Show In > Web Browser via LiveReload Server. Easy :) > For workspace resources, can right-click index.html file in project explorer tab and select Open With > Web Browser via LiveReload Server. But then if want to open file in editor have to click again Open With > JBoss Tools editor. So the file's default association with editors and browsers has to keep changing as I open it with LiveReload or an editor. > A better workflow for workspace resources would be if can right-click index.html file in project explorer tab and select *Show In* > Web Browser via LiveReload Server. This would be good because: > * Would match 'Show In' for deployed apps > * Would leave association of file with one editor and double-clicking file would always result in opening in editor > * Would mean not having to reset file association with editor after opening in browser with LiveReload server -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14503) LiveReload server information in the Servers View

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14503?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14503: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > LiveReload server information in the Servers View > ------------------------------------------------- > > Key: JBIDE-14503 > URL: https://issues.jboss.org/browse/JBIDE-14503 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > The LiveReload server should display information in the Server Views, such as: > - number of connected browsers > - proxy enabled > - remote connections enabled > - script injection enabled > - the IP address the Proxy is listening on -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15519) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15519?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15519: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15519 > URL: https://issues.jboss.org/browse/JBIDE-15519 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > Move all *.ui.* dependencies from livereload.core to livereload.ui -- 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, 7 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 updated JBIDE-16217: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > 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 > 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 jbosstools-4.1.x 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14670) Automatically notify browsers after user edited a file, even *before* saving it

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14670?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14670: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Automatically notify browsers after user edited a file, even *before* saving it > ------------------------------------------------------------------------------- > > Key: JBIDE-14670 > URL: https://issues.jboss.org/browse/JBIDE-14670 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > The idea is to notify the livereload server which in turn will notify browser that are connected to the proxy to access local files. when the browser will send a request to the proxy, this latter one will not return the content of the resource on the FS but rather, it will first check if there's an open editor for that resource and then, it will send the working copy instead. > This should be an option in the LiveReload Proxy Configuration -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14868) livereload should change state when notifications are being sent out

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14868?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14868: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > livereload should change state when notifications are being sent out > -------------------------------------------------------------------- > > Key: JBIDE-14868 > URL: https://issues.jboss.org/browse/JBIDE-14868 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > when livereload notices changes it would be nice if its "synchronized" state was set to unknown or publishing... and when notifications have been sent then it goes to "synchronized" -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14949) Enable support for LiveReload when deploying on OpenShift

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14949?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14949: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Enable support for LiveReload when deploying on OpenShift > --------------------------------------------------------- > > Key: JBIDE-14949 > URL: https://issues.jboss.org/browse/JBIDE-14949 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > -- 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, 7 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