[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3797:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Installer: temporary files are not removed when window is closed
> ----------------------------------------------------------------
>
> Key: JBDS-3797
> URL: https://issues.jboss.org/browse/JBDS-3797
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer, upstream
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
>
> # download installer exe
> # run DeveloperPlatformInstaller*.exe
> # when installer's window opens, close the window
> # look into _C:\Users\yourusername\AppData\Local\Temp_
> result:
> Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3797:
-----------------------------------
Assignee: Denis Golovin
> Installer: temporary files are not removed when window is closed
> ----------------------------------------------------------------
>
> Key: JBDS-3797
> URL: https://issues.jboss.org/browse/JBDS-3797
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer, upstream
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
>
> # download installer exe
> # run DeveloperPlatformInstaller*.exe
> # when installer's window opens, close the window
> # look into _C:\Users\yourusername\AppData\Local\Temp_
> result:
> Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3798:
--------------------------------
Labels: ui (was: havoc)
> Repeated component detection keeps stale values
> -----------------------------------------------
>
> Key: JBDS-3798
> URL: https://issues.jboss.org/browse/JBDS-3798
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160413-107
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.2.0.AM2
>
> Attachments: screenshot-1.png
>
>
> Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same.
> Using the existing (no longer existing in fact) installation fails, naturally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3798:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Repeated component detection keeps stale values
> -----------------------------------------------
>
> Key: JBDS-3798
> URL: https://issues.jboss.org/browse/JBDS-3798
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160413-107
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
> Attachments: screenshot-1.png
>
>
> Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same.
> Using the existing (no longer existing in fact) installation fails, naturally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19911:
----------------------------------
Assignee: Nick Boldt
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM2
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19911:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.x)
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Fix For: 4.4.2.AM2
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months