[JBoss JIRA] (JBIDE-25098) Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25098?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-25098.
---------------------------------
Merged in master. Closing.
> Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-25098
> URL: https://issues.jboss.org/browse/JBIDE-25098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Fix For: 4.5.1.AM3
>
>
> in org.jboss.tools.runtime.core.util.internal.DownloadRuntimeOperationUtility.downloadAndUnzip(String, String, String, boolean, String, String, TaskModel, IProgressMonitor)
> a status is directly returned instead of following the guidelines explained in the javadoc for CoreException.getStatus to recreate a Status which will preserve the stacktrace
> {noformat}
> IStatus org.eclipse.core.runtime.CoreException.getStatus()
> Returns the status object for this exception.
> IMPORTANT:
> The result must NOT be used for logging, error reporting, or as a method return value, since that code pattern hides the original stack trace. Instead, create a new Status with your plug-in ID and this CoreException, and use that new status for error reporting or as a method return value. For example, instead of:
> yourPlugin.getLog().log(exception.getStatus());
>
> Use: IStatus result = new Status(exception.getStatus().getSeverity(), pluginId, message, exception);
> yourPlugin.getLog().log(result);
>
> Returns:a status object
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-25095.
---------------------------------
Both modules are now added to the default classpath for both wf11 and eap 7.1. Verified in devstudio 11.1.0.AM3 B1225. Closing.
> WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path
> -----------------------------------------------------------------------------
>
> Key: JBIDE-25095
> URL: https://issues.jboss.org/browse/JBIDE-25095
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM3
>
>
> When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet).
> To make this code compile, two jar files are required:
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar
> I think the runtime should add them by default.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25050:
----------------------------------
Fix Version/s: 4.5.1.Final
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: 4.5.1.Final
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25050:
----------------------------------
Story Points: 5
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: 4.5.1.Final
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25050:
----------------------------------
Description:
Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
* Install manually HyperV in fresh windows image
* Add new virtual switch
* Set env. variable HYPERV_VIRTUAL_SWITCH
* Add user into Hyper-V Administrators group
* Test whether cdk can be run on the slave
was:Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months