November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21137) Consistency of sorting in EmbedCartridgesJob

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-21137: --------------------------------------------- Summary: Consistency of sorting in EmbedCartridgesJob Key: JBIDE-21137 URL: https://issues.jboss.org/browse/JBIDE-21137 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Final Environment: Sorting with CartridgeAddRemovePriorityComparator implies that cartridges should be stored in IApplication in a specific order, for instance, "mysql" should precede all other cartridges. If Edit Embedded Cartridges wizard is run once, the desirable order is guaranteed. However, if wizard is run twice, with "postgresql" selected on the first run and "mysql" added on the second run, the cartridges will be added to IApplication unsorted by the comparator. Reporter: Viacheslav Kabanovich Assignee: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- Happy to see movement on this one again, but I don't grok why you need to ask all this. using skipTest to disable globally all downloads via the normal download plugin is just wrong imo. > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20999) Application wizard: Validation error for a new label (in Resource Labels page) is not accurate

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20999?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20999: -------------------------------- Priority: Minor (was: Major) > Application wizard: Validation error for a new label (in Resource Labels page) is not accurate > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-20999 > URL: https://issues.jboss.org/browse/JBIDE-20999 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > In Resource Label dialog opened from New OpenShift Application wizard there is a validation error description informing users about correct form of a new label. This description is not accurate. > First inaccurate description is the one with empty label name/value (if one of them is empty). There is missing information about possible characters (underscore, slash). > Label value validation error description does not contain information about underscore. > Also there should be mentioned that also upper case letters are allowed - in validation error description are mentioned only lower case letters. > For more reference about proper format of a label see kubernetes doc at http://kubernetes.io/v1.0/docs/user-guide/labels.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20999) Application wizard: Validation error for a new label (in Resource Labels page) is not accurate

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20999?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20999. --------------------------------- Resolution: Done Fixed in master/4.3.x > Application wizard: Validation error for a new label (in Resource Labels page) is not accurate > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-20999 > URL: https://issues.jboss.org/browse/JBIDE-20999 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > In Resource Label dialog opened from New OpenShift Application wizard there is a validation error description informing users about correct form of a new label. This description is not accurate. > First inaccurate description is the one with empty label name/value (if one of them is empty). There is missing information about possible characters (underscore, slash). > Label value validation error description does not contain information about underscore. > Also there should be mentioned that also upper case letters are allowed - in validation error description are mentioned only lower case letters. > For more reference about proper format of a label see kubernetes doc at http://kubernetes.io/v1.0/docs/user-guide/labels.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18876: ------------------------------------ Outcome from today's build.next call is that we'd like to see statistics on how often and for whom this problem occurs. If every time it happens you ( [~dgolovin] ) could jot down some details here or in a Google spreadsheet, we can better prioritize how urgent this change is. > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18876: ------------------------------- Priority: Minor (was: Major) > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15332: ------------------------------------ In discussion today we decided we could: 1. ask on jbosstools-dev@ who, if anyone, needs to download upstream libraries/runtimes/jars using something like maven-dependency-plugin, and if they've already set <skip>false</skip> on those plugins' builds, eg., https://github.com/jbosstools/jbosstools-livereload/pull/54/ 2. ask on jbosstools-dev@ who, if anyone, is using any of these variables: * <swtbot.test.skip>true</swtbot.test.skip> * <skipRequirements>${skipTests}</skipRequirements> * <skipPrivateRequirements>true</skipPrivateRequirements> * <skipTestsWithPrivateRequirements>${skipPrivateRequirements}</skipTestsWithPrivateRequirements> 3. remove all the unneeded/unused skip*Requirements variables 4. dedupe the declaration of maven-download-plugin in parent pom ( https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... ) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15332 at 11/25/15 12:33 PM: --------------------------------------------------------------- In discussion today we decided we could: 1. ask on jbosstools-dev@ who, if anyone, needs to download upstream libraries/runtimes/jars using something like maven-dependency-plugin, and if they've already set <skip>false</skip> on those plugins' builds, eg., https://github.com/jbosstools/jbosstools-livereload/pull/54/ 2. ask on jbosstools-dev@ who, if anyone, is using any of these variables: * <swtbot.test.skip>true</swtbot.test.skip> * <skipRequirements>$\{skipTests}</skipRequirements> * <skipPrivateRequirements>true</skipPrivateRequirements> * <skipTestsWithPrivateRequirements>$\{skipPrivateRequirements}</skipTestsWithPrivateRequirements> 3. remove all the unneeded/unused skip*Requirements variables 4. dedupe the declaration of maven-download-plugin in parent pom ( https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... ) was (Author: nickboldt): In discussion today we decided we could: 1. ask on jbosstools-dev@ who, if anyone, needs to download upstream libraries/runtimes/jars using something like maven-dependency-plugin, and if they've already set <skip>false</skip> on those plugins' builds, eg., https://github.com/jbosstools/jbosstools-livereload/pull/54/ 2. ask on jbosstools-dev@ who, if anyone, is using any of these variables: * <swtbot.test.skip>true</swtbot.test.skip> * <skipRequirements>${skipTests}</skipRequirements> * <skipPrivateRequirements>true</skipPrivateRequirements> * <skipTestsWithPrivateRequirements>${skipPrivateRequirements}</skipTestsWithPrivateRequirements> 3. remove all the unneeded/unused skip*Requirements variables 4. dedupe the declaration of maven-download-plugin in parent pom ( https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... ) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- I believe that grouping items with Group widget or using a title would be a good solution. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20609: ---------------------------------------- It's hard to understand what I'm seeing in that page and what I can do there. What about adding the following titles to these two lists: 1) Installed EA units: ... 2) Available sites for the installed EA: ... or something like that. Can we get some help form UX team? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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