[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24548.
------------------------------
Verified in Devstudio 11.0.0.GA. Closing.
> Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-24548
> URL: https://issues.jboss.org/browse/JBIDE-24548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Environment: Running on Mac 10.12.4
> JBDS
> Version: 10.3.0.GA
> Build id: GA-v20170218-1636-B94
> Build date: 20170218-1636
> Installed minishift v1.0.1
> Reporter: Veer Muchandi
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.Final
>
>
> * Created a Wildfly application on openshift web-ui
> * Setup a server adapter
> * Imported application to JBDS
> * Made code changes and saved.
> Result:
> While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-24024:
------------------------------------
[~adietish] I guess this is resolved as part of your huge PR which didn't make it into 11.0.0.GA, right? If so, please change the fix version ;-)
> Server adapter editor, wizard: better tell me what the settings are for
> -----------------------------------------------------------------------
>
> Key: JBIDE-24024
> URL: https://issues.jboss.org/browse/JBIDE-24024
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png, server-adapter-editor.png, server-adapter-wizard.png
>
>
> A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though:
> The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where"
> !image-2017-03-03-11-43-41-941.png!
> The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination:
> !image-2017-03-03-11-44-46-410.png!
> "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource".
> Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24509.
--------------------------------
> No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final
> ------------------------------------------------------------------------
>
> Key: JBIDE-24509
> URL: https://issues.jboss.org/browse/JBIDE-24509
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Environment: JBoss Tools 4.4.4.Final
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> Eclipse Neon 4.6.1
> Fedora 24 and Windows 10
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.5.0.Final
>
> Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png, Screenshot from 2017-06-02 10-20-42.png, Screenshot from 2017-06-02 10-39-16.png, Screenshot from 2017-06-02 10-54-54.png
>
>
> Description of problem:
> No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools:
> JBoss OpenShift 2 Tools
> JBoss OpenShift JavaScript Tools
> JBoss Tools EGit Integration
> Version-Release number of selected component (if applicable):
> JBoss Tools 4.4.4.Final
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> How reproducible:
> Always
> Steps to Reproduce:
> 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...:
> --> Add the following URL to Eclipse Neon 4.6.1 installation via:
> Help > Install New Software... > Work with:
> http://download.jboss.org/jbosstools/neon/stable/updates/
> Then select all the components, choose to install them.
> 2. Restart Eclipse Neon 4.6.1 after JTB installation finished
> 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty
> 4. Go to Help > Intallation Details, search for openshift
> Actual results:
> 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist:
> JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat
> JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat
> JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat
> Expected results:
> JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> Additional info:
> Issue reproduced on both Fedora 24 and Windows 10.
> This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24642) Please include sha256 checksums in announcements
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24642?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24642.
--------------------------------
Verified, I have received email announcement which contains checksums. Closing.
> Please include sha256 checksums in announcements
> ------------------------------------------------
>
> Key: JBIDE-24642
> URL: https://issues.jboss.org/browse/JBIDE-24642
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, website
> Reporter: Jesper Skov
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> I would like to be able to verify checksums on downloaded JBoss artifacts - both EAP and eclipse-related binaries.
> Or even better, verify a signature.
> Today, when I want to use a JBossTools release, I would download
> http://download.jboss.org/jbosstools/static/oxygen/development/updates/co...
> And my only opportunity to verify the file is by downloading the sha256 file that lies next to it:
> http://download.jboss.org/jbosstools/static/oxygen/development/updates/co...
> If a hacker manages to replace the updatesite archive with compromised files, I assume they will have the brains to also update the checksum file next to it.
> So the current checksum can really only be used to verify the integrity of the downloaded file.
> Not that its contents is untampered.
> If the jar-files in the archive were signed, it would be less of an issue...
> Signed artifacts would be best. But would probably take some effort to put in place.
> A simpler remedy would be to include the checksums in the announcement. This would give an additional factor of security for those who care about that.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months