April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19630: ------------------------------------- Affects Version/s: 4.3.0.Alpha2 > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19630) v3 connections: store to default url based persistence vs custom json format

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19630: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > v3 connections: store to default url based persistence vs custom json format > ---------------------------------------------------------------------------- > > Key: JBIDE-19630 > URL: https://issues.jboss.org/browse/JBIDE-19630 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19611) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19611?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-19611. ------------------------------------------ Resolution: Done > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE] > -------------------------------------------------- > > Key: JBIDE-19611 > URL: https://issues.jboss.org/browse/JBIDE-19611 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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 from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19621) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19621?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-19621. ------------------------------------------ Resolution: Done > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [BrowserSim] > --------------------------------------------------------- > > Key: JBIDE-19621 > URL: https://issues.jboss.org/browse/JBIDE-19621 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [BrowserSim]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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 from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19624) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19624?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-19624. ------------------------------- Assignee: Fred Bricon Resolution: Done Done. parent set to 4.3.0.Beta1-SNAPSHOT in master > For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central] > ------------------------------------------------------ > > Key: JBIDE-19624 > URL: https://issues.jboss.org/browse/JBIDE-19624 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha2 > > > For JBIDE 4.3.0.Alpha2 [Central]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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 from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT) > mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha2x > git push origin jbosstools-4.3.0.Alpha2x > {code} > 5. Close (do not resolve) this JIRA when done. > [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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19626: ------------------------------------- Attachment: connection-error.png > Explorer: If you have an erroring v3 connection, refresh has no visible effect > ------------------------------------------------------------------------------ > > Key: JBIDE-19626 > URL: https://issues.jboss.org/browse/JBIDE-19626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: connection-error.png > > > # ASSERT: make sure that you have a connection to an openshift v3 server under your full control > # ASSERT: make sure your connection to it was not unfolded/loaded yet > # EXEC: shut down your local openshift v3 server so that it does not answer > # EXEC: unfold your connection > # ASSERT: the connection shows an error "child" > !connection-error.png! > # EXEC: re-start your local v3 server > # EXEC: pick "Refresh" from the context menu of your connection > Result: > Nothing happens, the error "child" stays -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19626: ------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Explorer: If you have an erroring v3 connection, refresh has no visible effect > ------------------------------------------------------------------------------ > > Key: JBIDE-19626 > URL: https://issues.jboss.org/browse/JBIDE-19626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: connection-error.png > > > # ASSERT: make sure that you have a connection to an openshift v3 server under your full control > # ASSERT: make sure your connection to it was not unfolded/loaded yet > # EXEC: shut down your local openshift v3 server so that it does not answer > # EXEC: unfold your connection > # ASSERT: the connection shows an error "child" > !connection-error.png! > # EXEC: re-start your local v3 server > # EXEC: pick "Refresh" from the context menu of your connection > Result: > Nothing happens, the error "child" stays -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19626: ------------------------------------- Attachment: (was: connection-error.png) > Explorer: If you have an erroring v3 connection, refresh has no visible effect > ------------------------------------------------------------------------------ > > Key: JBIDE-19626 > URL: https://issues.jboss.org/browse/JBIDE-19626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: connection-error.png > > > # ASSERT: make sure that you have a connection to an openshift v3 server under your full control > # ASSERT: make sure your connection to it was not unfolded/loaded yet > # EXEC: shut down your local openshift v3 server so that it does not answer > # EXEC: unfold your connection > # ASSERT: the connection shows an error "child" > !connection-error.png! > # EXEC: re-start your local v3 server > # EXEC: pick "Refresh" from the context menu of your connection > Result: > Nothing happens, the error "child" stays -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19626: ------------------------------------- Description: # ASSERT: make sure that you have a connection to an openshift v3 server under your full control # ASSERT: make sure your connection to it was not unfolded/loaded yet # EXEC: shut down your local openshift v3 server so that it does not answer # EXEC: unfold your connection # ASSERT: the connection shows an error "child" !connection-error.png! # EXEC: re-start your local v3 server # EXEC: pick "Refresh" from the context menu of your connection Result: Nothing happens, the error "child" stays was: # ASSERT: make sure that you have a connection to an openshift v3 server under your full control # ASSERT: make sure your connection to it was not unfolded/loaded yet # EXEC: shut down your local openshift v3 server so that it does not answer # EXEC: unfold your connection # ASSERT: the connection shows an error "child" # EXEC: re-start your local v3 server # EXEC: pick "Refresh" from the context menu of your connection Result: Nothing happens, the error "child" stays > Explorer: If you have an erroring v3 connection, refresh has no visible effect > ------------------------------------------------------------------------------ > > Key: JBIDE-19626 > URL: https://issues.jboss.org/browse/JBIDE-19626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: connection-error.png > > > # ASSERT: make sure that you have a connection to an openshift v3 server under your full control > # ASSERT: make sure your connection to it was not unfolded/loaded yet > # EXEC: shut down your local openshift v3 server so that it does not answer > # EXEC: unfold your connection > # ASSERT: the connection shows an error "child" > !connection-error.png! > # EXEC: re-start your local v3 server > # EXEC: pick "Refresh" from the context menu of your connection > Result: > Nothing happens, the error "child" stays -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19626) Explorer: If you have an erroring v3 connection, refresh has no visible effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19626: ------------------------------------- Attachment: connection-error.png > Explorer: If you have an erroring v3 connection, refresh has no visible effect > ------------------------------------------------------------------------------ > > Key: JBIDE-19626 > URL: https://issues.jboss.org/browse/JBIDE-19626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: connection-error.png > > > # ASSERT: make sure that you have a connection to an openshift v3 server under your full control > # ASSERT: make sure your connection to it was not unfolded/loaded yet > # EXEC: shut down your local openshift v3 server so that it does not answer > # EXEC: unfold your connection > # ASSERT: the connection shows an error "child" > !connection-error.png! > # EXEC: re-start your local v3 server > # EXEC: pick "Refresh" from the context menu of your connection > Result: > Nothing happens, the error "child" stays -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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 April 2015