[JBoss JIRA] (JBIDE-21491) For JBIDE 4.3.1.Beta2: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21491?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21491.
------------------------------
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch
> -------------------------------------------
>
> Key: JBIDE-21491
> URL: https://issues.jboss.org/browse/JBIDE-21491
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2: 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...]
> See also: JBDS-3584
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21491) For JBIDE 4.3.1.Beta2: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21491?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-21491.
--------------------------------
Assignee: Nick Boldt
Resolution: Done
Aerogear and Arquillian are disabled (no new commits).
Everyone else should be building soon via http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch
> -------------------------------------------
>
> Key: JBIDE-21491
> URL: https://issues.jboss.org/browse/JBIDE-21491
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2: 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...]
> See also: JBDS-3584
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21529) Properties view: Columns of OpenShift resources in tabbed properties are too wide
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21529?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21529 at 1/21/16 10:23 PM:
-------------------------------------------------------------------------
For adjusting columns width to the table size, our plugins have 6 (six!!!) copies of identical(!) AutoResizeTableLayout classes. I hope that this class may solve the problem. But is not it a good time to put it to org.jboss.tools.common.ui visible to all plugins. [~adietish], please consider if AutoResizeTableLayout may be good for TableViewerBuilder.
was (Author: scabanovich):
For adjusting column width to the table size, our plugins have 6 (six!!!) copies of identical(!) AutoResizeTableLayout classes. I hope that this class may solve the problem. But is not it a good time to put it to org.jboss.tools.common.ui visible to all plugins. [~adietish], please consider if AutoResizeTableLayout may be good for TableViewerBuilder.
> Properties view: Columns of OpenShift resources in tabbed properties are too wide
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21529
> URL: https://issues.jboss.org/browse/JBIDE-21529
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: properties
>
> In new tabbed properties overview of OpenShift resources there is a table listing selected OpenShift resource, e.g. pods, builds etc. Columns in this table are too wide by default and their width exceed few times content of the column. It makes necessary to scroll or resize columns, what make it less user friendly. Columns could fit more to length of content of the column by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21529) Properties view: Columns of OpenShift resources in tabbed properties are too wide
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21529?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21529:
-----------------------------------------------
For adjusting column width to the table size, our plugins have 6 (six!!!) copies of identical(!) AutoResizeTableLayout classes. I hope that this class may solve the problem. But is not it a good time to put it to org.jboss.tools.common.ui visible to all plugins. [~adietish], please consider if AutoResizeTableLayout may be good for TableViewerBuilder.
> Properties view: Columns of OpenShift resources in tabbed properties are too wide
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21529
> URL: https://issues.jboss.org/browse/JBIDE-21529
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: properties
>
> In new tabbed properties overview of OpenShift resources there is a table listing selected OpenShift resource, e.g. pods, builds etc. Columns in this table are too wide by default and their width exceed few times content of the column. It makes necessary to scroll or resize columns, what make it less user friendly. Columns could fit more to length of content of the column by default.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21531) New Application wizard: Template parameter with empty/generated value has wrong validation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21531?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21531:
-----------------------------------------------
[~adietish], please take a look at the pull request.
> New Application wizard: Template parameter with empty/generated value has wrong validation
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21531
> URL: https://issues.jboss.org/browse/JBIDE-21531
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> In New OpenShift application wizard on the wizard page with template parameters when I select to edit a parameter with empty ("") or generated ("(generated)") value, text widget to enter new value is marked with error validation mark, that new value is required, but OK button is enabled. It either should be without validation mark or OK button should be disabled, if confirmation is meant to be allowed only for a new value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21500) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21500?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-21500.
-------------------------------
Resolution: Done
Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
> -------------------------------------------------------
>
> Key: JBIDE-21500
> URL: https://issues.jboss.org/browse/JBIDE-21500
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [OpenShift]: 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 OpenShift 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, 4 months
[JBoss JIRA] (JBIDE-21500) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21500?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21500:
-----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
> -------------------------------------------------------
>
> Key: JBIDE-21500
> URL: https://issues.jboss.org/browse/JBIDE-21500
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [OpenShift]: 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 OpenShift 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, 4 months