[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18912:
-------------------------------------
I'm lowering severity based on recent comment:
"11. If you remove the project and deploy again now, it will work. But if you go all over again (i.e. new server start) it will not work"
This means publishing to a custom folder generally works, but fails in this specific case.
> Custom deploy dir with remote server using filesystem operations does not work
> ------------------------------------------------------------------------------
>
> Key: JBIDE-18912
> URL: https://issues.jboss.org/browse/JBIDE-18912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Labels: help_wanted
> Fix For: 4.5.0.AM2
>
>
> This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used).
> Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles.
> I tried this several times and still could not get it to work.
> Perhaps it might be worth to try and get this in the final 4.2.1.Final build?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4448:
--------------------------------
Sprint: devex #135 July 2017
> JBDS install failure with no explanation
> -----------------------------------------
>
> Key: JBDS-4448
> URL: https://issues.jboss.org/browse/JBDS-4448
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.4.0.GA
> Environment: Mac, using DevSuite installer 1.4.1 GA
> Reporter: Bob Davis
> Assignee: Denis Golovin
> Priority: Critical
> Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log
>
>
> Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out.
> Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it.
> Quitting is the only option.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18912:
--------------------------------
Priority: Minor (was: Major)
> Custom deploy dir with remote server using filesystem operations does not work
> ------------------------------------------------------------------------------
>
> Key: JBIDE-18912
> URL: https://issues.jboss.org/browse/JBIDE-18912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Labels: help_wanted
> Fix For: 4.5.0.AM2
>
>
> This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used).
> Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles.
> I tried this several times and still could not get it to work.
> Perhaps it might be worth to try and get this in the final 4.2.1.Final build?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4330) GPG Signature verification for .json and .js files
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4330?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4330:
--------------------------------
Sprint: devex #135 July 2017 (was: devex #134 Jun 2017)
> GPG Signature verification for .json and .js files
> --------------------------------------------------
>
> Key: JBDS-4330
> URL: https://issues.jboss.org/browse/JBDS-4330
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> To allow loading remote configuration or even java script modules there should be a way to confirm origin of downloaded file to prevent 'man in the middle attacks'. Files loaded from remote location should bear GPG signature that installer should verify before proceeding with loaded file.
> This should be possible with https://github.com/openpgpjs/openpgpjs using https://openpgpjs.org/openpgpjs/doc/index.html using 'Create and verify detached signatures'.
> The Idea is to sign .json of .js file with GPG and then download it ad separate json/js code from the signature, verify it and then proceed with loading .json or js module form string.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3868:
--------------------------------
Sprint: devex #135 July 2017 (was: devex #134 Jun 2017)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> 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
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4444:
--------------------------------
Sprint: devex #135 July 2017 (was: devex #134 Jun 2017)
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM2
>
> Attachments: devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months