August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundled Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3948: -------------------------------- Sprint: (was: devex #118 July 2016) > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundled Installer > -------------------------------------------------------------------------------------------- > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3867?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3867: -------------------------------- Sprint: (was: devex #118 July 2016) > CDK file name should include version, match file name on RHCP > ------------------------------------------------------------- > > Key: JBDS-3867 > URL: https://issues.jboss.org/browse/JBDS-3867 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not. > The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box. > It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22979) Freemarker New and Noteworthy for 4.4.1.AM3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22979?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-22979. ------------------------------------ Resolution: Done > Freemarker New and Noteworthy for 4.4.1.AM3 > ------------------------------------------- > > Key: JBIDE-22979 > URL: https://issues.jboss.org/browse/JBIDE-22979 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.1.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23007) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23007?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-23007 at 8/15/16 8:52 PM: ----------------------------------------------------------------- Downloads/installs are interesting but we also want to track usage. How many startups, what features are used by users who installed devstudio via rpm, etc. The stuff we track by our usage plugin. The easiest way to do it seems to be to use different product IDs when it's possible or/and we can add a special prefix to product ID when reporting it to Google Analytics. was (Author: akazakov): Downloads/installs are interesting but we also want to track usage. How many startups, what features are used by users who installed devstudio via rpm, etc. The stuff we track by our usage plugin. > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBIDE-23007 > URL: https://issues.jboss.org/browse/JBIDE-23007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23007) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23007?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23007: ---------------------------------------- Downloads/installs are interesting but we also want to track usage. How many startups, what features are used by users who installed devstudio via rpm, etc. The stuff we track by our usage plugin. > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBIDE-23007 > URL: https://issues.jboss.org/browse/JBIDE-23007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22771) Remove Add and Remove page from new server wizard for CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22771?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22771: ------------------------------------- I looked into making a patch for this upstream, but it seems absolutely impossible. One of the general rules is that each page can have children pages. A page can only tell the framework to update itself, or its child pages. There's no way to tell the framework to reload all pages, or to reload the list of children available from the root fragment. In fact, adding such an API could add instability into how the pages are resolved, and what page is the current page. TaskWizardPage is package-private, which means nobody can see it, and looking back through their commit log, this seems 100% intentional. Even if I try to do this 100% in wtp, and keep all changes private in wtp, it still seems virtually impossible to instruct the root fragment of the wizard to re-load its children. The TaskWizard framework simply won't allow it, and that's probably because it's unsafe to make changes to any fragment that isn't in use or its direct children. Sadly, I'm going to have to reject this as won't fix. I know it's not a satisfying answer, but allowing a child fragment to force it's parent to reload / recreate the children just isn't appropriate, and that's the only way to accomplish the fix. > Remove Add and Remove page from new server wizard for CDK > --------------------------------------------------------- > > Key: JBIDE-22771 > URL: https://issues.jboss.org/browse/JBIDE-22771 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > Maybe this is just not possible, I don't know. > But I noticed that when you create a cdk server, you still go through the Add or Remove page which is not really relevant here. > And then in the Servers view, in the context menu (right-click the cdk adapter), you also have Add or Remove - could we possibly remove it from there too? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22771) Remove Add and Remove page from new server wizard for CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22771?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22771. --------------------------------- Fix Version/s: 4.4.1.Final (was: LATER) Resolution: Rejected > Remove Add and Remove page from new server wizard for CDK > --------------------------------------------------------- > > Key: JBIDE-22771 > URL: https://issues.jboss.org/browse/JBIDE-22771 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > Maybe this is just not possible, I don't know. > But I noticed that when you create a cdk server, you still go through the Add or Remove page which is not really relevant here. > And then in the Servers view, in the context menu (right-click the cdk adapter), you also have Add or Remove - could we possibly remove it from there too? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23007) Track rh-eclipse46-devstudio-*.rpm version usage

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23007?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23007 at 8/15/16 7:09 PM: ------------------------------------------------------------- If we rebuild (or simply tweak) the update site metadata we could embed a different "phone home" URL, via p2StatsURL: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L118 Then we could look at those 404 requests to https://devstudio.redhat.com/usage/installs/$\{JOB_NAME}/$\{project.versi... in the apache log to see how many installs come from rpm vs. from update site. I don't believe we currently differentiate between the two options in #3 above (a., jar installer vs. b., p2/BYOE install vs., c., Marketplace install), nor would we be able to differentiate #2 ("installed via p2") vs. #3b or #3c. In other words, any p2 installation that points at the same update site, eg., https://devstudio.redhat.com/10.0/stable/updates/ , will appear to be the same install regardless of HOW the user did the install. So, I propose these 3 cases instead: 1) Devstudio installed via rh-eclipse46-devstudio-*.rpm - track using p2StatsURL or by counting the number of times the rpm is downloaded 2) Devstudio installed via p2 (BYOE, Marketplace, or on top of rh-eclipse46-base-*.rpm) - track using p2StatsURL 3) Devstudio installed via installer jar - track by counting the number of times the jar is downloaded was (Author: nickboldt): If we rebuild (or simply tweak) the update site metadata we could embed a different "phone home" URL, via p2StatsURL: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L118 Then we could look at those 404 requests to https://devstudio.redhat.com/usage/installs/${JOB_NAME}/${project.version... in the apache log to see how many installs come from rpm vs. from update site. I don't believe we currently differentiate between the two options in #3 above (a., jar installer vs. b., p2/BYOE install vs., c., Marketplace install), nor would we be able to differentiate #2 ("installed via p2") vs. #3b or #3c. In other words, any p2 installation that points at the same update site, eg., https://devstudio.redhat.com/10.0/stable/updates/ , will appear to be the same install regardless of HOW the user did the install. So, I propose these 3 cases instead: 1) Devstudio installed via rh-eclipse46-devstudio-*.rpm - track using p2StatsURL or by counting the number of times the rpm is downloaded 2) Devstudio installed via p2 (BYOE, Marketplace, or on top of rh-eclipse46-base-*.rpm) - track using p2StatsURL 3) Devstudio installed via installer jar - track by counting the number of times the jar is downloaded > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBIDE-23007 > URL: https://issues.jboss.org/browse/JBIDE-23007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23007) Track rh-eclipse46-devstudio-*.rpm version usage

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23007?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23007: ------------------------------------ If we rebuild (or simply tweak) the update site metadata we could embed a different "phone home" URL, via p2StatsURL: https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L118 Then we could look at those 404 requests to https://devstudio.redhat.com/usage/installs/${JOB_NAME}/${project.version... in the apache log to see how many installs come from rpm vs. from update site. I don't believe we currently differentiate between the two options in #3 above (a., jar installer vs. b., p2/BYOE install vs., c., Marketplace install), nor would we be able to differentiate #2 ("installed via p2") vs. #3b or #3c. In other words, any p2 installation that points at the same update site, eg., https://devstudio.redhat.com/10.0/stable/updates/ , will appear to be the same install regardless of HOW the user did the install. So, I propose these 3 cases instead: 1) Devstudio installed via rh-eclipse46-devstudio-*.rpm - track using p2StatsURL or by counting the number of times the rpm is downloaded 2) Devstudio installed via p2 (BYOE, Marketplace, or on top of rh-eclipse46-base-*.rpm) - track using p2StatsURL 3) Devstudio installed via installer jar - track by counting the number of times the jar is downloaded > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBIDE-23007 > URL: https://issues.jboss.org/browse/JBIDE-23007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.1.Final > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23008: ------------------------------- Workaround Description: Build using mvn flag `-Dtycho.baseline=disable` to skip the baseline check. Workaround: Workaround Exists > openshift.cdk.feature.source missing from JBT site; causes baseline check to fail > --------------------------------------------------------------------------------- > > Key: JBIDE-23008 > URL: https://issues.jboss.org/browse/JBIDE-23008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since the weekend (after I published an AM3 build into /neon/staging/updates/): > {code} > [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar > [INFO] > [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server --- > [INFO] > [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar > [INFO] > [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server --- > [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents > [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml > The main artifact has been replaced with the baseline version. > The following attached artifacts are not present in the baseline and have been removed: [sources]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016