June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22475) For JBIDE 4.4.0.Final: Prepare for Final/GA

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22475: ---------------------------------- Summary: For JBIDE 4.4.0.Final: Prepare for Final/GA Key: JBIDE-22475 URL: https://issues.jboss.org/browse/JBIDE-22475 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.4.0.Final For JBIDE 4.4.0.Final: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.x git push origin jbosstools-4.4.x {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) {code} mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT {code} 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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-3919 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22432) Server Adapter wizard: If oc binary can't be located, then nothing happens and NPE is logged to console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22432?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22432: ------------------------------------------ [~jeffmaury] Thx! merged into master > Server Adapter wizard: If oc binary can't be located, then nothing happens and NPE is logged to console > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22432 > URL: https://issues.jboss.org/browse/JBIDE-22432 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.0.Final > > > If oc binary can't be located (default configuration and not found in path), then an internal error is spanwed when trying to create a server adapter -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22472) Improve UI of per-module zip settings

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22472?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22472: ------------------------------------- will look into this. > Improve UI of per-module zip settings > ------------------------------------- > > Key: JBIDE-22472 > URL: https://issues.jboss.org/browse/JBIDE-22472 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > This is a follow up of JBIDE-22157 and JBIDE-20577. > When you were implementing JBIDE-22157, you asked me for feedback which I gave you but there was no further reply from you: > https://github.com/jbosstools/jbosstools-server/pull/412 > {quote} > what happens if I select to zip all? the new column does not apply then? it would be good to make this obvious somehow. > also, could it be a checkbox instead of false/true? > {quote} > 1) Could we have checkboxes instead of true/false? > 2) On a new server adapter, a "false" actually means "see default above" - once you change the default to compress all, each "false" will change to "true". But once you change a module to true and then back to false, changing the default will no longer affect the module settings anymore. This is counter intuitive. > So what would make more sense in my opinion is to have checkboxes for each module and then perhaps a link called "all" at the column header? And get rid of the default settings? What do you think? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22380) New Application wizard: project is not preselected (nor can you select any) if launched from explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22380?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22380. -------------------------------------- Resolution: Cannot Reproduce Bug resolving as I and [~mlabuda] couldnt reproduce this lately. > New Application wizard: project is not preselected (nor can you select any) if launched from explorer > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22380 > URL: https://issues.jboss.org/browse/JBIDE-22380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Final > > Attachments: project-not-preselected.png > > Original Estimate: 8 minutes > Remaining Estimate: 8 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) Sprint: (was: devex #115 May 2016) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Sprint: (was: devex #115 May 2016) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - PMC/Findbugs > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-22473: --------------------------------------------- Assignee: Viacheslav Kabanovich > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-295: ---------------------------------- [~apodhrad] - I think the spirit of the Jira is satisfied with your use of the JBDS-specific tycho testing support. I was just thinking of adding a quick test to the JBDSIS build in order to get some level of confidence before testing it. > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBTIS-295 > URL: https://issues.jboss.org/browse/JBTIS-295 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-726) Generate a p2diff report with the target platform build - ref JBIDE-22308

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-726?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-726. ---------------------------- Fix Version/s: 4.4.0.Alpha1-TP Resolution: Done p2diff report files now generated. https://github.com/jbosstools/jbosstools-integration-stack/commit/79c264f... > Generate a p2diff report with the target platform build - ref JBIDE-22308 > ------------------------------------------------------------------------- > > Key: JBTIS-726 > URL: https://issues.jboss.org/browse/JBTIS-726 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.0.Alpha1-TP > > > Generate a p2diff report for the EA and released JBTIS TP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-726) Generate a p2diff report with the target platform build - ref JBIDE-22308

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-726: -------------------------------- Summary: Generate a p2diff report with the target platform build - ref JBIDE-22308 Key: JBTIS-726 URL: https://issues.jboss.org/browse/JBTIS-726 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.4.0.Alpha1-TP Reporter: Paul Leacu Assignee: Paul Leacu Generate a p2diff report for the EA and released JBTIS TP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016