September 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2730: ------------------------------------------- marking as critcial since work is going on but if it fails to complete we can release without it and do akamai update later. > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: requirements, updatesite > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17608) improve p2diff's URI handling to support relative path folder and zips

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17608?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17608: --------------------------------------------- moving off since not blocking release > improve p2diff's URI handling to support relative path folder and zips > ---------------------------------------------------------------------- > > Key: JBIDE-17608 > URL: https://issues.jboss.org/browse/JBIDE-17608 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x, 4.3.0.Alpha1 > > > Instead of having to type: > {code} > p2diff file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target/jbtearlyaccess-multiple.target.repo/ file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target_FULL/jbtearlyaccess-multiple.target.repo/ > {code} > I'd like to see it work for > {code} > p2diff target target2 > or > p2diff site.zip site2.zip > {code} > So we need a few things: > a) find the nested repo in the specified folder (if not in `pwd` look in child folders for a p2 repo or repo zip) > b) better error reporting if the specified folders aren't repos or don't contain repos (right now p2diff does NOTHING if it doesn't like the URIs stated > c) if a local path exists, prepend file:// onto the file path so it behaves like a p2 URI > d) if a local repo zip found then prepend jar:file:// and append !/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2730: -------------------------------------- Priority: Critical (was: Major) > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: requirements, updatesite > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16970: ---------------------------------------- Fix Version/s: 4.2.x 4.3.0.Alpha1 (was: 4.2.0.Final) > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x, 4.3.0.Alpha1 > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17608) improve p2diff's URI handling to support relative path folder and zips

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17608?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17608: ---------------------------------------- Fix Version/s: 4.2.x 4.3.0.Alpha1 (was: 4.2.0.CR1) > improve p2diff's URI handling to support relative path folder and zips > ---------------------------------------------------------------------- > > Key: JBIDE-17608 > URL: https://issues.jboss.org/browse/JBIDE-17608 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x, 4.3.0.Alpha1 > > > Instead of having to type: > {code} > p2diff file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target/jbtearlyaccess-multiple.target.repo/ file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target_FULL/jbtearlyaccess-multiple.target.repo/ > {code} > I'd like to see it work for > {code} > p2diff target target2 > or > p2diff site.zip site2.zip > {code} > So we need a few things: > a) find the nested repo in the specified folder (if not in `pwd` look in child folders for a p2 repo or repo zip) > b) better error reporting if the specified folders aren't repos or don't contain repos (right now p2diff does NOTHING if it doesn't like the URIs stated > c) if a local path exists, prepend file:// onto the file path so it behaves like a p2 URI > d) if a local repo zip found then prepend jar:file:// and append !/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create p2diff job to verify that nightly build is different from previous milestone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16970: ---------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR1) > create p2diff job to verify that nightly build is different from previous milestone > ----------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Final > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3052: -------------------------------------- Assignee: Michelle Murray (was: Nick Boldt) > Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3052 > URL: https://issues.jboss.org/browse/JBDS-3052 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 8.0.0.CR1 > > Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png > > > To test the user experience on Windows, I created three accounts: > * nboldt (my own admin user) > * {color:orange}*dummy*{color} (a standard user) > * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account ) > Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central: > !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png! > !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png! > ------ > However, there are problems when using an Admin user-installed shared install folder for JBDS. > Steps to repro: > *As nboldt / admin user* > * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions) > *As dummy / standard user* > * Log in > * Launch the shared JBDS > * Install something from Central > !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png! > *PROBLEM*: standard user should not be able to install new features into the shared install folder > *As kid / child user* > * Log in > * Launch the shared JBDS > * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png! > *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3052: -------------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) marking as affecting docs and assigning to michelle so its not lost. > Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3052 > URL: https://issues.jboss.org/browse/JBDS-3052 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 8.0.0.CR1 > > Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png > > > To test the user experience on Windows, I created three accounts: > * nboldt (my own admin user) > * {color:orange}*dummy*{color} (a standard user) > * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account ) > Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central: > !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png! > !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png! > ------ > However, there are problems when using an Admin user-installed shared install folder for JBDS. > Steps to repro: > *As nboldt / admin user* > * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions) > *As dummy / standard user* > * Log in > * Launch the shared JBDS > * Install something from Central > !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png! > *PROBLEM*: standard user should not be able to install new features into the shared install folder > *As kid / child user* > * Log in > * Launch the shared JBDS > * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png! > !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png! > *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17932) build tool to compare projects' latest github revision that have been built against latest revisions in github

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17932?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17932: ---------------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.CR2) > build tool to compare projects' latest github revision that have been built against latest revisions in github > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17932 > URL: https://issues.jboss.org/browse/JBIDE-17932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > > Need a cmd tool (python?) that given a list of projects={aerogear, birt, ...vpe, webservices} & a stream={4.2.luna, master} can perform these steps: > a) check the latest built github revision in Jenkins for the job > b) check the latest github revision for the matching branch > c) report to console: > {code} > status, job name, branch built, revision in Jenkins, revision in github branch > PASS, jbosstools-aerogear_4.2.luna, origin/jbosstools-4.2.0.Beta3x, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80 > FAIL, jbosstools-birt_4.2.luna, origin/jbosstools-4.2.0.Beta3x, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80, 638aa9268c52fbafd6fd283aedd67a1813444848 > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17932) build tool to compare projects' latest github revision that have been built against latest revisions in github

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17932?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17932: --------------------------------------------- moving of 4.2 since not blocking > build tool to compare projects' latest github revision that have been built against latest revisions in github > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17932 > URL: https://issues.jboss.org/browse/JBIDE-17932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > > Need a cmd tool (python?) that given a list of projects={aerogear, birt, ...vpe, webservices} & a stream={4.2.luna, master} can perform these steps: > a) check the latest built github revision in Jenkins for the job > b) check the latest github revision for the matching branch > c) report to console: > {code} > status, job name, branch built, revision in Jenkins, revision in github branch > PASS, jbosstools-aerogear_4.2.luna, origin/jbosstools-4.2.0.Beta3x, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80 > FAIL, jbosstools-birt_4.2.luna, origin/jbosstools-4.2.0.Beta3x, 91f7dc7626d8a3e4c27bd84a27c0f485d0a63c80, 638aa9268c52fbafd6fd283aedd67a1813444848 > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 September 2014