June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19914) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JBT Update Sites]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19914: ---------------------------------- Summary: For JBIDE 4.3.0.Beta1: Code Freeze + Branch [JBT Update Sites] Key: JBIDE-19914 URL: https://issues.jboss.org/browse/JBIDE-19914 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: updatesite Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta1 [JBT Update Sites]: 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.Beta1 [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|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 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.Beta1-SNAPSHOT; {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Beta1-SNAPSHOT</version> </parent> {code} 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; {code} mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) or mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) {code} 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta1x git push origin jbosstools-4.3.0.Beta1x {code} 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Beta2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 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 JBT Update Sites 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, 10 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19915: ---------------------------------- Summary: For JBIDE 4.3.0.Beta1: Code Freeze + Branch [VPE] Key: JBIDE-19915 URL: https://issues.jboss.org/browse/JBIDE-19915 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta1 [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.Beta1 [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|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 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.Beta1-SNAPSHOT; {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Beta1-SNAPSHOT</version> </parent> {code} 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; {code} mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) or mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) {code} 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta1x git push origin jbosstools-4.3.0.Beta1x {code} 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Beta2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 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.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19911: ------------------------------- Affects Version/s: 4.3.0.Beta1 > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.3.0.Beta2 > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19911: ------------------------------- Fix Version/s: 4.3.0.Beta2 > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.3.0.Beta2 > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19911: ------------------------------------ See also https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.3.0.Beta2 > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19773: ------------------------------------- I forgot to apply the last PR. This is fixed now. [~rawagner], please rebuild and try again. > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19773: ------------------------------------------------ [~rawagner] it actually depends. According to the message which you see - you have old xulrunner. The only way to disable it is start eclipse with -Dorg.jboss.tools.vpe.loadxulrunner=false. For checking browser engine(and version) I'd recommend to open internal web browser, go to http://whatsmyuseragent.com and compare user agent you see with listed in my comment above. Anyway, message {quote}"Please use a fully HTML5 compliant browser in order to leverage all JBoss Central features"{quote} says that [~fbricon] does not apply https://github.com/jbosstools/jbosstools-central/pull/338 and you also have old version of website(new version supports obsolete xulrunner which is shipped by vpe). I will perform some tests on Fedora tomorrow, but also on Friday I plan to write some testcases for verifying new central. > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19773) Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do?

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19773?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19773: ------------------------------------------ I tested central on RHEL7. - with GTK3 it works. - with GTK2 central says "Please use a fully HTML5 compliant browser in order to leverage all JBoss Central features" [~kmarmaliykov] when GTK2 is used, is xulranner used too ? Or do I have to enable xulrunner explicitly somehow ? > Can Central tell the user what's wrong if gtk/swt/webkit not available so they know what to do? > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-19773 > URL: https://issues.jboss.org/browse/JBIDE-19773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > It was suggested today on build.next call by Max that it would be great if when gtk/swt/browser/webkit problems occur as a result of Central loading that we could notify the user what when wrong and suggest a solution. > Context: > {quote} > * No more handles with install-grinder https://issues.jboss.org/browse/JBIDE-19750 and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... > * SWT problem? GTK problem? xvnc/xvfb problem? > * missing webkit package on RHEL7 ? > * @mickael to ping Fred; see what is missing on RHEL7 (need GTK3 packages) > * what about x86 bundles for x86_64 platform? - https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/how_... {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19911: ----------------------------------- Description: For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. * Input: sourceSite, initialMirror (as found in .target), targetMirror * Then ** job mirros the sourceSite ** job publishes (scp) it to targetMirror ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER ** p2diff ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment was: For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. * Input: sourceSite, initialMirror (as found in .target), targetMirror * Then ** job mirros the sourceSite ** job publishes (scp) it to targetMirror ** job runs "sed s/${initialMirror}/${targetMirror}/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** git add multiple/*.target; git commit -m "Update ${initialMirror} to ${targetMirror}"; git push origin HEAD:change-${BUILD_NUMBER} ** p2diff ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19911: -------------------------------------- Summary: Create a (manual) job to update a given 3rd-party project on TP Key: JBIDE-19911 URL: https://issues.jboss.org/browse/JBIDE-19911 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Reporter: Mickael Istria For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. * Input: sourceSite, initialMirror (as found in .target), targetMirror * Then ** job mirros the sourceSite ** job publishes (scp) it to targetMirror ** job runs "sed s/${initialMirror}/${targetMirror}/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** git add multiple/*.target; git commit -m "Update ${initialMirror} to ${targetMirror}"; git push origin HEAD:change-${BUILD_NUMBER} ** p2diff ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015