[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: devex #114 May 2017
> 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 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.0.0.Alpha3
>
>
> 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, 11 months
[JBoss JIRA] (JBDS-3864) Why is the platform installer installing pscp when Cygwin openssh scp is also installed?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3864?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3864:
--------------------------------
Sprint: devex #114 May 2017
> Why is the platform installer installing pscp when Cygwin openssh scp is also installed?
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3864
> URL: https://issues.jboss.org/browse/JBDS-3864
> Project: Red Hat 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: Optional
> Fix For: 10.0.0.Alpha3
>
>
> Why does the platform installer install putty's pscp.ese when it also installs Cygwin's openssh which includes scp?
> A while back vagrant-service-manager had a dependency on pscp.exe for copying certificates, but I believe that was eliminated a while back. (around the time of the rename from adbinfo to service-manager).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3727:
--------------------------------
Sprint: devex #114 May 2017
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha3
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22268) Server adapter wizard: create unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22268?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22268:
-------------------------------------
Original Estimate: 8 minutes
Remaining Estimate: 8 minutes
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22268
> URL: https://issues.jboss.org/browse/JBIDE-22268
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
> Original Estimate: 8 minutes
> Remaining Estimate: 8 minutes
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22268) Server adapter wizard: create unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22268?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22268:
------------------------------------------
merged https://github.com/jbosstools/jbosstools-openshift/pull/1133 with a testing infrastructure and 2 tests that assert selecting the workspace project for a given service (workspace-project/git-remote vs buildConfig/buildSourceURI).
[~scabanovich] you can add your test for ServerSettingsWizardPageModel in ServerSettingsWizardPageModelTest.
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22268
> URL: https://issues.jboss.org/browse/JBIDE-22268
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-13287) examples URLs should use major/minor/service/milestone convention
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13287?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13287:
-------------------------------------
We can't move all the files to other locations, some of theses are hard coded in older versions of JBT/JBDS (pre ide-config.properties). Unless we don't give a crap.
Moving all bits and pieces for post ide-config.properties, will be tedious and we might risk missing some things. But it's doable.
Or we can start moving to semver organization for JBT 4.4/Devstudio 10 only.
In that case, do we want to separate JBT/Devstudio folders or keep everything under the JBT versioning scheme?
> examples URLs should use major/minor/service/milestone convention
> ------------------------------------------------------------------
>
> Key: JBIDE-13287
> URL: https://issues.jboss.org/browse/JBIDE-13287
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.4.x
>
>
> Instead of
> {code:title=http://download.jboss.org/jbosstools/examples/}
> project-examples-community-4.0.GA.xml
> project-examples-jbds60.xml
> project-examples-maven-4.0.GA.xml
> project-examples-shared-4.0.GA.xml
> ...
> {code}
> We should consider using something like 6/1/0/Alpha1/project-examples*.xml
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3698) Installer - We should document (rel notes) the versions of the installable components that we support
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3698?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3698:
---------------------------------
Added this note to the doc:
Note: If an older than required version of one of the listed products is detected, the current version of the Installer requires the user to quit the Installation, uninstall/update the relevant product(s), and then start the Installer afresh.
[~jrichter1]:
a. Does this look OK to you, or do you have any further feedback about this?
b. Is this issue logged in a JIRA somewhere? It may be useful to link to the relevant JIRA as a known issue for this in the note.
> Installer - We should document (rel notes) the versions of the installable components that we support
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-3698
> URL: https://issues.jboss.org/browse/JBDS-3698
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Task
> Components: documentation, platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: havoc
> Fix For: 10.0.0.Alpha3
>
>
> It's good that the installer will allow users to have/retain their own installed components, and verify that the installed versions are supported, but we should provide the users with a documented list of the ranges of supported versions. Thx!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months