[JBoss JIRA] (JBDS-4624) All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4624?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4624:
-----------------------------
Fix Version/s: 11.x
(was: 11.1.0.GA)
> All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4624
> URL: https://issues.jboss.org/browse/JBDS-4624
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Affects Versions: 11.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 11.x
>
>
> All properties for Devstudio 11.1.0.GA / JBT 4.5.1.Final are commented out in ide-config.properties at
> http://download.jboss.org/jbosstools/configuration/ide-config.properties
> {code}
> ### milestone staging
> # 4.5.oxygen version of jbosstools-earlyaccess.properties should be edited here, so the discovery job can fetch it: http://download.jboss.org/jbosstools/oxygen/snapshots/updates/earlyaccess...
> #jboss.discovery.directory.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/jbosstools-directory.xml
> #jboss.discovery.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/
> #jboss.discovery.earlyaccess.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/
> #jboss.discovery.earlyaccess.list.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/discovery.earlyaccess/4.5.1.Final/jbosstools-earlyaccess.properties
> #jboss.central.webpage.url|jbosstools|4.5.1.Final=https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=public-jboss&g=org.jboss.tools.central&a=jbosstools-central-webpage&v=2.0.0-SNAPSHOT&e=zip&mustEndWith=.zip
> #jboss.discovery.site.integration-stack.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/development/updates/integration-stack/discovery/
> #jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/development/updates/integration-stack/discovery/earlyaccess/
> #jboss.fuse.extras.site.url|jbosstools|4.5.1.Final=http://download.jboss.org/jbosstools/oxygen/staging/updates/fuse-extras/4.5.1.Final/
> # 4.5.oxygen version of devstudio-earlyaccess.properties should be edited here, so the discovery job can fetch it: https://devstudio.redhat.com/11/snapshots/updates/earlyaccess.properties/...
> #jboss.discovery.directory.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/devstudio-directory.xml
> #jboss.discovery.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/
> #jboss.discovery.earlyaccess.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/
> #jboss.discovery.earlyaccess.list.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/discovery.earlyaccess/11.1.0.GA/devstudio-earlyaccess.properties
> #jboss.central.webpage.url|devstudio|11.1.0.GA=https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?r=public-jboss&g=org.jboss.tools.central&a=jbosstools-central-webpage&v=2.0.0-SNAPSHOT&e=zip&mustEndWith=.zip
> #jboss.discovery.site.integration-stack.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/development/updates/integration-stack/discovery/
> #jboss.discovery.earlyaccess.site.integration-stack.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/development/updates/integration-stack/discovery/earlyaccess/
> #jboss.fuse.extras.site.url|devstudio|11.1.0.GA=https://devstudio.redhat.com/11/staging/updates/fuse-extras/11.1.0.GA/
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25351) CDK server adapter can be saved even though that there is error
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25351?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25351:
-------------------------------------
The location of the error decorator (bottom left) is set in org.eclipse.ui.forms. There is no ability to override this, without a patch to both org.eclipse.wst.server and org.eclipse.ui.forms. Sorry.
The error message "1 error detected" is the default behavior of IManagedForm, an implementation choice made on the part of org.eclipse.wst.server.ui. This is to accumulate several possible errors together into one error message. On mouse-over, you can view all the different errors. Changing the behaivor here to show the single message if only one error is present would need to be done in org.eclipse.ui.forms, and may not be desirable since that package is so widely used by many different plugins. Many plugins may prefer the existing behavior.
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=527081 to address some of the other issues. Who knows how it will be received.
> CDK server adapter can be saved even though that there is error
> ---------------------------------------------------------------
>
> Key: JBIDE-25351
> URL: https://issues.jboss.org/browse/JBIDE-25351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
>
> CDK 3.2+ server editor allows user to save the editor even if it shows error in server's name that is already in use.
> Also, error decorator is placed in the bottom part of the field, and in page header, there is only message "1 error detected". Change the error message in header or just do not show anything as is happening with validation of field like Minishift Binary.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25374) Validate Red Hat credentials when entering them / setting up CDK adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25374?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25374:
-------------------------------------
I'm not entirely sure this is possible. First, not all credentials will be validatable. Remember, the credential framework is sorted into domains only really as an organizing method. The credentials aren't used exclusively with those domains.
Second, even if they were, there's no universal web url at every domain through which all credentials can be validated. This means the validation method would need to be customized per-domain, which would drastically reduce it's utility.
Third, if credentials for servers that are not up yet (ie imagine an apache server on a machine in your network) simply can't be validated.
Fourth, since we mostly just take a domain, a user, and a password (for now), we'd need to know what TYPE of credentials this is. If it's an ssh credential, it's validation method would be completely different than if it's an https credential for your IP's apache installation, or for an instance of your mysql database. As of now, we don't separate out credential types, and so we can't really know how to validate it.
I see this as an extremely difficult task, at least to solve generically in the credentials framework itself.
> Validate Red Hat credentials when entering them / setting up CDK adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-25374
> URL: https://issues.jboss.org/browse/JBIDE-25374
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> In JBIDE-25260 we were dealing with the issue that when the credentials are wrong when starting CDK in devstudio, the user will be asked to correct them in the Console view which brings problems.
> Gerard Braad suggested that we should validate the credentials when setting them up. I think it's actually not a bad idea. We would need to figure out when/where to do this. Also, the credentials could still become invalid before starting CDK, but the risk would be much lower. So it's a good question if it's worth or a good idea to do something like this.
> Cc: [~jeffmaury]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25380) Server adapter editor: 'Undo' of most editor actions fails to correctly undo
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25380?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25380:
--------------------------------
Fix Version/s: 4.5.2.AM1
> Server adapter editor: 'Undo' of most editor actions fails to correctly undo
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25380
> URL: https://issues.jboss.org/browse/JBIDE-25380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.5.2.AM1
> Reporter: Rob Stryker
> Fix For: 4.5.2.AM1
>
>
> Many actions in the editor cannot be correctly undone. Using the ctrl+z shortcut often leaves the editor and model in conflicting states. I believe the root cause of this is that the dependence on databinding and a specific model type is confusing things. What's more, the specific model class being used is extended from teh wizard model. This seems completely inappropriate, because the server editor is really just backed by the server working copy, and doesn't need 80% of the fields that are in the wizard model.
> Also, since a good many actions like changing the connection or the source project, make no sense and almost never function correctly, many of these actions should really not be available. They only make it more likely for a user to break his environment.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months