January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21514) Old webpages are displayed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21514?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21514. --------------------------------- Done. I can no longer reproduce the problem. Closing. > Old webpages are displayed > -------------------------- > > Key: JBIDE-21514 > URL: https://issues.jboss.org/browse/JBIDE-21514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Almost everybody in our team (QA in Brno) is seeing old website tools.jboss.org (http://i.imgur.com/mJ0WUIU.png). Only one who is still getting new design is mmalina (we have no idea why... he is on same subnet). rawagner claims that yesterday everything was ok. > Somebody is able to get new design in private window... but is seems completely random. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21514) Old webpages are displayed

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21514?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21514: ---------------------------------- Fix Version/s: 4.3.1.Beta2 > Old webpages are displayed > -------------------------- > > Key: JBIDE-21514 > URL: https://issues.jboss.org/browse/JBIDE-21514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Almost everybody in our team (QA in Brno) is seeing old website tools.jboss.org (http://i.imgur.com/mJ0WUIU.png). Only one who is still getting new design is mmalina (we have no idea why... he is on same subnet). rawagner claims that yesterday everything was ok. > Somebody is able to get new design in private window... but is seems completely random. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21514) Old webpages are displayed

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21514?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-21514. ----------------------------------- Resolution: Done Problem resolved by Vladimir Vasilev: Magnolia sites had been moved to some new hardware and 'tools' have duplicate entries. > Old webpages are displayed > -------------------------- > > Key: JBIDE-21514 > URL: https://issues.jboss.org/browse/JBIDE-21514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Almost everybody in our team (QA in Brno) is seeing old website tools.jboss.org (http://i.imgur.com/mJ0WUIU.png). Only one who is still getting new design is mmalina (we have no idea why... he is on same subnet). rawagner claims that yesterday everything was ok. > Somebody is able to get new design in private window... but is seems completely random. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21514) Old webpages are displayed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21514?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21514: --------------------------------------- It seems to be resolved. There are two name servers and each had a different record: {code} $ dig tools.jboss.org ; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7 <<>> tools.jboss.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26373 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tools.jboss.org. IN A ;; ANSWER SECTION: tools.jboss.org. 20 IN A 10.5.105.17 tools.jboss.org. 20 IN A 10.4.129.25 ;; AUTHORITY SECTION: jboss.org. 254 IN NS ns01.intranet.prod.int.phx2.redhat.com. jboss.org. 254 IN NS ns02.intranet.prod.int.phx2.redhat.com. ;; ADDITIONAL SECTION: ns01.intranet.prod.int.phx2.redhat.com. 70 IN A 10.5.30.45 ns02.intranet.prod.int.phx2.redhat.com. 161 IN A 10.5.30.46 ;; Query time: 64 msec ;; SERVER: 10.34.32.1#53(10.34.32.1) ;; WHEN: Thu Jan 21 15:16:51 CET 2016 ;; MSG SIZE rcvd: 179 {code} But now it no longer happens. >From vvasilev: {quote} Hi, I moved the magnolia sites to new IP and hardware load balancer Looks like tools had two records. Now this is fixed. It will take 5-15 minutes to be visible world wide Sorry for the troubles {quote} > Old webpages are displayed > -------------------------- > > Key: JBIDE-21514 > URL: https://issues.jboss.org/browse/JBIDE-21514 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Xavier Coulon > Priority: Critical > > Almost everybody in our team (QA in Brno) is seeing old website tools.jboss.org (http://i.imgur.com/mJ0WUIU.png). Only one who is still getting new design is mmalina (we have no idea why... he is on same subnet). rawagner claims that yesterday everything was ok. > Somebody is able to get new design in private window... but is seems completely random. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21506) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21506?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-21506: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [BrowserSim] > -------------------------------------------------------- > > Key: JBIDE-21506 > URL: https://issues.jboss.org/browse/JBIDE-21506 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [BrowserSim]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (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.1.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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 BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21527) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21527: ------------------------------------- Summary: Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH Key: JBIDE-21527 URL: https://issues.jboss.org/browse/JBIDE-21527 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Assignee: Viacheslav Kabanovich Priority: Minor Fix For: 4.3.1.Beta2 In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21527) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21527?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21527: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21527 > URL: https://issues.jboss.org/browse/JBIDE-21527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21527) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21527?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21527. ----------------------------------- Resolution: Done > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21527 > URL: https://issues.jboss.org/browse/JBIDE-21527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21526) Deploy from existing project git constraints are too stringent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21526?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21526: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > Deploy from existing project git constraints are too stringent > -------------------------------------------------------------- > > Key: JBIDE-21526 > URL: https://issues.jboss.org/browse/JBIDE-21526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha1 > > > There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: > - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted > - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21494) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21494?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-21494: ---------------------------------------------- Assignee: Konstantin Marmalyukov > For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE] > ------------------------------------------------- > > Key: JBIDE-21494 > URL: https://issues.jboss.org/browse/JBIDE-21494 > 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.1.Beta2 > > > For JBIDE 4.3.1.Beta2 [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (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.1.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta2x > git push origin jbosstools-4.3.1.Beta2x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and > * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016